You Made a Decision in a Meeting. It Doesn't Count.

You close your laptop, feeling that rare wave of product manager relief. The debate is over. The VP of Engineering nodded, the lead designer said, “Makes sense,” and you all agreed to cut the vanity feature and focus on the core user flow. Decision made. Progress.

A week later, you ping the engineer for an update. “Hey, how’s the refactor of that user flow coming along?”

The response comes back. “Oh, were we doing that now? I thought we were just kicking around ideas. I’m still working on the vanity feature.”

Your stomach drops. That "decision" wasn't a decision at all. It was just a conversation that you happened to win. The momentum is gone. The alignment you thought you had was a mirage. The work never started because, in the minds of the team, the decision was never actually made.

Meetings don't produce decisions. People do. And if you don’t formalize the output, the default action for any busy person is no action.

Why Your "Decisions" Evaporate

This isn’t about blame. Engineers and designers aren't ignoring you on purpose. They’re drowning in context, meetings, and Slack pings just like you are. A verbal agreement is sand; it shifts and disappears.

Your decision evaporated because it fell into one of these traps:

• The Consensus Mirage: Everyone nodded along. But nodding isn't commitment. It's often just a signal for "I hear you and I don't feel strongly enough to argue right now." No one was asked to explicitly agree to an action.
• The Vague Next Step: The meeting ended with, “Okay, so someone from engineering will look into this.” Who is "someone"? What does "look into this" mean? A tech spec? A one-hour spike? By when? Ambiguity is where work goes to die.
• The Silent Disagreement: Someone in the room hated the idea but didn't want to cause conflict. They stayed quiet, assuming the idea would die a natural death. By not forcing a formal record, you gave them the out they were looking for.

A decision isn't real until it's written down, assigned, and communicated. It’s a deliverable, just like a PRD or a user story.

The Three Elements of a Real Decision

Stop treating decisions as conversational milestones. Start treating them as artifacts. Every real decision must have three parts, recorded immediately after the meeting.

1. The What: State the decision in the plainest language possible. No jargon, no backstory.
   • Bad: "Per our discussion, we're aligning on a strategic pivot to a more streamlined user experience."
   • Good: "We are cutting the 'Social Sharing' feature from the V2 launch. We will not build it."
2. The Who: Name the single individual responsible for the very next action. Not a team, not a group. A person. Accountability cannot be shared.
   • Bad: "The front-end team will scope the work."
   • Good: "Anna is responsible for creating the JIRA tickets for the V2 work, removing the social sharing epics."
3. The When: Give the owner a deadline. The next action needs a specific timeframe.
   • Bad: "Anna will get to this sometime next week."
   • Good: "Anna will create the tickets by Tuesday, May 28th, at 5 PM."

This isn't micromanagement. It's clarification. You are removing all ambiguity so your team can execute with confidence.

Your 5-Minute Post-Meeting Workflow

Making a decision real doesn't require a new process or another tool. It takes five minutes of discipline directly following the meeting.

Step 1: Open a Doc. Write It Down. Before you get pulled into anything else, open your team’s source of truth (Confluence, Notion, Coda) and write down the decision using the What, Who, and When framework. This is non-negotiable.