The meeting ended. And then the real work started.
Hey,
Last week I had a customer review that lasted exactly 30 minutes.
Thirty minutes on the clock. And then three days of work that followed from it — a revised proposal, an internal technical discussion and call I hadn’t planned for, a pricing summary that went through four drafts before I sent it.
I sat back after it was all done and thought — that one call basically wrote my entire week.
And here’s the honest thing I want to share with you this week: I wasn’t bothered by it. Because every bit of that post-meeting work felt purposeful. I knew why I was doing it. It was moving something forward.
That’s when it hit me — we’ve been thinking about meetings all wrong.
The productivity world loves to say meetings are a waste of time. “This could’ve been an email.” “Meetings steal your deep work hours.” I’ve nodded along to all of it. Still do, sometimes.
But managing a sales team has taught me something that’s hard to learn from a productivity book: the meeting itself is rarely the problem. The work it generates is.
When a meeting ends well, you walk out with a clear head and a short list of things that genuinely matter. The follow-up work feels almost easy — you know what it is, you know why it exists, you know who’s doing it.
When a meeting ends badly — vague, undecided, slightly uncomfortable — the aftermath is a different animal entirely. Threads asking “wait, what did we agree on?” Internal messages trying to reconstruct decisions nobody wrote down. Action items that sit in someone’s head and quietly die there.
Same thirty minutes. Completely different three days.
I started asking myself one question before any important meeting now:
What work do I want this meeting to create?
Not what topics do I want to cover. Not what’s on the agenda. But what should the people in this conversation walk away actually doing?
It sounds almost too simple. But preparing with that question in mind changes everything — how I open the meeting, what I push to decide vs. park, and how I close it.
And after the call? I give myself five minutes — right then, while it’s all still fresh — to write down three things in my notes: the outcome, the decisions, the next steps with names attached. Five minutes. It saves hours of confusion later.
Because here’s what I’ve noticed: if you don’t capture the why behind a decision while you still remember it, the follow-up work eventually feels like busywork. And busywork is what makes people say “ugh, that meeting was pointless.”
The meeting wasn’t pointless. You just lost the thread.
Wispr Flow makes it even more easy, just talk to my Pixel or Dell Latitude. And the meeting brief is there in my Obsidian Daily Notes and Coda (if 'its a project).
So does a meeting ever really end?
Probably not. It ends when everything it set in motion is done. And I’ve made peace with that.
The goal was never to have meetings that create no work. That would mean nothing got decided and nothing’s moving. The goal is to have meetings that create the right work — work you can do with clarity and confidence.
That’s the version of “productive meeting” nobody really talks about. It’s not shorter. It’s not fewer. It’s just — better designed.
Worth thinking about this week.
One small thing to try before your next important meeting:
Write this sentence before you walk in: “After this meeting, I want [person] to be able to do [specific thing].”
If you can’t fill it in, you’re not ready yet.
As always, thank you for reading. Means a lot that you’re here.
Keep going.
— Kaushik / SystemsAndFlow