The Personal Discovery Phase: Applying Business Analysis to Becoming
Why pausing for self-reflection is not a delay, but a necessary phase of personal growth.
The Personal Discovery Phase: Applying Business Analysis to Becoming
It has been over three months since I wrote an article.
And strangely, the only person keeping track of that timeline has been me.
Which made me wonder: Why haven't I written in so long? Was it because I had nothing to say? Was it because I lost my curiosity?
No.
Not because I stopped having thoughts.
Not because I stopped wanting to share.
But somewhere along the way, life became a project with too many competing requirements.
Deadlines.
Responsibilities.
Expectations.
Learning curves.
Conversations.
Decisions.
The things that needed immediate attention always seemed to move to the front of the queue. And slowly, quietly, one thing kept moving further down my backlog:
My own reflection.
Maybe that's something many of us experience—especially women.
We become so focused on meeting expectations, solving problems, and supporting everyone around us that we forget to pause and ask:
"Where am I in all of this?"
We measure our progress through invisible milestones, many of which we set for ourselves.
The next promotion.
The next achievement.
The next goal.
The next version of ourselves we believe we should have already become.
And when we don't meet those timelines, we convince ourselves that we're falling behind.
But what if we're not behind?
What if we're simply in discovery?
Discovery Is Not a Delay
As a Business Analyst, I've learned that every successful project begins with a discovery phase.
Before solutions are designed, we ask questions.
Before processes are changed, we understand the current state.
Before we build the future, we acknowledge what we don't yet know.
Discovery is not considered a delay.
It is considered a necessary step.
Yet when it comes to our own lives, we often expect ourselves to skip discovery and jump straight into execution.
We want the perfect roadmap.
The clear to-be state.
The certainty that everything will work before we even begin.
But what if uncertainty isn't a problem to solve?
What if it's a requirement?
In business analysis, uncertainty is not something we ignore.
We investigate it.
We document it.
We use it as a guide for what we need to learn next.
Maybe our personal uncertainty deserves the same patience.
Maybe the unanswered questions in our lives are not signs that we're failing.
Maybe they're simply areas waiting to be explored.
Sometimes we mistake being pulled in multiple directions for being lost.
But perhaps we're simply gathering requirements for the next version of ourselves.
We Become Experts at Analyzing Systems
The challenge is that many of us, especially women, are taught to constantly optimize.
Be productive.
Be dependable.
Be successful.
Have a plan.
Have a backup plan.
Always know what comes next.
We learn to carry responsibilities, manage expectations, and adapt to everyone else's needs.
But sometimes we forget to ask whether those expectations still align with who we're becoming.
We become experts at analyzing systems but rarely analyze ourselves with the same compassion.
We look for gaps, risks, and improvements in everything around us, yet forget that we, too, are evolving systems deserving of patience.
In my career, I would never consider incomplete requirements a failure.
I would call it discovery.
Perhaps even a lesson learned.
So why do I view my own unanswered questions as shortcomings?
Why do I treat the unknown chapters of my life as missing data instead of opportunities for exploration?
The truth is, growth rarely happens in a perfectly documented environment.
It happens through iterations.
Life Is Agile
Life is not a waterfall project where every requirement is gathered upfront and the final product is launched without changes.
Life is Agile.
We learn.
We adapt.
We refine.
We discover new requirements along the way.
Sometimes a requirement changes because we change.
Sometimes the destination evolves because we evolve.
And that doesn't mean the previous version was wrong.
It simply means we gained new information.
The version of ourselves we'll become five years from now may not even be something we can define today—and that's okay.
The goal is not to eliminate uncertainty.
The goal is to build enough trust within ourselves to navigate it.
Maybe It's Being Built in the Discovery Phase
So, after three months away from writing, I'm returning to this space.
Not because everything became less busy.
But because reflection is also part of the work.
Because discovering ourselves is just as important as discovering solutions.
Maybe the next great version of ourselves isn't waiting at the end of certainty.
Maybe it's being built in the discovery phase.
Maybe the only score that matters isn't how quickly we arrive, but how intentionally we evolve.
About the Author
Hi, I'm Nishi.
By day, I navigate the complexities of business processes, systems, and transformation as a Business Analyst.
By night, I explore the human stories hidden beneath our routines, expectations, and identities.
I'm not writing because I have everything figured out.
I'm writing because I believe our voices become stronger when we allow ourselves to be seen—even while we're still evolving.
Through my writing, I hope to create space for conversations about growth, uncertainty, ambition, and breaking the invisible molds that shape us.
Because sometimes the most powerful transformation begins when we give ourselves permission to discover who we are becoming.
