If We Do This, What Stops?
The second question overloaded organisations forget to ask
THE ARGUMENT, IN SHORT Every organisation asks whether a new thing is worth doing. Almost none asks what will stop in order to make room for it. A decision that adds without subtracting is not a decision, it is a wish. This is a rule you can start applying this week, in meetings you already attend, without anyone's permission.
Four minutes.
The Big Idea in this edition ends with one instruction: see the total. Every programme, every change, every governance requirement, every standing commitment currently live in your organisation, on one page, including the paused and the nearly finished and the ones with nobody's name against them.
That exercise tells you the weight. It does not stop it growing. By the time most teams have finished counting, two more things have arrived.
So here is the rule that holds the line.
The decision that was never finished
Watch what happens when something new arrives in a leadership meeting. Somebody presents it. The logic is sound, the market context is real, the customer need is genuine. People ask about cost, about timing, about who will own it. Then somebody says yes, and everybody moves on to the next item feeling that a decision has been made.
One question was never asked.
Not should we do this. That question got a thorough answer and the answer was defensible. The missing question is the one that determines whether the answer means anything.
If we do this, what stops?
When the answer is nothing, no decision has actually been made. What has happened is an addition to a system that was already full, with the consequences left unallocated. Somebody downstream will absorb them, invisibly, by working longer or by quietly letting something else slide. The organisation will not learn which, because nobody named it at the point of decision.
An incomplete decision does not fail immediately. It fails later, somewhere else, to somebody else. Which is precisely why the connection is so rarely made.
Why the first question alone is dangerous
Should we do this is a question about merit. It gets asked well in most organisations, by intelligent people who genuinely interrogate the business case.
The trouble is that merit is not the constraint. Almost everything an overloaded organisation is carrying has merit. That is how it got in. Nobody signs off nonsense. They sign off ten sensible things in a system with capacity for four, and then wonder why none of them lands properly.
Judging each new thing on its own merits, one at a time, is exactly the mechanism that produces overwhelm. The question performs rigour while ignoring the only variable that matters, which is whether the system has anywhere to put it.
Merit tells you whether something deserves to exist. Capacity tells you whether it can.
Using this when you do not set the agenda
Here is what makes this rule useful to you specifically, if you are the one absorbing decisions rather than making them.
You do not need authority to ask a question. You need authority to say no, and most people reading this do not have it. Asking what stops requires nothing except being in the room.
It also cannot easily be read as resistance, which matters enormously, because the cost of being heard as obstructive is high and you have probably paid it before. Asked in the right register, what stops is not a refusal. It is a request for completion. You are not questioning whether the thing should happen. You are trying to deliver it properly, which is a position nobody can reasonably object to.
The register is everything. Some versions that work:
That makes sense. To land it properly, what would we take off the team to make room?
Happy to pick this up. Of the four things we committed to last quarter, which one moves?
I can do this by the date you need, or I can do the migration by the date you need. Which would you rather have?
That last one is the most powerful sentence in this article. It is not a complaint, it is not a capacity plea, and it contains no grievance. It is a straightforward offer of two real outcomes, which hands the trade-off back to the person with the authority to make it. Most of the time they had no idea a trade-off existed.
The four honest answers
When somebody does engage with the question, there are only four legitimate responses. Knowing them makes the conversation faster.
Something stops. Named, dated, and communicated to the people working on it. The cleanest answer and the rarest.
Something pauses properly. Genuinely stopped, resources released, a date to revisit it. Not the thing organisations usually call a pause, which is a project left breathing in the corner, still consuming attention and still appearing on a report.
Something shrinks. The scope comes down, the ambition is honestly restated, and the new version is the version people are now held to.
Something slips. A date moves, and the slip is announced rather than discovered in six weeks.
What is not on that list is the answer most people give, which is that everything continues and this is added on top. That is not a fifth option. It is the absence of a decision, wearing the clothes of one.
What to do when the answer is nothing
Sometimes you will ask and be told, in effect, to find a way. It happens, and it is worth being honest that a single well-framed question does not always change the room.
Two things are still true.
You have converted an invisible problem into a stated one. Before you asked, the overload was a feeling in your team. Now it is a position somebody has taken on the record, in front of witnesses, which is a materially different thing when the consequences arrive.
And you have gathered real data. Not about workload. About how your organisation responds when someone reports the truth about capacity. That response tells you something important, and it is a subject I will be taking up in full.
The one thing to take into your next meeting
You do not need to run an exercise or introduce a framework. Take one sentence.
If we do this, what stops?
Ask it about the next new thing that arrives, in the meeting where it arrives, in front of the people deciding. Ask it warmly and without edge, as though you are simply finishing the thought everybody else has started.
The first time, it will change the temperature of the room for about four seconds. Somebody will laugh. Somebody else will say that is a fair question.
The tenth time, it will be how your organisation makes decisions.
This rule is the front door to a wider pattern. Read the full entry on Drag in the Pattern Library.
This is one of a growing set of tools built for leaders working inside real constraints and usable without waiting for permission. Find them in The Toolkit →
If the total you counted this month is heavier than anything one rule can fix, that is worth an honest conversation with someone outside the system. Here is how I work →
Blood Sweat and Business publishes one theme a month, examined from three angles. Subscribe to The Log for each edition, and the thinking behind why I chose it.
