Early in my leadership career, I believed my job was to solve problems.
It sounds reasonable. In fact, it's exactly why many people get promoted in the first place.
They are reliable. They execute well. They take ownership. When something goes wrong, they step in and fix it.
That was certainly true for me.
Before moving into leadership, I built my career in environments where solving difficult problems was rewarded. From the U.S. State Department to Trust & Safety, Risk, and Compliance roles in the technology industry, much of my success came from my ability to navigate ambiguity, manage complex situations, and find solutions under pressure.
When I became a leader, I assumed those same skills would continue to drive success.
Instead, they nearly became my biggest weakness.
The mistake wasn't a failed project.
It wasn't a poor hiring decision.
It wasn't a bad strategy.
The mistake was believing that leadership meant being the person with all the answers.
It took a major operational challenge for me to realize how wrong I was.
The Situation
Several years ago, I was leading a team responsible for managing complex operational and risk-related issues.
The work moved quickly.
Stakeholders expected answers.
Decisions carried real consequences.
Every day involved competing priorities, urgent requests, and constant ambiguity.
As the team's leader, I wanted to be helpful.
Whenever an issue surfaced, I got involved.
If a stakeholder escalated a concern, I joined the conversation.
If a team member wasn't sure how to proceed, I provided direction.
If a difficult decision needed to be made, I made it.
Initially, this approach appeared successful.
Projects moved forward.
Stakeholders felt supported.
The team knew they could rely on me.
From the outside, it looked like effective leadership.
Internally, however, a different reality was developing.
Without realizing it, I had positioned myself at the center of nearly every important decision.
The Hidden Cost of Being Helpful
Most leadership mistakes don't announce themselves immediately.
In fact, many of them look like strengths in the short term.
Being responsive looks positive.
Being available looks positive.
Being knowledgeable looks positive.
The problem is that these behaviors can create unintended consequences when they become the default operating model.
Over time, I noticed a pattern.
People weren't bringing me recommendations.
They were bringing me decisions.
Instead of saying, "Here's what I think we should do," team members were asking, "What should we do?"
Instead of solving problems independently, they were waiting for guidance.
Instead of moving quickly, they were waiting for approval.
At first, I blamed the workload.
Then I blamed process inefficiencies.
Then I blamed resource constraints.
Eventually, I realized the real issue.
The bottleneck wasn't the process.
The bottleneck was me.
How Leaders Accidentally Create Dependency
This is one of the most common leadership traps I see.
High-performing individual contributors become managers and continue behaving like elite individual contributors.
The intention is good.
The outcome is not.
When leaders consistently provide answers, teams stop developing the confidence required to generate answers themselves.
When leaders make every important decision, teams stop building decision-making skills.
When leaders solve every difficult problem, teams stop learning how to navigate difficult problems independently.
None of this happens overnight.
It's gradual.
That's what makes it dangerous.
By the time leaders recognize the problem, they've often created a system that depends entirely on them.
The team becomes slower.
Decision-making becomes centralized.
Growth stalls.
And leaders become overwhelmed.
The Moment Everything Changed
The turning point came during a particularly demanding period.
Several high-priority issues emerged simultaneously.
Stakeholders wanted updates.
Executives needed decisions.
Team members required guidance.
The volume exceeded what any single person could reasonably manage.
For the first time, I was forced to confront an uncomfortable truth.
Even if I worked harder, it wouldn't solve the problem.
Even if I spent longer hours, it wouldn't solve the problem.
The issue wasn't effort.
The issue was structure.
I had built a team that relied too heavily on me.
The only sustainable solution was to change how I led.
The Framework I Started Using
The adjustment wasn't immediate.
Like many new leaders, my instinct was still to jump in and solve things.
I had to deliberately create new habits.
Over time, I developed a simple framework that transformed how I approached leadership.
Step 1: Diagnose Before Advising
When someone came to me with a problem, I stopped providing immediate answers.
Instead, I asked questions.
What have you already considered?
What information are we missing?
What options are available?
What risks concern you most?
This accomplished two things.
First, it improved the quality of the discussion.
Second, it encouraged independent thinking.
People started arriving better prepared because they knew I would ask.
Step 2: Ask for Recommendations
One of the most powerful questions a leader can ask is:
"What do you think we should do?"
Simple question.
Huge impact.
When team members know they'll be expected to provide a recommendation, they engage differently.
They analyze more carefully.
They consider trade-offs.
They develop judgment.
Over time, confidence grows.
Decision-making improves.
Future leadership capability is built.
Step 3: Delegate Outcomes, Not Tasks
Many leaders delegate activities.
Fewer leaders delegate ownership.
There's a difference.
Task delegation sounds like:
"Please complete these five things."
Outcome delegation sounds like:
"You're responsible for solving this problem."
The second approach requires trust.
It also creates growth.
People become more invested when they own outcomes rather than simply execute instructions.
Step 4: Review Thinking, Not Just Results
One mistake leaders make is focusing exclusively on outcomes.
Good outcomes matter.
But strong decision-making matters more.
Sometimes excellent decisions produce poor outcomes because circumstances change.
Sometimes poor decisions produce positive outcomes through luck.
I began spending more time understanding how decisions were made rather than simply evaluating results.
This accelerated development dramatically.
What Changed
The results weren't immediate.
In fact, some people initially found the new approach frustrating.
Providing answers is faster than teaching judgment.
Short-term efficiency often decreases before long-term capability increases.
But eventually, the shift became obvious.
Team members started bringing recommendations instead of questions.
Decisions moved faster.
Stakeholder interactions improved.
People became more confident.
Most importantly, the team became less dependent on me.
That wasn't a sign of reduced leadership.
It was a sign of better leadership.
What I Tell New Managers Today
Whenever someone tells me they're becoming a manager for the first time, I share the same lesson.
Your job is no longer to be the hero.
Your job is to create more heroes.
That's a difficult transition for many high performers.
We've spent years being rewarded for expertise.
We've spent years being rewarded for solving problems.
Leadership requires a different mindset.
The goal is not to become indispensable.
The goal is to build a team that can succeed without constant intervention.
The strongest leaders don't create followers.
They create capable decision-makers.
Final Thoughts
Looking back, the biggest leadership mistake I made was surprisingly simple.
I confused solving problems with leading people.
For a long time, I thought leadership meant providing answers.
Experience taught me that leadership is often about developing the people who will eventually provide those answers themselves.
That's harder.
It's slower.
It requires patience.
But it's also what allows teams, organizations, and leaders to scale.
And in my experience, it's the difference between managing work and truly leading people.
