How Vision and Evidence Change During a Long Build
In a long build, vision provides the initial momentum, but evidence provides the direction. Understanding how these two forces interact is the difference between building a product that lasts and one that gets lost in the middle.
In the early days of a long build, vision is your only currency. You are building something that does not yet exist, fueled by a conviction that the world lacks a specific utility. At this stage, evidence is sparse, and if you rely solely on it, you would likely never start. However, as the build progresses into the months and years of the middle journey, the relationship between your vision and the evidence gathered from the market must shift. If it does not, the vision becomes a hallucination, and the evidence becomes a distraction.
The Lifecycle of Conviction
The primary challenge for a founder is that vision and evidence do not grow at the same rate. Vision is often at its peak before the first line of code is written. It is pristine, unburdened by technical debt or user complaints. Evidence, conversely, starts at zero and grows through the friction of real-world usage.
The first version of a product is best treated as a hypothesis rather than a verdict. Its value is not that every early assumption survives. Its value is that it creates a real surface against which customers, support conversations, observed behavior, and technical constraints can respond. That evidence can remove non-essential ideas while leaving the underlying purpose intact.
Phase 1: Vision-Led Momentum
In the beginning, you must protect the vision from premature evidence. If you listen to every early skeptic or try to solve every edge case before you have a core loop, you will dilute the product into nothingness. Here, vision acts as a filter, allowing you to say no to features that do not align with the long-term horizon.
Phase 2: The Arrival of Evidence
As the product enters the hands of users, evidence begins to arrive in the form of support tickets, churn patterns, and quiet neglect. This is the most dangerous part of the long build. This is where the founder tension between ambition and patience is most acute. The evidence often suggests that your vision was slightly off-target. The temptation is to either ignore the evidence to protect your ego or to pivot so violently that you lose the original soul of the project.
From Theory to Utility
A founder does not need to invent a dramatic pivot story to explain this change. The ordinary work is enough: compare the promise with actual use, separate recurring evidence from isolated requests, and ask whether complexity serves the customer or merely protects the founder’s original idea. Support can become product research without every complaint becoming a roadmap instruction.
Vision matures when it becomes specific enough to be tested and flexible enough to learn. The question moves from “How do I preserve every part of the original idea?” to “Which purpose must remain true, and which implementation choices should evidence be allowed to change?”
The Decision Framework: Vision vs. Evidence
To navigate a long build, you need a framework to decide when to hold the line and when to adapt. Not all evidence is equal, and not all visions are worth preserving.
| Situation | Vision-Led Response | Evidence-Led Response | The Balanced Path |
|---|---|---|---|
| Low User Retention | "They just don't understand the long-term value yet." | "The product is broken; we should change everything." | Audit the onboarding. Is the vision communicated, or is the utility missing? |
| Feature Requests | "That doesn't fit the aesthetic/strategic goal." | "Build it immediately to stop the churn." | Identify the underlying pain. Can the vision solve this without adding bloat? |
| Market Shifts | "Stay the course; we are building for the future." | "Chase the latest trend to stay relevant." | Adapt the delivery, but keep the core principle. Simplicity as strategy. |
Failure Modes in the Middle
Understanding what founders misunderstand about ambition and patience is critical when vision and evidence conflict. There are two primary ways to fail during a long build:
- The Ghost Ship: This happens when a founder clings so tightly to the original vision that they ignore years of evidence that the market has moved on. They build a perfect product for a customer that no longer exists.
- The Feature Factory: This happens when a founder has no vision left and only reacts to evidence. The product becomes a bloated mess of disconnected features, losing its competitive advantage and its simplicity.
The goal is to arrive at a state of "informed conviction." This is a vision that has been weathered by evidence but not eroded by it. It is the realization that while the product's form may change, the intent behind it remains the same.
Field Notes for the Long Build
If you are currently in the middle of a multi-year build, consider these steps to reconcile your vision with the evidence you are seeing:
- Categorize your support tickets as research. Stop seeing them as problems to be solved and start seeing them as data points on where your vision is failing to meet reality.
- Identify your "Non-Negotiables." What are the 2-3 core principles of your vision that cannot change? Everything else—UI, specific features, pricing—should be subject to evidence.
- Practice "Simplicity as Strategy." Often, the evidence suggests that your vision is too complex. Learning to say no to your own early ideas is the highest form of founder maturity.
- Review the cost of speed. Sometimes evidence suggests you need to move faster, but in a long build, moving too fast on the wrong evidence creates technical and emotional debt that can sink the project later.
For more reflections on the journey through the middle, you can continue with The Long Build and GrowthDiary essays. Building over a long time horizon requires a shift in identity—from a person with an idea to a person who can steward a system through the fog of uncertainty.
Follow via RSS: latest articles · full article archive