Running a meeting
Open with a clear agenda, keep time, and close with owners and dates, or show up and add real value.
Case study: Karan's sixty minute status call
Karan, a tech lead in Hyderabad, ran a weekly sync with a client team in Amsterdam. There was no agenda. He opened with "Shall we start? Anyone has any points?" and the call drifted into a forty minute debate about logging. Two decisions never got made, and the Dutch product owner started declining the invite. His colleague Meera took over for a month. She sent three agenda items a day early, put a time next to each, opened with "By 4:30 we need a decision on the release date," and closed by reading out owners and dates. The call shrank to 25 minutes and the product owner started joining early.
Takeaway: A meeting with a stated outcome, a clock and named owners earns people's time. One without them loses it.
We often wait for the senior person to steer, and we stay silent so we don't seem pushy. Global teams expect whoever owns the invite to drive it, and expect attendees to speak up early instead of saving their point for a follow-up chat.
Running the meeting
Goal: End on time with decisions made, and every action tied to one owner and one date.
Step by step
- State the outcome. Open with what the meeting must decide or produce, not just the topics.
- Timebox the agenda. Two or three items, each with minutes next to it.
- Keep the clock. Park side topics politely and move on when time is up.
- Close with owners. Read back each action with one name and one date.
Say this, not that
| Thanks for joining. By the end of this call, we need to agree on the release date. | Shall we start? Anyone has any points? | An outcome gives the meeting a finish line. |
| We've got three items today. Ten minutes on the bug list, ten on the demo, and five on next steps. | ||
| That's a great point, but it needs more time. Can we park it and pick it up separately? | Let's not discuss that now. | Parking respects the idea and protects the clock. |
| We're at time on this one. Let me summarize where we landed and move on. | Okay okay, we'll see later. | A summary closes the item instead of letting it trail off. |
| Before we drop, let me read back the actions: Hannah, the test plan by Thursday. Me, the deployment checklist by Friday. |
Model conversation
- You
- Hi everyone, thanks for joining. By 4:30 we need to agree on the release date. Three items: open bugs, the demo, and next steps.
- Hannah
- Sounds good. Can I start with the bugs? Two of them are blockers for us.
- You
- Please do, Hannah. We have ten minutes for this one.
- Hannah
- The login timeout and the export bug. Also, while we're here, I wanted to talk about the new reporting module.
- You
- Reporting is important, but it deserves its own slot. Can we park it and I'll set up a call for Monday?
- Hannah
- Fair enough. Monday works.
- You
- Great. So, actions: Hannah confirms the bug priority by Thursday, and I'll share the fix plan by Friday. Release date stays the twentieth unless the blockers slip.
- Hannah
- Perfect. That's the shortest useful call we've had all month.
Attending and contributing
Goal: Speak in the first ten minutes and make one clear, useful point in about thirty seconds.
Step by step
- Prepare one point. Before the call, write down the one thing you want to say.
- Speak early. Get your voice in the first ten minutes. It gets harder later.
- Point first. Lead with your conclusion, then one reason, then a suggestion.
- Hand it back. End with a question or a clear ask so the meeting can move.
Say this, not that
| Can I add something quickly? | Sorry, sorry, just one small thing, maybe it is not important. | Too many apologies shrink your point before you make it. |
| My main point is that we should test on the client's data before Friday. | Conclusion first lets busy listeners follow you. | |
| The reason is simple. Last sprint, staging data hid two bugs that production found. | ||
| To build on what Greg said, we could also automate that check. | Same point as Greg only. | Building on others shows you listened and adds something new. |
| So my suggestion is a one hour test run on Thursday. Does that work for everyone? | That's all from my side. | A question invites a decision. A sign off invites silence. |
Model conversation
- Greg
- Okay, that's the plan for the release. Any thoughts before we move on?
- You
- Can I add something quickly, Greg?
- Greg
- Sure, go ahead.
- You
- My main point is that we should test on a copy of the client's data before Friday. Last sprint, staging hid two bugs that production found.
- Greg
- That's a good catch. How long would it take?
- You
- About an hour. I can set it up on Thursday morning, if that works for everyone.
- Greg
- Let's do it. Can you send me the slot?
- You
- Will do, right after this call.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.