Move to Action (Decision-Making Methods)
Dialogue without decisions is just conversation — clarify who does what by when
Move to Action addresses the gap between having a productive dialogue and actually doing something about it. The authors observed that many crucial conversations fail not because the dialogue was poor but because the conversation ended without clear decisions, assignments, or follow-up. Two specific failures are common: people have different assumptions about how decisions will be made, and people do not convert decisions into specific actions with clear ownership and deadlines.
The framework introduces four decision-making methods — Command, Consult, Vote, and Consensus — and provides criteria for choosing among them. Command decisions are made by one person without involving others (appropriate when authority is clear or time is short). Consult decisions involve gathering input from stakeholders before one person decides. Vote is appropriate when efficiency matters, options are clear, and everyone can support whichever option wins. Consensus means everyone must agree — it produces the highest commitment but takes the most time and should be reserved for high-stakes decisions where universal buy-in is essential.
Once the decision method is clear and a decision is made, the framework requires converting it into specific assignments: Who does what by when? And how will we follow up? Without this explicit conversion, conversations produce the illusion of agreement but no actual change. The authors stress that unclear assignments after dialogue are the number one reason that crucial conversations fail to produce results.
- Dialogue without decision is wasted effort — every crucial conversation should end with clear next steps
- Ambiguity about how decisions are made causes as much conflict as the decisions themselves
- Choose the decision method (Command, Consult, Vote, Consensus) explicitly and before the discussion
- Every decision must be converted into specific assignments: who does what by when
- Follow-up is not optional — without it, commitments dissolve
- Do not use consensus when a simpler method would suffice — it wastes time and energy
- Determine the decision-making methodBefore or at the beginning of the discussion, clarify how the decision will be made. Will one person decide (Command)? Will input be gathered before one person decides (Consult)? Will the group vote? Will you require full consensus? Making this explicit prevents later conflict about process.
- Make the decisionUse the agreed-upon method to reach a decision. Draw on the pool of shared meaning that was built during the dialogue. If new information surfaces that changes the equation, it is acceptable to revisit the method. But do not loop endlessly — make the call.
- Convert the decision into action itemsSpecify exactly who will do what by when. Do not accept vague commitments like 'We'll look into it' or 'Someone should handle that.' Assign named individuals, specific actions, and concrete deadlines. Write these down so everyone has the same understanding.
- Establish follow-up mechanismsAgree on how and when you will check on progress. Set a follow-up meeting, establish a reporting schedule, or create a shared tracking document. Without follow-up, even the most specific assignments drift. The method of follow-up should be proportional to the stakes.
A leadership team noticed that the same topics kept resurfacing at monthly meetings. Each time, they had a productive discussion but never explicitly decided anything. They implemented Move to Action by adding a standing agenda item at the end of each meeting: 'What did we decide? Who does what by when? When will we check progress?' They also began specifying the decision-making method at the start of each topic.
The authors noticed a frustrating pattern in their consulting work: organizations would invest in crucial conversation training, people would learn to dialogue effectively, and then... nothing would change. Upon investigation, they found that conversations were ending ambiguously. People walked out of meetings with different understandings of what was decided, who was responsible, and when things needed to happen. The Move to Action framework was developed to close this execution gap.