What to Do With Doubt When It Does Not Go Away
Doubt is not a sign of failure; it is a permanent byproduct of building on a long time horizon. Learn how to contain uncertainty through a structured containment framework.
The persistent feeling that you are building on shifting sand is not a sign that you have made a mistake. In the context of the long build, doubt is not a bug in your psychology; it is a feature of the environment. When you are working through the valley between validation and scale, doubt does not go away because you reach a milestone or secure a visa. It simply changes shape.
The answer to persistent doubt is not to seek a state of absolute certainty, which is a fantasy in early-stage building. Instead, the answer is containment. You must move doubt from a constant, ambient noise that interferes with execution to a structured, scheduled input that informs strategy. You do not eliminate it; you build a system to house it.
The Arrival Fallacy and the Persistence of Pressure
There is a common belief that doubt is a temporary condition that will vanish once a specific external condition is met. We tell ourselves that once the product is launched, or once we move to a more stable environment, the weight will lift. But as I learned when I finally arrived in Newark with my family on July 18, 2024, after months of paperwork and uncertainty, arrival is rarely the end of the pressure. It is often just the beginning of a new chapter of responsibility.
When you come from a background of constraint—like my own upbringing in Enugu State—you learn early on that discipline is a survival condition. You do not romanticize the struggle. You realize that the cost of failure is vivid and real. This background gives you a harder relationship with difficulty, but it also means that when you are building something like Postly, which represents a transition from reaction to design, the doubt is fueled by the very real stakes of your life. This is what I call the 'emotional engine' of the work. If the product matters because it represents your agency, the doubt will naturally be as large as the ambition.
A Framework for Containing Doubt
To keep doubt from paralyzing your progress, you must distinguish between the types of uncertainty you are facing. Not all doubt requires the same response. By categorizing the noise, you can determine which signals require a pivot and which require simple endurance.
The Doubt Inventory Table
| Type of Doubt | Root Cause | Recommended Action |
|---|---|---|
| Execution Doubt | Unclear processes or lack of immediate results. | Audit the current workflow. Focus on the 'invisible SaaS work' that compounds over time. |
| Market Doubt | Fear that the product does not fit the current environment. | Return to 'customers as teachers.' Use support interactions as primary research. |
| Identity Doubt | The feeling of being an imposter or 'not fitting the conditions of entry.' | Acknowledge the leadership tax and focus on the survival discipline learned from past reversals. |
| Structural Doubt | External shocks (exchange rates, policy changes, etc.). | Improvise and absorb. Ensure the product is a vehicle for stability, not just a business idea. |
The Scheduled Re-evaluation Strategy
One of the most destructive habits of a founder in the 'middle' is the daily re-litigation of their entire life's work. When you allow yourself to ask, "Is this worth it?" every Tuesday morning at 10:00 AM, you drain the cognitive energy required to actually make it worth it.
To manage this, implement Strategic Containment Windows. Decide that for the next 90 days, the 'big questions' are closed. During this window, your only job is execution. You treat the plan as a set of instructions from a version of yourself that was thinking clearly. You only open the door to doubt during scheduled quarterly reviews where you look at the data, the market, and your own endurance honestly.
This is how you carry ambition without letting it consume everything. By creating a boundary between your strategy and your daily labor, you protect the work from the fluctuations of your mood.
Field Notes for the Long Build
When the doubt feels particularly heavy, it is helpful to remember a few principles from the manuscript of The Long Build:
- The first product is not the real product: You are often building the foundation for something that will only become clear later. Don't judge the final destination by the current scaffolding.
- Simplicity as strategy: When overwhelmed by complexity, strip the problem back to its most basic elements. What is the one thing that must work today?
- Endurance is a system: Do not rely on your personality or 'grit' to get through. Build a system for endurance that includes rest, structured feedback, and clear boundaries.
My relationship to risk was formed long before Postly existed. It was formed through reversals, through watching financial progress erode, and through the humiliating experience of navigating systems that did not care about my effort. If you are feeling doubt, it may be because you understand the cost of failure more vividly than those who come from abundance. That is not a weakness; it is a sharpened understanding of reality.
Moving Forward
If you are currently in a period where doubt will not go away, do not try to fight it with motivational clichés or 'heroic hindsight.' Instead, treat it as a management problem. Document the doubts, assign them to a future review date, and return to the work. The product matters, but so does what the product represents: the possibility that you can move from surviving systems built by others to building a system of your own.
To explore more about the emotional and strategic realities of the middle of the journey, you can continue with the essays at GrowthDiary, where we document the honest cost of building over a long time horizon.
Follow via RSS: latest articles · full article archive