A team can spend plenty of time talking and still leave with different ideas about what happens next. The problem is often missing context: one person is discussing a deadline, another is questioning the scope, and a third is waiting for a decision nobody knows they own.
Before scheduling a conversation, write down what you need from it. That small act can reveal whether you need a meeting, a written update, or one clear question to the right person.
Separate an update from a decision.
An update tells people what has changed. A decision asks them to choose a direction. Mixing the two can make a conversation harder to follow.
For an update, share the current state, what moved since the last update, and anything that needs attention. For a decision, explain the question, the practical options, and the tradeoff that matters. Make it clear who will make the final call.
Give people enough context to respond without asking them to read an entire project history. A short explanation with a link to supporting detail is often a useful starting point.
Make the request explicit.
“Any thoughts?” leaves a lot for the reader to work out. Are you looking for approval, a technical concern, or a different idea? Does silence mean agreement?
A more specific request could be: “Please flag anything that makes this scope unrealistic by Thursday. After that, the project owner will confirm what we are taking forward.” The example matters less than the structure: say what kind of response is needed, when it is needed, and what happens after.
Shared context gives a conversation somewhere useful to begin.
Use the conversation for the difficult part.
Some things deserve time together: a sensitive disagreement, a complicated tradeoff, or a problem the team needs to explore. Written context can help people arrive ready to discuss those things.
Close the conversation by recording the decision and the next action. Include the reason when it will help someone understand the choice later. If the team could not decide, record the missing information and who will find it.
Try this with one recurring meeting. Send a brief note beforehand with the context and the question to resolve. Afterwards, share a short decision record. Ask the team whether the change made the conversation easier to follow, and adjust from there.
More ideas for the work ahead.
Explore the blog