You get promoted to project lead. Congratulations.
Nobody hands you a manual.
Most new project leads make the same mistake in month one. They keep doing the job that got them promoted — the technical work, the hands-on fixing, the “let me just do it myself” instinct. And they wonder why the team isn’t performing, why stakeholders are frustrated, why everything still runs through them.
The mistake: leading by doing
As an individual contributor, your value was measured by output. You solved the problem. You wrote the code, ran the analysis, built the drawing.
As a project lead, your value is measured by outcomes delivered through other people. That is a completely different game.
New leads often struggle here because nobody told them the rules changed. They keep solving problems the team should be solving. They keep making decisions the team should be making. It feels productive. It is actually a bottleneck — and it’s the fastest way to burn yourself out while your team quietly disengages.
The PMP exam blueprint puts this exact shift front and center. One of its core people-focused tasks is simply: lead the project team. Not “do the team’s work.” Lead it.
That task breaks down into things most new leads never think to do deliberately:
Establish expectations at the team level
Empower the team to own their piece of the work
Solve problems with the team, not instead of them
Represent the team’s voice upward
Determine the leadership style the moment actually calls for
Set clear roles and responsibilities so nobody is guessing
Notice what’s missing from that list. “Do the technical work yourself” isn’t on it.
Why this trips people up
Here’s the part that catches even experienced professionals off guard.
Technical competence built your credibility. Naturally, you assume more technical control equals more credibility. But the moment you’re leading a team, control and credibility start to pull in opposite directions.
The PMBOK Guide frames this as building an empowered culture — team members trust one another, adapt to change, and feel genuinely empowered because the leader recognizes their contributions instead of absorbing all the decisions. That’s not soft language. It’s a direct predictor of whether a team performs under pressure or collapses under it.
The other shift is authority versus accountability. As an IC, you were accountable for your own output. As a lead, you’re accountable for outcomes you don’t fully control — which means your job becomes creating the conditions for other people to succeed, not doing their job for them.
Where this shows up on exam day
This transition isn’t just a career theme. It’s tested constantly, and it’s tested through situational judgment, not definitions.
A typical scenario: a team member comes to you with a technical problem you personally know how to solve in ten minutes. The exam wants you to recognize that solving it yourself isn’t leadership — it’s a missed coaching moment. The stronger answer usually involves guiding the team member to the solution, or determining whether this is a one-off or a signal of a broader skills gap.
Another pattern: a team is underperforming and the “obvious” answer is tighter oversight. The better answer is usually diagnosing why — unclear roles, no shared expectations, no ground rules — before reaching for control.
If you’re studying and every “correct” answer feels like it favors coaching over commanding, that’s not a coincidence. That’s the exam mirroring what actually works.
What to actually do about it
For busy professionals studying while working full-time, this is good news — you don’t need new theory, you need to notice what you’re already doing on the job:
Audit your week. How many hours did you spend doing versus enabling? Be honest.
Delegate one decision you’d normally make yourself. Notice what happens.
Write down team expectations explicitly, even if they feel obvious. Most conflict starts with an assumption that was never actually agreed on.
Ask your team what they need from you, not what you think they need. The gap is usually bigger than expected.
Study the “Lead the project team” and “Build an Empowered Culture” concepts side by side. They reinforce the same shift from two different angles — one from the exam outline, one from the guide — and seeing both makes the pattern much easier to remember under pressure.
The takeaway
Getting promoted proves you were good at the old job. Succeeding in the new one requires letting go of most of what made you good at it.
The professionals who make this shift early — deliberately, not accidentally — are the ones who pass the exam and become genuinely effective leads. The ones who don’t tend to plateau, exhausted, wondering why doing more is producing less.
Leading isn’t doing more. It’s making sure the right things get done by the right people, for the right reasons.
P.S. Wondering if you qualify for the PMP? The rules are stricter than most people think. Check in under a minute → https://vandersonbaril.com/products/pmp-eligibility-checker/
Know a colleague who just stepped into a leadership role and is finding the transition harder than expected? Share this with them.
That’s it for this week—thank you for reading, and see you next Saturday.
