top of page
The Strategy eXecution Forum logo

🎪 The Title Was Bigger Than The Job 📉- Strategy Execution vs Program Management

Writer: Ben Chamberlain
Ben Chamberlain
Sep 14
2 min read

Somebody's about to have a very confusing first day. New title on the door, "Head of Strategy Execution," a genuinely warm welcome committee, a handshake in progress, and then someone slides a laptop in front of him showing exactly one thing, a kanban board with three columns and a handful of sticky notes. That's it. That's the whole capability. No mandate, no operating model, no seat at the table where actual strategic decisions get made, just "To Do," "In Progress," and "Done," and a nameplate promising something considerably bigger than what's on the screen.


Cartoon of a new Head of Strategy Execution sitting deflated at a desk in front of a laptop showing only a basic kanban board, while enthusiastic colleagues welcome him, a nameplate on the desk reading "Head of Strategy Execution"

This happens more often than it should. Organizations think of Strategy Execution as program management on steroids, better tracking, tighter boards, a nicer looking dashboard, and hire against that job description instead of the actual discipline. But Strategy Execution isn't a bigger version of project delivery. It's the enterprise capability that integrates Strategy, Portfolio Management, Operating Model Design and Architecture, FP&A, Project Execution, and Change Management into one cohesive operating system, aligning all activity and spend, operational and discretionary, with strategic intent, so the organization can maximize and accelerate the value it's actually chasing.


That's the core of Principle 2 of the 10 Key Principles of Strategy Execution, Establish an Enterprise Function to Orchestrate Strategy Execution. It's built around integrating six critical capabilities and their associated teams into a genuinely cohesive operating system, not stacking another delivery tracker on top of the same disconnected functions and hoping alignment shows up on its own. Give someone that mandate, and you've built a capability. Give someone a kanban board and a fancy title instead, and you've built an expensive project tracker with a promotion attached.


The 10 Key Principles aren't something we came up with on our own. They're being defined in the open by the StrategyXF community, multi disciplinary leaders and practitioners from Strategy, Operations, Finance, HR, Architecture, Transformation, PMO, Delivery, and Change Management, coming together to name the real challenges holding organizations back from mastering Strategy Execution, and to share what's actually worked. This scene came directly from that conversation.


Where has your organization confused Strategy Execution vs program management, and handed someone a title without the operating model to back it up?👇 



StrategyXF Painfully Accurate Series (Sad, but True!)

This cartoon is part of Painfully Accurate, a StrategyXF series built from real Strategy Execution challenges our members have actually lived through, laughed about, and found a way past.

StrategyXF Painfully Accurate Series (Sad, but True!)

This cartoon is part of Painfully Accurate, a StrategyXF series built from real Strategy Execution challenges our members have actually lived through, laughed about, and found a way past.


Every scene started as something a leader or practitioner described, not a hypothetical, an actual moment somebody in this community said out loud and everyone else in the room recognized instantly. Sad but true, every one of them, and every one of them survivable.


If any of this feels a little too familiar, you're exactly who this community was built for. Join StrategyXF and help us turn these shared war stories into the practical, personalized strategies that finally put them behind us.


 
 
bottom of page