Sunk cost and genuine belief are difficult to tell apart from the inside
When a project is failing, the question of whether to stop or restructure is rarely straightforward. The investment already made — time, money, reputation, other people's effort — creates pressure to continue even when the evidence points the other way.
That pressure is not irrational. Stopping carries its own costs: the appearance of failure, the impact on people who have contributed, the loss of what has been built. But continuing a project that cannot work compounds those costs rather than avoiding them.
The decision requires separating what has already been spent — which cannot be recovered regardless of what happens next — from what is still ahead. Pairwise comparison makes that separation easier by examining each factor directly rather than letting sunk cost dominate the whole evaluation.
Why the project is failing — and whether that changes the decision
The reason for failure matters because it determines whether restructuring is a realistic option
Execution failures can often be corrected. Fundamental problems with the goal or the conditions usually cannot.
A project can fail for reasons that are genuinely fixable — poor sequencing, the wrong people in the wrong roles, insufficient resource at a critical stage, or a communications breakdown that created problems which could be resolved. These are execution failures, and restructuring to address them directly can produce a different outcome.
A project can also fail for reasons that restructuring cannot fix — the original goal was wrong, the market or context has changed, the core assumption it was built on has not held up, or the level of resource required to succeed is simply not available. In these cases, restructuring extends the project without changing its trajectory.
Identifying which category the current failure falls into is the most important question at this stage — and it is the one most often avoided because the answer is sometimes unwelcome.
Whether a second attempt is genuinely warranted
Restructuring is only worth doing if the underlying case for the project still holds
A restructured project that addresses symptoms rather than causes tends to arrive at the same outcome more slowly.
The case for restructuring rests on two things being true simultaneously: the core idea is still sound, and the specific reasons for failure are genuinely addressable. If either of those is not true, restructuring is likely to extend a difficult situation rather than resolve it.
The pull toward restructuring is often partly driven by the desire to avoid the conversation that stopping requires — with funders, team members, stakeholders, or simply with oneself. That is understandable. But it is worth separating the question of whether restructuring is the right strategic decision from the question of whether it is the more comfortable one.
If the honest answer is that restructuring is genuinely warranted, it needs to be done with a clearly defined scope, a realistic assessment of what will be different, and an agreed point at which the assessment is repeated.
When honesty and obligation pull in different directions
The obligation to people who have contributed and the obligation to be honest about what the evidence shows are both real
Continuing a project that cannot succeed does not honour the people who have contributed to it — it extends the period in which their effort goes toward something that will not work. Stopping, when done clearly and with proper acknowledgement of what was built and learned, is often a more respectful outcome than prolonged failure.
The priority that needs to lead this decision is not which option feels more comfortable or which one requires the harder conversation. It is which one is most honest about what the evidence is showing — and which one protects the capacity, relationships, and resources needed for whatever comes next.
The three positions this decision can realistically resolve into
A clear decision in any of these directions is better than continued uncertainty
Stopping and closing properly means ending the project with clarity — acknowledging what was built, what was learned, and what did not work. Done well, this is not failure. It is the honest conclusion of a process that ran as far as it could, and it frees the people and resources involved to go somewhere more productive.
Restructuring with a clearly defined second attempt means committing to a specific set of changes, a realistic timeframe, and an agreed assessment point. It is only worth doing if the underlying case is still sound and the reasons for failure are genuinely addressable. Restructuring without those conditions in place is usually just a delayed stop.
Pausing formally to reassess means neither decision is clear enough yet, and that forcing one now risks making the wrong call. This is only useful if the pause has a defined end point and produces new information that genuinely changes the evaluation.