The 7 signs your decision is stuck
1) You cannot say the decision in one sentence
If the 'decision' is actually a topic, a project, or a vague outcome, it is hard to land.
Test: Can one person write the decision statement without qualifiers?
Example: 'Do we consolidate endpoint protection onto one platform by June, yes or no?'
2) The inputs are messy, contradictory, or incomplete
Teams often argue because they are using different facts, different time horizons, or different definitions.
Watch for duelling spreadsheets, unclear baselines, and debates that start with 'It depends...'
3) People are debating solutions, but avoiding the trade-off
Most stuck decisions are not stuck on options. They are stuck on an unspoken trade-off.
Common trade-offs in B2B SaaS and cybersecurity include:
- speed to reduce risk vs operational simplicity
- best-of-breed capability vs standardised coverage
- short-term cost vs long-term control
- central governance vs team autonomy
4) The stakeholder set keeps changing
If the room is different each week, the decision will keep resetting.
Signal: 'We need to bring in... ' becomes the default move.
5) Ownership is fuzzy
If nobody is clearly accountable for landing the decision, everyone participates but nobody drives.
Signal: lots of 'we should' and 'someone needs to', with no named owner and date.
6) Incentives are pulling in different directions
Security wants risk reduction. Engineering wants delivery velocity. Finance wants predictability. Sales
wants flexibility.
All valid. But if nobody names the tension, it leaks out as delay.
7) Delay is being used as risk management
Sometimes 'we need more data' is code for 'I do not want to own the call'. Delay feels safer than being wrong.
Signal: the cost of waiting is never written down, so nobody feels it.
What most teams do that makes it worse
When a decision starts looping, the default reaction is to add another meeting, add more pre-reads,
widen the stakeholder group, or ask for more analysis.
This increases activity, but it does not reduce friction. More discussion rarely creates clarity. It usually creates more angles to disagree.
A simple reset you can run in 30 minutes
If a decision is looping, try this before you schedule anything else:
1. Step 1: Write the decision statement
One sentence. Yes/no or option A vs option B.
2. Step 2: Name the trade-off
Finish this sentence together: 'We are choosing to optimise for xxx
over xxx' .
If you cannot complete that line, you are not ready to decide yet. That is fine. It just means the work is clarifying, not debating.
3. Step 3: Lock the stakeholder set
Who needs to be in the decision, and who simply needs to be informed? Write it down.
4. Step 4: Assign an owner and a decision date
Not 'next week'
- a date. Put a name next to it.
5. Step 5: Write the cost of delay
One line: 'If we do not decide by X, the cost is Y.'
Y can be delivery slip, customer risk, security exposure, morale, or revenue. It just needs to be explicit.
A quick example
A security leadership team I worked with spent six weeks circling a 200k GBP decision around endpoint security and incident response coverage.
The debate kept looping on: 'Do we consolidate onto one platform, or keep best-of-breed tools?'
When we sat down properly, it took about twenty minutes to realise the real question had not been asked.The real question was: 'What matters more right now, consistent coverage and simpler operations, or maximum capability even if it adds complexity?'
Once that trade-off was on the table, the decision landed within 24 hours.
They were not stuck on the tools. They were stuck on the trade-off they had not named.
If this resonates
If you have a decision that keeps looping,
send me:
- what the decision is (one sentence)
- who is involved
- what happens if it slips another month
I will reply within 48 hours with a quick diagnosis and whether a Decision Sprint or Alignment Sprint would help.
Justin
Founder, The Exec Memo
