The pricing decision had already been waiting for three weeks when the leaders found themselves talking about it again.
It was Monday morning, and the issue mattered. Sales needed the new price for the Q4 bundles before the campaign could move. Finance had concerns. Sales had its own view. There were reasonable questions to answer, and nobody in the room appeared unwilling to do the work. Yet as the conversation continued, the decision remained exactly where it had been before the meeting began: unresolved.
Eventually, someone suggested that they discuss it again the following week.
That suggestion did not sound irresponsible. In fact, postponement often arrives dressed as responsibility. Another week gives you more time to check the numbers, consult someone else, reduce the risk, and avoid forcing a decision before everyone feels ready. When the stakes matter, asking for more time can seem like the mature thing to do.
But this decision had already received three weeks.
And while the leaders were protecting themselves from making the wrong decision, something else was happening. Sales could not move. The Q4 campaign remained pending. People downstream were waiting for a decision they did not have the authority to make themselves.
That is what makes delayed decisions difficult to see clearly. The people in the meeting experience the delay as caution. The people waiting outside the meeting experience it as stopped work.
What Are We Protecting?
I have learned not to assume that leaders postpone because they are lazy, indecisive, or afraid of responsibility. Those explanations are sometimes convenient, but they rarely help us understand what needs to change.
A more useful question is: What are we protecting?
A Finance leader may be protecting the company from a pricing mistake. A Sales leader may be protecting customer relationships or a revenue target. Someone may be protecting credibility because making a decision creates the possibility of being proven wrong. Another person may want to preserve options because once a choice is made, some doors close.
Even harmony can become something we protect. As long as the conversation continues, disagreement can remain polite and unresolved. A decision eventually requires somebody to say, “This is what we are going to do,” knowing that not everybody may prefer the choice.
I cannot say what every person in that room was protecting. But the pattern matters because postponement is rarely empty. When we continue doing something that is clearly costing us, there is often some benefit, safety, or protection hidden inside the familiar move.
That is why telling leaders to “be more decisive” is usually not enough. If postponement is serving a purpose, exhortation does not remove that purpose.
More information can sound prudent. More consultation can sound collaborative. Another meeting can feel safer than making the wrong call. The familiar move makes sense.
But safety has another side. A decision can protect us from one risk today while quietly creating another risk somewhere else. Sometimes the safe decision becomes dangerous because the cost of continuing to wait keeps accumulating.
In this case, the cost was already visible. Sales was waiting. The campaign was waiting. Time was passing whether the leaders decided or not.
The Conversation Needed a Different Job
Later, during the workshop, we practised a very simple move. It was not a decision-making model with multiple boxes, weighted criteria, and a new vocabulary everyone had to memorize. Those approaches have their place, particularly when a decision is genuinely complicated. But this team did not appear to have a shortage of analysis.
They had a shortage of closure.
So we used three questions:
What’s the decision? Who owns it? By when?
The questions look almost too simple when written on a page. Their usefulness comes from what they force people to make visible.
“What’s the decision?” stops a meeting from treating a subject as if the subject itself were the work. People can discuss pricing for an hour without being clear about what must actually be decided. Naming the decision creates a boundary around the conversation.
“Who owns it?” separates participation from responsibility. Ten people may have valuable information. Ten people may be affected. But if everyone leaves believing the decision belongs vaguely to “us,” it may belong to nobody once everyone returns to ordinary work.
And “By when?” removes the comfortable ambiguity of soon, ASAP, and let’s follow up. A decision without a point in time can survive another meeting remarkably easily.
We practised the questions before returning to the real issue. That mattered. A useful idea is not proven because people nod when they hear it. It becomes useful when someone can employ it in the situation where the familiar behavior normally takes over.
After lunch, the pricing issue came back into the room.
This time, instead of reopening the entire discussion, we changed the questions.
What’s the Decision?
The question was not, “What do we think about the pricing proposal?”
That could easily have produced another round of explanations. It invites everybody to contribute, which can be useful, but contribution was not what this situation lacked. People had already contributed.
The question was more specific:
What decision has to be made so the work can move?
The answer became clear. They needed to set the new price for the Q4 bundles.
That sounds obvious when you read it now. Yet this is one reason meetings can become surprisingly long. People discuss a topic without forcing themselves to name the decision hiding inside it. Once the decision is named, information can finally be judged by whether it helps make that choice.
The room now had something it could finish.
Who Owns It?
The Finance lead and the Sales director owned the decision.
That did not mean other people’s views no longer mattered. Ownership is not the same as dictatorship. Other people may have information, experience, objections, or consequences worth considering.
But somebody still has to carry the decision.
This becomes especially important in organizations that value collaboration. We rightly want people involved. We ask for opinions and create space for discussion. But collaboration can accidentally blur accountability when involvement becomes confused with ownership.
A decision everybody helped discuss can still be a decision nobody feels responsible for finishing.
Naming the owners changed that.
By When?
The answer was 4:00 PM that day.
The deadline did not suddenly make the pricing decision important. It had been important for three weeks. What the deadline did was give that importance a place in reality.
That is what I mean by making what matters urgent. Urgency does not always mean panic, emergency, or rushing without thought. Sometimes responsible urgency simply means refusing to wait for a crisis before something important receives a real commitment.
Now the pricing issue was no longer floating around the organization. It had become something concrete: a specific choice, owned by specific people, with a specific point at which the waiting would end.
The conversation continued, but its purpose had changed. People were no longer trying to keep every concern alive. They were helping the owners get what they needed to make the decision.
Within 17 minutes, it was done.
The pricing decision that had been waiting for three weeks moved.
The Real Result Was Not 17 Minutes
The contrast makes an attractive headline: three weeks versus 17 minutes.
But speed was not the most important result.
The real result appeared in what could happen next. Sales now knew the price. The Q4 campaign moved from pending to launching that week. People who had been waiting could continue their work. A decision that had occupied repeated conversations became something the organization could finally act upon.
That is the distinction I want leaders to notice. A meeting may contain plenty of activity without creating movement. People can contribute intelligently, listen respectfully, ask excellent questions, and leave believing they had a productive conversation.
The harder question is:
What became different because we met?
In this case, the answer was visible. The decision was made. The owners were clear. Sales could move. The campaign could launch.
Those are stronger measures than whether the discussion felt productive.
But the Old Move Was Still Waiting
One successful decision would have made a good workshop story, but it would not yet have changed the way the organization worked.
The old pattern was still available. In the next difficult meeting, someone could once again suggest gathering more information, consulting another stakeholder, or returning to the issue the following week. Those suggestions might even be appropriate. Sometimes postponement is exactly the responsible choice.
The problem is postponement by habit.
So the team moved the three questions out of the workshop and into the place where the old behavior normally happened. They added them to their meeting agendas.
That small change mattered because they were no longer depending only on leaders remembering a workshop lesson. They began to change the environment that had been rewarding the old game. The meeting itself now reminded people that an important discussion should eventually produce a decision, an owner, or a deliberate reason for not deciding yet.
They also introduced a simple scoreboard. Instead of counting a meeting as successful because the agenda had been covered or everyone had participated, they began making movement visible.
The early scoreboard told a simple story:
Decisions made: 2
Owners named: 2
Delay cleared: 3 weeks
Time to decide: 17 minutes
The scoreboard changed what the meeting counted as a win. That matters because changing the score can matter as much as changing the strategy. What we count quietly teaches people what winning looks like.
Those numbers did not prove that the organization had transformed. They proved something more modest and more useful.
A different move had produced a different result.
That was enough reason to keep practising it.
Try the 3-Question Play
You do not need to redesign every meeting to try this.
Think of one issue that has already appeared in more than one conversation. It matters enough that people keep discussing it, but somehow the work is not moving.
Before scheduling another discussion, ask:
What’s the decision?
Try to put it into one sentence. What exactly needs to be approved, rejected, chosen, changed, started, stopped, or committed to?
If nobody can name the decision, you may already have discovered why the conversation keeps growing.
Who owns it?
Do not ask only who cares about the issue or who needs to be consulted. Ask who has the responsibility and authority to carry the decision to completion.
Participation matters. Ownership must still become visible.
By when?
Give the decision a real date or time that makes sense for the people whose work depends on the answer.
“Soon” is not a commitment. “We will follow up” is not a deadline.
And if the same decision keeps returning despite those three questions, go one level deeper:
What are we protecting by postponing this?
Do not use the question as an accusation. Use it to understand why the familiar move still makes sense.
Perhaps there is a legitimate risk that has not been addressed. Perhaps an important voice is missing. Perhaps the owner lacks authority. Perhaps the organization punishes failed decisions so severely that postponement feels safer than choosing.
If the protection is legitimate, deal with it.
If the protection is simply keeping everyone comfortable while the cost of delay keeps growing, make that visible too.
Follow the Proof
Do not judge the play by whether people like the questions.
Watch what happens afterward.
Does a decision that has been circling finally get made? Does someone clearly know what they own? Can the people waiting downstream continue their work? Does the issue disappear from next week’s agenda because it has actually been resolved rather than merely postponed again?
And over time, watch for something even more important: Can the team make this move without somebody reminding them?
That is when a useful question begins to become a practice.
The lesson I carried from that pricing decision was not that every three-week delay can be solved in 17 minutes. Some decisions deserve weeks of investigation. Some deserve patience because the cost of moving too quickly is much greater than the cost of waiting.
The lesson is simpler.
When something important has been postponed again and again, do not assume another discussion is automatically progress. Look at the familiar move. Ask what people are protecting. Name the decision that actually has to be made, put ownership where it belongs, and decide when the waiting should end.
Then follow what happens.
Because the goal is not to make meetings shorter.
The goal is to make what matters move.