> ## Content Index > Fetch the complete content index at: https://www.wendypage.digital/llms.txt > Use this file to discover other available public pages before exploring further. # A pilot does not need to proceed to be successful - URL: https://www.wendypage.digital/a-pilot-does-not-need-to-proceed-to-be-successful/ - Published: 2026-10-08T22:09:12.000Z - Updated: 2026-10-08T22:25:27.000Z - Description: A genuine pilot reduces uncertainty and risk. Sometimes the smartest outcome is to proceed. Sometimes it is to change direction. And sometimes it is to stop. - Author: Wendy Page - Tags: Digital Decisions, Digital Leadership If every pilot is expected to proceed, it is not really a pilot. It is a rehearsal. The purpose of a pilot is not to prove that something should move into production. It is to reduce uncertainty and risk before a larger commitment is made. A pilot should help us understand what we are really dealing with. Whether the idea works in practice. Whether the data is good enough. Whether the people it is intended for find it useful. Whether the costs, dependencies and consequences are acceptable. Whether it is fit for purpose. A genuine pilot should be able to end in one of three ways: - With the confidence to proceed - With a decision to change direction - With a decision to stop. That last outcome is often the hardest one to accept. ## **When momentum starts making the decision** By the time a pilot reaches its decision point, it is rarely just an experiment anymore. People have backed it. Time has been committed. Someone has sponsored it. Teams may have demonstrated it internally or talked enthusiastically about what it could become. That creates momentum. And momentum can quietly change the question. Instead of asking, “What did we learn, and what should we do with that information?” the organisation starts asking, “How do we keep this moving?” Those are not the same question. Perhaps the tool works, but not well enough for the job. Perhaps the data required to support it is unreliable. Perhaps the operating cost is higher than expected. Perhaps users don’t yet see the value. Perhaps implementation would introduce more complexity than the problem warrants. Those findings do not mean the pilot failed. They are exactly the sort of things a pilot is supposed to uncover before the organisation commits more money, more time and more reputation to the idea. The difficult part is saying so. If the people closest to the work believe that recommending “stop” will be interpreted as failure, they have a powerful incentive to soften what the evidence is telling them. Or not say it at all. A weak result becomes “promising with further development.” A poor fit becomes “an opportunity to refine the use case.” A status that should be red stays amber. And sometimes the strongest concern never appears in the project record at all. It is shared quietly in corridors, side conversations and one-to-ones while the formal reporting continues to imply that the work is broadly on track. That is not transparency. And it makes a decision to stop much harder, because the organisation is no longer working with the full picture. ## **Expect the answer to change** A pilot should be expected to change the shape of the answer. That is one of the reasons we run one. The original estimate may no longer hold. The delivery path may need to change. The scope may narrow, or an anticipated risk may prove easier to manage than expected. The team may uncover dependencies, costs or opportunities that were not visible at the start. A pilot can change more than our view of the solution. It can also challenge the assumptions around it. A deadline thought to be fixed may prove negotiable. A dependency thought to be critical may be removed. A risk thought to be unavoidable may prove manageable. That is the pilot doing its job: replacing assumptions with evidence. Leadership has a role here too. People need permission to bring back an answer that is different from the one everyone hoped for. If new information is treated as failure, teams learn very quickly to soften it, delay it or work around it. A genuine pilot therefore needs more than a stop gate. It needs leaders who are willing to hear: “What we know now is different from what we knew then, and the plan needs to change.” ## **A genuine pilot ends in a decision** The question is not, “Did the pilot make it into production?” The better question is, “Did we learn enough to make a sound decision about what happens next?” ![Pilot learnings leading to a decision point with three outcomes: proceed, change direction or stop.](https://storage.ghost.io/c/6f/bb/6fbbede7-d925-45f2-b43b-2e6dfda04bd3/content/images/2026/10/2026-15-Pilot-Decision.png) That includes whether the solution is fit for purpose. Whether the risks are acceptable. Whether the economics still make sense. Whether the delivery path is realistic. Whether the problem is still worth solving in the way we first imagined. A pilot is a relatively cheap place to discover that the right decision is not to proceed. Production is a very expensive one. The money spent on a pilot that tells you to stop is not wasted. It is the cost of discovering, early enough, that a much larger investment would be a mistake. Stopping should not be treated as the embarrassing outcome. Sometimes stopping is the clearest evidence that the pilot worked. If the evidence says the answer has changed, the organisation needs to be able to hear it. That is not a failure of the pilot. That is the pilot doing its job.