After a cancellation that turned on circumstances, a team keeps the project alive on discretionary time and budget, so when the decision is revisited it returns as a working prototype that is cheap to approve.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
When a specialty chemicals company cut its development budget to fund an acquisition, a water-based industrial coating that had passed early lab trials was canceled. The lead chemist had a standing allowance of ten percent of her group's lab time for exploratory work, and she used it. With her director's knowledge, two chemists kept refining the formulation one afternoon a week, logged the hours under the exploratory code, and kept the supplier samples current. Eighteen months later a large customer asked for a low-solvent coating to meet its own emissions targets. The lead chemist brought the director a formulation that had already passed adhesion and cure testing, with a cost model and a pilot plan. The capital committee approved a three-month scale-up in one meeting, where the original proposal would have needed two years.
Why it works
Work done while a project is officially stopped changes what decision-makers are asked to approve. A speculative idea becomes a working prototype with the effort already absorbed, so the project looks better at the next decision point. It also becomes cheaper to approve: the code or formulation exists, the team's knowledge is warm, dependencies are current, and most of the cost of revival has already been paid. It depends on real discretionary slack, on a cancellation that turned on circumstances (a reversed strategy opens a window, a rejected principle does not), and on strategy or leadership cycles long enough to bring the question back.
The thinking behind it
Avinash K. Dixit Dixit and Pindyck's Investment under Uncertainty (1994) treats an investment that is hard to reverse as an option: a firm that can delay keeps the value of waiting for better information. A canceled project kept alive on discretionary time is a small, cheap option on its revival. When the customer request or the new strategy arrives, the company can exercise it in one meeting, because most of the learning has already been paid for.
Hal R. Arkes Arkes and Blumer's The Psychology of Sunk Cost (1985) describes the sunk cost effect, a greater tendency to continue once money, effort, or time has gone into an endeavor, partly to avoid appearing wasteful. It names the risk on both sides of a ghost project: the team may keep going because it has already invested, and approvers may overrate a prototype because effort is visible in it. Asking whether the reason for the cancellation has changed keeps the move honest.
When it fits
Belief comes first: you think the project still has value, the cancellation was about timing, money, or a strategy that may turn, and you control discretionary time or budget you are allowed to spend on exploration. You need a small team that still believes in the work and a revival window that is plausible within a year or two. A principled rejection is a different situation, and this does not fit it.
How to use it well
Look hard at the cancellation first: if leadership rejected the idea itself, stop, and if it rejected the timing or the cost, note what would have to change for the answer to change.
- Use only time and money that are yours to allocate for exploration, recorded under their real codes, and tell your own manager what you are doing.
- Keep it small: preserve the knowledge, the materials, and the dependencies, and take the work only as far as a credible prototype.
- Watch for the conditions that would reopen the question, such as a customer request, a new strategy, or a change of leadership.
When the window opens, bring the prototype, a cost model, and a scaled pilot to the forum that made the original decision, and ask it again.
What it costs and where it backfires
Slack spent on the work could have gone elsewhere, and the people doing it keep investing in something the organization has said no to. If the work is discovered and looks hidden, you lose credibility with the leaders who canceled it, a small chance of a large cost. If the cancellation was principled, persisting reads as defiance. Once the hours are billed to unrelated budget lines to keep them out of view, this stops being persistence and becomes misreporting.
When it is used on you
Projects you canceled can keep running. When the team stays together and commits, samples, or other artifacts keep appearing under other budget lines, the work is continuing. If you mean the decision to be final, remove the slack: reassign the people and close the budget lines. Then hear the believers' case directly, because a formal cancellation alone does not stop work that people believe in.