The Second Scorecard
Why Your First Project Is Judged Twice — And Nobody Tells You About the Second One
A 3-minute read for experienced project managers ready to elevate their impact.
Welcome to the Agile Admiral weekly newsletter. Your Essential Resource for Project Management Excellence.
Each week, I tackle reader questions about PMP preparation, implementing PMP in real-life projects, and a career as a Senior Project Manager.
This Week at a Glance:
The Second Scorecard: Why Your First Project Is Judged Twice — And Nobody Tells You About the Second One
10 things silently sabotaging your project
👉🏼Do it together - join the PMP Operation System: https://gaborstramb.com/
The Second Scorecard
Why Your First Project Is Judged Twice — And Nobody Tells You About the Second One
How first-time project managers (PM) pass the visible test, fail the invisible one, and stall their careers without understanding why — and what to do about it.
1. The Problem: The Project Delivered, But Something Didn’t Add Up
For many first-time PMs, their strong performance on the delivery side is contrasted by a problem they never perceive.
They finish the project. They hit the milestones. They present the deck. On paper, everything worked. And then — nothing changes. No bigger project. No expanded scope. No conversation about what comes next. Just a quiet return to where they started, wondering what they missed.
I’ve watched this pattern for 25 years, across projects in Scandinavia, Germany, Belgium, and the US, as a consultant and inside a large corporation.
The PMs it happens to are rarely the weak ones. Often it’s the opposite — the deep experts, the ones who know the subject matter better than anyone on the team, and who were promoted into the PM role for that very reason. And that expertise is precisely what becomes the trap. Understanding the subject matter deeply creates an almost irresistible pull to step in and do the operational work yourself. The PM sees exactly how it should be done, so they do it — and quietly stop leading. Ironically, the very knowledge that earned them the role then becomes what holds their career back.
2. Two Tests, Not One
The first test is the visible one. Can you deliver the work? The plan, the budget, the timeline, the deliverable. This is the test everyone prepares for, and most first-time project managers pass it — sometimes barely, often with overtime, but they pass.
What they often didn’t see was the second test running the whole time: how they handle the soft side of the project. How to lead a team without formal authority. How to manage a crisis. How to negotiate with suppliers and customers — to name just a few. They pass the visible test and never notice the invisible one existed — until the promotion that should have followed quietly doesn’t.
Those are different questions, with different criteria, read from different signals.
The first is read from your project plan. The second is read from your behavior when the plan stops being enough.
Not the polished status deck from the weeks when everything was on track and there wasn’t a cloud in the sky. But how you conducted yourself when you were suddenly in water up to your waist.
3. Where the Second Test Is Actually Scored
The second test is not scored in the moments that go well. It is scored in the moments that go wrong — because that is when character becomes visible.
• The escalation that was raised early — or delayed until it was too late to matter.
• The risk that was named out loud — or the one the PM quietly hoped would resolve itself.
• The decision the PM forced when everyone was avoiding it — or let drift.
• The bad news the PM delivered to their sponsor straight — or softened until it was useless.
Often the troubled times feel like a curse to a PM, and few realize that they are in fact a blessing in disguise — they are the PM’s opportunity to show what they are truly capable of.
Each of these is a signal. And the people who decide the trajectory of your career are reading them, continuously, even when they never say so out loud.
Senior leaders rarely tell PMs about the second test. They simply observe. And they draw their conclusions — often lasting ones — from how you behaved in the hard moments, not the easy ones.
4. Why Capable People Get Stuck
The project manager who fixes every problem personally passes the delivery test and fails the trust test, because leadership sees someone who cannot scale beyond their own effort.
The PM who keeps the status green until the last possible moment protects the timeline and destroys their credibility, because when the truth surfaces, it surfaces as a surprise — and surprises are what senior leaders learn to distrust.
The result is a strange and painful outcome: Someone works harder than anyone on the project, delivers it, and comes out the other side with less trust than they started with. Not because they failed to deliver the project outcome. Because they passed the wrong test, and didn’t know there was a second one.
5. Closing the Loop: What to Do About It
The shift is not about working differently on the visible test. It is about recognizing that the invisible test — where your reputation beyond the project is built — runs on a different set of skills than the ones that got you here.
So it helps to be clear about what those skills actually are. The soft side of project management is not vague, and it is not about being likeable. It comes down to a handful of concrete capabilities: Leading people who don’t report to you, so that they follow your direction without being told to. Reading stakeholders — hearing what they mean, not just what they say. Handling conflict before it hardens into a blocker. Negotiating with suppliers, customers, and sponsors whose interests don’t align with yours. And communicating bad news in a way that builds trust rather than eroding it. None of these appear on a Gantt chart. All of them decide whether the project — and your reputation — moves.
The good news is that these are not fixed traits you either have or don’t. They are learned the same way any craft is learned: By doing them consciously, one situation at a time, and paying attention to what happened. The first-time project manager who treats every difficult conversation, every escalation, every negotiation as a rep — a deliberate attempt rather than a thing to survive — improves far faster than the one who simply endures them and moves on. The raw material for growth is already there, in every ordinary week of your job. Most people just let it pass unexamined.
Which points to the single most underused tool available to a first-time PM: reflection. Either done on your own or with people you trust. Not vague self-criticism, but a specific, honest question asked regularly. After a hard moment, two questions do most of the work. What did I actually do — and what signal did that send to the people watching? And: If the same situation arrived again next week, what would I do differently? The failures are worth more here than the successes, because a failure examined closely tells you exactly where your instinct still pulls you the wrong way. A success, unexamined, teaches nothing. The project managers who accelerate are often the ones who turn each project into evidence — and then actually read it and learn from it.
Because the first test gets you through the project. The second test decides what happens after it. And the second test is also one you can prepare for — starting with your very next difficult conversation.
Jens Rosenstand spent 25 years leading and advising on projects across Scandinavia, Germany, Belgium, and the US, in consulting and inside a global corporation. He is the founder of The First Project, a community where people stepping into their first project leadership role exchange notes on the shift that first project demands: from doing the work to being trusted with it. linkedin.com/in/jens-rosenstand
The biggest threats to a project are rarely the ones everyone is talking about.
They are the small behaviors teams gradually accept as normal.
One person becomes the answer to every problem.
Every task is treated as urgent.
Decisions are discussed but never truly made.
Heroics are rewarded more than prevention.
Concerns stay unspoken.
Information doesn't flow.
Calendars leave no room for deep work.
Key conversations happen outside the room.
Momentum gets interrupted by constant switching.
Deadlines are set before the work is understood.
None of these seems significant in isolation.
But together, they create friction.
And friction is what quietly slows execution, drains energy, and makes great teams perform below their potential.
The best project leaders don't just manage plans.
They identify and remove the hidden obstacles standing in the way of progress.
Because when friction decreases, performance increases.
See you next week
Follow me on LinkedIn | YouTube | Instagram
If we are not connected via LinkedIn, click here → LinkedIn
PMP prep is not a walk in the park. An average student spends 4 to 6 months preparing for exams. There is a different way of doing this, and I’m happy to show you “how”. When you’re ready, follow the links below:
👉🏼Do it together - join the PMP Operation System
👉🏼Do it 1-on-1 - join 8-week coaching program
You may find something from this recent analysis and critique I posted to be of interest? https://project-doctor.medium.com/public-response-to-ms-anna-ladipos-paper-on-managing-academic-transformation-0ebdebdf85ba?source=email-3b44037f3ff8-1784002711573-newsletter.subscribeToProfile-------------------------736b0113_0327_4745_9f3f_426fafab1676--------7c555891395e