From Junior to Strategic: How Leaders Are Helping Project Managers Level Up
Strategic Gap: Project managers often excel tactically but struggle to influence outcomes and think strategically.
Transformative Question: Key, targeted questions can reveal gaps and initiate PMs' shift from tactical to strategic thinking.
Ownership Transfer: Leaders encourage PM growth by requiring solutions and business impact analyses, not passive updates.
Business Exposure: Involving PMs in strategic business contexts transforms their focus from execution to decision making.
Leadership Restraint: Letting PMs own outcomes, even failures, builds their strategic capacity and organizational impact.
Every leader has worked with this project manager: organized, reliable, on top of every timeline and risk register — and somehow still not seen as strategic. The status reports are flawless. The schedules hold. And yet when leadership talks about who's ready for bigger things, their name doesn't come up. We asked leaders across industries how they've helped junior project managers break through that ceiling, and their stories followed a strikingly consistent arc: a moment of recognition, a question that exposed the gap, a deliberate transfer of ownership, and a hard look at the habits that keep PMs tactical in the first place.
The Tactical Ceiling: Excellent at Execution, Blind to Impact
The pattern starts the same way almost every time. Yuki Yang, Operations Manager at Kabeier, described a junior project coordinator who managed product development and production schedules across multiple client accounts. "She was excellent at reporting what was happening, but struggled to understand why it was happening or what might happen next," Yang said. "She viewed project management as tracking activity rather than influencing outcomes."
She was excellent at reporting what was happening, but struggled to understand why it was happening or what might happen next. She viewed project management as tracking activity rather than influencing outcomes.
Bogdan Condurache, the CPO and co-founder of Brizy, saw the same thing on his product team — a PM who ran meetings well, tracked timelines, and kept projects moving, but where "every conversation was centered around what needed to get done, not why we were doing it." As he put it, "They were managing activity, not outcomes." Sometimes the ceiling shows up commercially rather than operationally.
Unlock for Free
Create a free account to finish this piece and join a community of forward-thinking leaders unlocking tools, playbooks, and insights for thriving in the age of AI.
Have an account? Log In
Tom Bukevicius, the CEO and founder of Scube Marketing, mentored a PM clients loved because they always said yes and moved quickly — while projects ran over budget and teams burned out. "The issue was not execution. The issue was a lack of commercial thinking."
The issue was not execution. The issue was a lack of commercial thinking.
And at Action1, Peter Barnett, the VP of product strategy, worked with a PM who looked like a top performer on paper. "The problem was that they treated every request as a requirement."
The Question That Changed Everything
Nearly every leader could point to a single question that exposed the gap. For Yang, it came during a complex production season when small delays were compounding and her coordinator presented a flawless status report with no view of downstream risk. Yang asked her, "If every task on this report slips by three days, which customer misses their launch date?" She didn't know the answer.
At Action1, the question came during planning for a security-focused initiative, when the PM presented a timeline that accommodated every stakeholder request. Barnett asked, "What are we saying no to?" The room went quiet. He later distilled the lesson into a line that became a recurring theme in their one-on-ones: "Your job isn't to create agreement. Your job is to help the business make better decisions."
Your job isn’t to create agreement. Your job is to help the business make better decisions.
Condurache took a similar tack during a launch planning review: "If we had to cut half of these features today, which ones would you keep and why?" The PM couldn't answer confidently — they'd never been asked to prioritize based on business impact.
Brad Maltz, President of Brad Maltz Consulting Inc., was blunter with a mid-level technical PM named Sarah, who had just walked him through a beautifully formatted but entirely passive update on a slipping launch. "I said, 'your status report is a perfect autopsy, but I don't need an undertaker, I need a pilot. If you were the CEO of this product line and your entire annual revenue depended on hitting this date, what aggressive trade-offs would you make right now to force this across the finish line?'"
Stop Answering, Start Requiring Recommendations
The question opens the door; what happens next is what builds the muscle. Across every story, leaders made the same deliberate move: they stopped being the first point of escalation and started requiring a point of view.
Yang stopped solving every problem for her coordinator and instead asked her to come to meetings with three things: "The biggest risk she saw. The likely business impact if nothing changed. Her recommended solution."
Maltz made the expectation explicit with his PM Sarah: "Stop asking me for permission to change the plan. Present me with the three best options, the financial trade-offs of each, and tell me which one we are executing. Your job isn't to report that the ship is sinking; your job is to steer it." It worked — Sarah went back to the engineering leads, re-architected the phased release plan to bypass the delayed vendor component, and preserved the launch date.
Your job isn’t to report that the ship is sinking; your job is to steer it.
Condurache stopped giving solutions altogether. When his PM came to him with a problem, he would ask, "What decision would you make if I wasn't here?"
Open the Doors: Exposure to Business Context
Requiring recommendations only works if the PM can actually see the business they're recommending for. So these leaders pulled their PMs into rooms they'd previously been shielded from. "I also began including her in customer planning discussions, pricing conversations, and production capacity meetings that I previously handled myself," Yang said.
I began including her in customer planning discussions, pricing conversations, and production capacity meetings that I previously handled myself.
Barnett did the same: "Budget discussions. Customer escalation reviews. Executive tradeoff meetings. Instead of asking them to report status, I asked them to recommend a course of action."
Rajendran brought his PM into architecture reviews, executive planning, and investment conversations with trade-offs — and reframed every project discussion to start with organizational outcomes rather than the project plan.
Condurache gave the exposure structure, asking the PM to evaluate every client request through four lenses: "client value, team impact, business profitability, and long term strategic fit." A few months later, when a similar mid-campaign request came in, the PM returned with a revised recommendation, an adjusted scope, and a clear explanation of the trade-offs. The client respected the decision, and the project stayed healthy.
Let Them Own the Outcome — Even When It Goes Wrong
The hardest part of this approach is what it asks of the leader: restraint. Yang described a moment when her coordinator recommended keeping a production schedule unchanged despite several warning signs. Yang disagreed internally but allowed the decision to proceed. Two weeks later, the team had to expedite part of the order at additional cost.
"Rather than treating it as a failure, we conducted a post-mortem together. She realized she had focused on current task completion rather than future constraints."
Rather than treating it as a failure, we conducted a post-mortem together. She realized she had focused on current task completion rather than future constraints.
Condurache had his own uncomfortable moment when his PM underestimated stakeholder concerns and a release was delayed. "My instinct was to step in early and fix it, but I let them handle the conversations themselves. It wasn't a perfect outcome, but it taught them more than any coaching session could."
My instinct was to step in early and fix it, but I let them handle the conversations themselves. It wasn’t a perfect outcome, but it taught them more than any coaching session could.
What "Strategic" Actually Looks Like
So what does the other side of the transition look like, concretely? For Yang's coordinator, the change shows up in how she frames decisions. "She no longer asks, 'What should we do?' Instead, she says, 'Here are the options, here's the risk associated with each, and here's what I recommend.'"
Rajendran draws the contrast in sharp parallel terms: "The tactical PM reports risks. The strategic PM anticipates risks before they appear in dashboards." And ultimately, "The tactical PM controls the project. The strategic PM controls the uncertainty."
The tactical PM reports risk. The strategic PM anticipates risks before they appear in dashboards.
Maltz frames it as a move from outputs to outcomes: "A tactical PM asks, 'Did we ship the features on time?' A strategic PM asks, 'Is this feature set still the fastest way to capture the market share defined in our business case, or has the market shifted since we wrote the scope?'"
And for Condurache, the proof is systemic thinking: "They understand how one decision affects resource allocation, margins, employee burnout, customer retention, and future opportunities."
Where Leaders Get It Wrong
If the path to strategic PMs is this consistent, why do so many stay tactical? Because the most common leadership instincts work against it. "The biggest mistake I see leaders make is over-coaching," Yang said. Managers answer every question, attend every stakeholder meeting, and intervene at the first sign of risk. "They intend to support development, but they inadvertently prevent project managers from building judgment."
Rajendran agrees: "The most common error leaders commit is excessive protection of PMs." Filtering stakeholder conversations and answering questions immediately produces excellent coordinators instead of effective strategists.
As Condurache put it, "Volume does not create strategic thinking. In many cases it reinforces tactical behavior because people become consumed by execution."
Volume does not create strategic thinking. In many cases it reinforces tactical behavior because people become consumed by execution.
Action1's VP of product strategy drew the same conclusion: "Strategic project managers aren't created by giving them bigger projects. They're created by giving them visibility into business tradeoffs and expecting them to have a point of view on those tradeoffs."
Even well-meaning development tactics can backfire. Maltz warns against the shadowing trap, where junior PMs are invited to executive meetings only to sit silently in the corner. "This passive observation doesn't build strategic muscle; it teaches them to watch leaders make decisions rather than making decisions themselves."
The Real Transfer Isn't Knowledge — It's Ownership
Notice what none of these leaders did: send their PM to a strategy course. They didn't teach strategy at all. They transferred ownership of project managers — of decisions, of trade-offs, of consequences — and strategic thinking grew to fill the space. Yang puts the destination plainly: "The goal isn't to teach someone how to manage tasks more efficiently. It's to teach them how to think like the business owner of the project." If you lead project managers, the question isn't whether they're ready for that responsibility. It's whether you're ready to hand it over.
Want more insights like these? Sign up for a free DPM account to hear from more experts like these.