A team agrees in advance to seek consensus by a set date and, failing that, to let the accountable executive decide with everyone's input on record, which ends stalling by holdouts.
An example
Usage-based pricing, in place of per-seat licenses, had been on the agenda of a mid-sized software company's executive team for two quarters. Every meeting produced more questions, and the head of customer success, warning that renewals would suffer, asked for more analysis each time. The chief revenue officer, who owned pricing, proposed a rule: the team would try to reach agreement by the end of the month, and if it could not, she would decide, after hearing everyone's views and putting them in writing. The team agreed. Over the next three weeks each executive submitted a short position. The head of customer success laid out the renewal risk with numbers, and the chief revenue officer built a two-year price protection for existing customers into the plan. Full agreement did not come. She decided on the date, and the new pricing launched the following quarter.
Why it works
Pure consensus gives every member a veto, so one holdout can stall a decision indefinitely by asking for more. Agreeing in advance that the accountable executive decides if consensus fails by a date makes approval easier, because a decision will now happen, and it makes holding out costlier: a member who blocks without reasons loses influence, while one who makes a clear case gets heard and can change the plan. It depends on an executive the group accepts as the decider, on a real attempt to agree first, and on the group's input shaping the final call.
The thinking behind it
Kathleen M. Eisenhardt Eisenhardt's Making Fast Strategic Decisions in High-Velocity Environments (1989) found that most fast decision-making teams tried for consensus by involving everyone, and when they could not agree, the senior executive decided, guided by the team's input, which kept conflict from stalling the decision. The evidence is case studies of eight firms in one industry and has not been tested on a larger sample, but the pattern matches the page's rule closely.
When it fits
Teams that decide together but keep stalling are the setting: executive teams, product councils, cross-functional committees. There must be an accountable executive with clear authority over the question and a group willing to accept the rule in advance. It works better on recurring kinds of decisions, where the rule can become standing practice.
How to use it well
Propose the rule before the decision is stuck, or at the moment it sticks, and propose it for the whole team. State the date and who decides if agreement fails.
- Ask each member for their position in writing, with reasons.
- Make a real effort to reach agreement, and change the proposal where the objections are good.
- If the date passes without agreement, decide, and explain the decision in terms of the input.
- Record the dissents.
The rule protects the decider only if the consultation is real. Use it to end stalling, and expect some objections to change the plan.
What it costs and where it backfires
Members who lose may feel the consultation was a formality, especially if the decider's view was known from the start. A decision made over strong objections still has to be carried out by the people who objected. If the decider falls back on the rule often, the team stops trying for agreement. The method is clean while the attempt at agreement is real. A date so close that nobody can make their case, or a decision taken before the input is heard, turns it into a pretext.
When it is used on you
Put your case in writing early, with numbers, if your team adopts this rule and you hold the minority view, and propose the changes that would win your agreement. A clear written position does more to shape the decision than continued objection. If the decision goes against you, ask for your view to be recorded.