Last week I met my dad for our semi-regular coffee date. It’s a chance for us to spend time together, catch up and talk about what is happening in the world. My dad has a PhD in Economics and teaches at a red brick university. Conversations with him are not meant to be comfortable. He operates in a space where orthodox thinking gets questioned as a matter of course - economics that crosses freely into philosophy, human behaviour, politics and the kind of anarchistic theory that makes you reconsider assumptions you did not know you had. I love it. It is one of my favourite kinds of challenge.
So when he spotted a T-shirt with the words 'never quit' on it recently and had some thoughts, I was not surprised. I hate that phrase too. We agreed, which is not unheard of, but it also felt worth writing down.
Because 'never quit' is not just an annoying motivational slogan. Applied without judgement, in business and beyond, it is genuinely dangerous. Between us, we covered three distinct versions of the same underlying truth: knowing when to stop is not weakness. It is one of the most underrated operational skills a business leader can develop.
The medical case
In clinical and physical settings, not quitting carries real risk. Continuing an ineffective treatment because stopping feels like giving up. Pushing through injury because rest feels like failure. The harm in these cases is visible and measurable. The body tells you. But in business, the equivalent signals are quieter and easier to rationalise away.
The sunk cost trap
Here is a scenario that will be familiar to more organisations than would care to admit it.
A business invests significant time and money implementing a project management platform. Six months in, it is not working. People are not using it properly. Work is becoming more fragmented, not less. Leadership knows this. The team knows this. Everyone, in some sense, knows this.
But the platform stays. Because so much has already been spent.
This is the sunk cost fallacy operating at full force. The money already spent is gone whether the platform stays or goes. The only financially rational question is: does continuing to use this create more value than stopping? In this case, the answer was clearly no. But the organisation kept going, and the operational cost of that decision, in disconnected work, wasted time and quiet team frustration, was higher than the original investment.
The business did not fail to quit because it lacked information. It failed to quit because quitting felt like admitting the original decision was wrong. Those are two very different things.
Assess early, decide deliberately, move on without guilt
There is a version of the fail fast principle that is worth applying seriously in operational decision-making. Not reckless trial and error, but the deliberate habit of building early assessment points into any significant initiative.
Before you commit fully, ask: at what point will we honestly evaluate whether this is working? What would tell us it is not? What would need to be true for us to change course?
These questions are simple. Most businesses do not ask them explicitly. And without them, the default setting is to keep going, because stopping requires justification and continuing does not.
The result is organisations carrying initiatives, tools, processes and even people beyond the point where the evidence supports them, because inertia is easier than decision-making.
Knowing your limits is a form of operational intelligence
There is a related point that deserves more credit than it usually gets. Recognising the limit of what you, your team or your current infrastructure can sustain is not defeatism. It is accurate self-assessment.
Businesses that overextend operationally, taking on more clients than they can serve well, launching more products than they can support, building more process than they can maintain, do not fail because they lacked ambition. They fail because they did not match their operational capacity to their commercial commitments.
Knowing your limits and working within them deliberately is what sustainable growth actually looks like from the inside.
What this means in practice
If your organisation regularly finds itself maintaining things that are not working, there are usually a few patterns worth examining:
- Decisions to continue are made by default rather than by review. Nobody is explicitly asking whether this is still the right call.
- Stopping feels politically uncomfortable. The person who championed the original decision is still in the room.
- There are no agreed criteria for what success or failure looks like. Without them, there is no clean point at which stopping becomes the obvious answer.
- Sunk cost language appears in conversations. Phrases like we have already invested so much in this are doing work they should not be doing.
None of this is unusual. These are normal human tendencies playing out in an organisational context. But they are operationally expensive, and they are worth naming clearly.
The Bloomfield view
Operational maturity is not only about building good systems. It is also about having the review discipline to recognise when something is no longer serving its purpose and the decision-making confidence to act on that honestly.
Businesses that build explicit review rhythms, with clear criteria for continuation and exit, spend less time and money carrying things that have stopped working. They also tend to move more quickly, because the decision machinery is already in place rather than having to be invented under pressure.
Persistence is a genuine virtue. But persistence without assessment is just expensive inertia.
Knowing when to stop is a skill. It deserves to be treated as one.