The Discovery Phase of the Soul: Why Uncertainty is a Requirement
Embracing the Unknown as Your Greatest Requirement for Growth
The Discovery Phase of the Soul: Why Uncertainty Is a Requirement
In my career as a Business Analyst, I’ve often heard peers say that a project without a “Discovery Phase” is destined to fail. Why, then, do we deny ourselves the same grace when navigating the discovery phases of our own identities?
I used to think of uncertainty as a system error, when it is actually the most critical requirement for growth.
Lately, I’ve been learning that the more we fight the unknown, the more “stuck” we are bound to feel. In the world of Business Analysis, we often treat uncertainty as a risk to be mitigated or a bug to be crushed. But if we apply a “Requirements Gathering” lens to our personal lives, we must treat uncertainty as a functional requirement—something the system needs in order to operate and evolve.
1. The Root Cause: Why Are We Fighting the Logic?
When we feel paralyzed by the unknown, we often misidentify the problem. I used to think of the anxiety of the fog as if it were a roadblock on the path. In our professional lives, we wouldn’t stop a project just because the documentation was incomplete; we would simply label it a “draft,” acknowledge that the “to-be” state is still being defined, and keep moving. We are comfortable with placeholders when they exist in a spreadsheet.
But in my personal life, I found myself mistaking a lack of clarity for a lack of capability. I was treating a temporary data gap as a permanent system failure.
I realized I was wasting my “processing power” on ghosts—simulating a thousand different “what-if” scenarios for a future that hasn’t even been coded yet. I was so busy trying to optimize a roadmap I couldn’t see that I forgot my ambiguity is actually a placeholder for my potential. In a Business Requirements Document, we don’t fear the “unknowns” section; we use it to define what we need to learn next. Why was I treating my own unknowns as a reason to shut down the whole operation?
If we are patient enough to sit with the discomfort and perform a root cause analysis—the classic “Five Whys”—we usually find that the root cause isn’t a lack of information. It’s a conflict of the heart.
The Internal Drill-Down:
The surface feeling: “I feel stuck because I don’t know what the next chapter looks like.”
Why? Because I’ve always been the one with the plan—the one who knows the way.
Why does that matter? Because I’m afraid that if I’m not achieving or moving, I’m disappearing.
Why? Because I’ve spent my life fulfilling a “requirement” to be the reliable one—the eldest daughter, the fixer, the analyst who never misses a detail.
Why? Because I’m terrified that if I don’t have a map, I’ll be seen as “broken” rather than “in transition.”
The root cause: Perhaps I am holding on to an old version of myself that no longer fits the person I am becoming.
By identifying this root cause, we realize that uncertainty isn’t the error—our resistance to it is. I am learning to remind myself that uncertainty is not failure, and it is certainly not a system failure. We are simply running a high-level recalibration. In my professional world, a system that pauses to ensure its integrity is considered reliable. Why should I expect anything less from myself?
2. Letting Go of the “Legacy Self”
The reason we fight uncertainty so hard is that we are protective of our legacy self—the version of us that felt safe, controlled, and understood. We try to “patch” the discomfort by staying busier, planning harder, or grasping for the one thing that will validate our worth.
In the world of data, “latency” describes the time it takes for a signal to travel. In our lives, we call it “waiting.” We feel like we are failing because we aren’t “loading” fast enough. But perhaps the system isn’t crashing—it’s simply rerouting to a destination we haven’t yet imagined.
The root cause of our pain isn’t the fog ahead of us; it’s our reluctance to let go of the dry land behind us. We are trying to carry the heavy furniture of our past into a future that requires us to travel light.
3. Trusting the Discovery
Uncertainty isn’t an error. It is a functional requirement—the space needed for the system to evolve.
If we want to move into the next version of our lives, we have to stop debugging the waiting and start trusting the discovery. We must accept that we are currently “Version 1.5”—a work in progress that is functional, valuable, and exactly where it needs to be.
I’ll be the first to admit that I’ve treated my life like a waterfall project for years. I tried to gather every requirement for my future before allowing myself to move, expecting a single, massive launch where everything would be perfect and permanent.
But it’s time to admit that life is actually Agile.
We live in sprints. Just when we think we’ve reached the final “to-be” state, the market shifts, our hearts change, and a new set of requirements emerges. This isn’t a sign that we’ve failed or returned to square one—it’s simply the next iteration.
The goal isn’t to eliminate the fog once and for all; it’s to build a system flexible enough to handle the next reroute. We don’t need a map that never changes—we need a compass that works even when the destination is still being defined.
About the Author
Hi, I’m Nishi. By day, I navigate the digital systems of the corporate world; by night, I peel back the layers of our performative culture to uncover the human stories beneath.
I am not a professional writer, but a woman learning to use her voice in a world that often teaches us to be quiet. Through my writing, I celebrate life’s uncertainties and the journey of breaking cultural molds. I choose to be heard rather than perfect, and I encourage other women to trade the hollow comfort of the “mold” for the power of their own voice.
