A conversation needs a bridge.
A productive meeting can still leave a team with very little to act on. People heard the same conversation, but they may have left with different interpretations of the decision. The useful work happens when someone builds a bridge between the conversation and the next action.
Name the action, not just the topic.
“Website feedback” is a topic. “Consolidate homepage feedback into one review document” is an action. The second version tells someone what to do and gives the rest of the team a way to recognize completion.
Give it an owner and a reference.
A task needs one person responsible for moving it forward, even if several people contribute. It also needs the right context: the design link, the feedback thread, or the relevant recording. Without that context, the next step often becomes another request for information.
Keep questions visible.
Not everything needs to become a task immediately. Some points are unresolved questions or decisions waiting on a stakeholder. Labeling them honestly prevents the team from treating an assumption as an agreement.
Try this after your next call.
Write four lines: what we decided, who owns the next action, what they need to do it, and when we will check again. A short, specific summary is often more useful than a complete retelling of the meeting.
Continue on Substack ↗