From Capable Coordinator to Strategic Program Leader
By David Mantica
I’ve been spending a lot of time in rooms full of Technical Program Managers lately. Different industries, different company sizes, different technical stacks. Same conversation almost every time.
A TPM walks me through the program they’re running. The technical complexity is real. The cross-functional surface area is huge. Six engineering teams, three product partners, two infrastructure dependencies, and an executive sponsor who can’t tell you what success looks like in measurable terms. They’re stretched thin, doing important work, and quietly wondering why they aren’t being treated like a strategic leader inside their own organization.
Here’s what I tell them:
The technical skills got you into the role. The power skills are what get you out of the coordinator box and into the strategic leader seat.
That’s the whole conversation. Everything else is detail.
The TPM reality nobody wants to say out loud
Technical Program Managers sit at the intersection of three worlds that don’t speak the same language. Technology, where the conversation is about architecture and trade-offs. People, where the conversation is about politics and trust. Business, where the conversation is about outcomes and money. The TPM is the only person in the org chart whose job is to translate across all three.
The TPM Institute put it well: technical knowledge forms the backbone of the role, but leadership drives execution. The trap most TPMs fall into is investing only in the technical side — because that’s the part that feels safe, where the next certification gives them a measurable accomplishment.
Technical depth gets you credibility with engineers, architectural judgment, clean trade-off analysis. That’s table stakes. It gets you in the room. What it doesn’t get you is cross-functional alignment, stakeholder trust, conflict resolution, or strategic influence. Those come from a different skill set — and they’re what determine whether you stay a coordinator or become a leader.
We used to call them soft skills. That was the wrong name. They aren’t soft. They’re hard to acquire, harder to fake, and impossible to automate. I call them what they are: power skills. They’re the source of professional power that compounds over a career.
The six that matter most
Six power skills move the needle for TPMs. I’m going to walk through them quickly so you can see how they connect.
Influence without authority is the core TPM superpower. You have responsibility for outcomes. You don’t have authority over the people who produce them. You can only influence — and influence runs on trust, not on title. Tactics without trust feel like manipulation, and engineers can smell that from a mile away. The TPMs who get traction lead with service over self-interest, build credibility through action, and treat every interaction as a deposit or a withdrawal in the trust account. That balance determines how much influence you have when you need it.
Systems thinking lets you see the whole, not just the snapshot. Peter Senge’s iceberg model is still the best mental tool for this: most organizational interventions try to fix events on the surface. Systems thinkers ask what pattern is producing this event, what structure is producing this pattern, and what mental model is producing this structure. For a TPM, that means tracing cause across teams, spotting second- and third-order effects, and knowing where the leverage actually is.
Critical thinking and problem solving is the cognitive foundation underneath everything else. Critical thinking is thinking about your thinking — clarifying it, catching your own errors and biases before they produce bad decisions. It’s not about solving problems. It’s about improving the quality of the thinking that produces solutions. Problem solving is the application: define the real problem first, separate symptoms from root causes, test cheaply, learn quickly, adjust. A clearly defined problem is half the solution. Most program problems get solved badly because nobody slowed down to define them correctly.
Navigating ambiguity is where most TPMs hit a wall, and it’s almost always because they’re using the wrong diagnostic frame. Ron Heifetz and Marty Linsky at Harvard draw a hard line between technical challenges, where the problem is clear and the solution is known, and adaptive challenges, where both the problem and the solution have to be learned through experimentation. Deploying a new CI/CD pipeline is technical. Shifting two teams from silos to shared ownership is adaptive. The mistake almost every TPM makes is trying to solve adaptive challenges with technical playbooks. That doesn’t work.
Business and strategic acumen is the gap that quietly limits most TPM careers. You don’t have to own product strategy. But you cannot lead a program without understanding the business model it serves. If you can’t draw the Business Model Canvas for your company — value proposition, customer segments, revenue streams, key resources — you can’t prioritize. You’re just executing on whatever lands in your inbox. The TPM’s job isn’t to set strategy. It’s to make sure the work delivers it.
Executive presence is the one that gets most misunderstood. Sylvia Ann Hewlett’s research surveyed 268 senior executives. Sixty-seven percent said gravitas — how you act under pressure, how confidently you decide, whether you know your stuff cold — is what really matters. Twenty-eight percent said communication. Five percent said appearance. Most TPMs spend energy on the wrong one. Gravitas is built by being right, often, when the room is hot. There is no shortcut.
The stack matters
Here’s the part most people miss. These skills don’t stack the same way. Critical thinking and systems thinking are the cognitive foundation. Influence, communication, and executive presence are the human skills layer on top. Navigating ambiguity is the adaptive leadership layer above that. Business acumen and strategic alignment sit at the top. You can’t skip layers. If your cognitive foundation is weak, no amount of executive presence training will save you. Build from the bottom up.
Three things to do this week
Pick one power skill. Just one. Invest in it deliberately for 90 days. Read the foundational book, find a mentor, get feedback from people who’ll tell you the truth.
Diagnose your next hard problem before you start solving it. Technical or adaptive? If you can’t tell, you’re going to apply the wrong tools.
Trace any project in your portfolio to a business outcome — in one sentence. If you can’t, that’s a strategic alignment problem, and it’s the most fixable one you’ll find this quarter.
The technical skills got you here. The power skills will take you the rest of the way.
David Mantica is Managing Director of SoftEd North America and writes regularly on adaptive leadership, GenAI, and the future of knowledge work.
Sources & further reading:
- TPM Institute, “Why TPM Jobs Require Both Technical and Leadership Skills” (2026)
- Heifetz, R. A., Grashow, A., & Linsky, M. The Practice of Adaptive Leadership. Harvard Business Press, 2009.
- Hewlett, S. A. Executive Presence 2.0. HarperCollins, 2023.
- Senge, P. M. The Fifth Discipline. Currency/Doubleday, rev. 2006.
Osterwalder, A. Business Model Generation. Wiley, 2010.
