This is part two of two articles on aligning business and technology through shared strategy execution frameworks.
Authors: Marga Lenten – van Boxtel, Alex Ballarin, Aaron McKenna, Frederic Moreau, and Tristan Pelloux
Transformation offices and PMOs sit at the center of organizational complexity. They coordinate projects, manage budgets, mitigate risks, and ensure compliance across multiple functions. Yet despite increasing sophistication, many PMOs still face the same challenge: strategy and delivery rarely move in sync.
Business priorities shift quarterly, technology evolves daily, and governance reports monthly. The result is misalignment. PMOs absorb the consequences of this misalignment, mediating between shifting priorities, fixed funding, and delivery realities without the authority to reset the system.
Part One showed that shared cadence between strategy and technology is a defining trait of organizations with high strategy execution maturity. This second article focuses on how PMOs and Transformation Offices turn that principle into an operating reality by redesigning planning, governance, and portfolio decision-making. Without this institutional layer, shared cadence remains fragile and dependent on individual leaders.
In SEM360™ terms, PMOs are the mechanism through which shared cadence is scaled and sustained across all five dimensions, from alignment of intent to empowerment of teams.
SEM360™ is a maturity model and diagnostic tool that assesses how effectively an organization translates strategy into execution across five dimensions: Align, Execute, Improve, Scale, and Empower. It provides a structured evaluation of strategy execution maturity and delivers practical recommendations to help leaders strengthen alignment, governance, and delivery.
Why PMOs Are Central to Sustaining Shared Cadence
The role of the PMO has evolved. Once focused on oversight and reporting, today’s PMOs are expected to enable agility and impact. They must ensure that every initiative contributes to measurable business outcomes, while keeping governance transparent and adaptable.
In many organizations, this shift is overdue. Projects still land on time and on budget, yet somehow miss the value they were meant to deliver. Funding cycles lock in plans that are outdated within months. The PMO risks becoming a function that chases status updates instead of adding real value by ensuring work clearly ladders up to strategic outcomes and delivers meaningful impact for the business.
“What if we found ourselves building something that nobody wanted? In that case what did it matter if we did it on time and on budget?”
Eric Ries
Modern PMOs exist to answer that question before it becomes an expensive lesson.
Structural alignment changes how decisions are made, not just how plans are documented. When the PMO establishes shared cadences across strategy, portfolio, and delivery, the organization aligns around a single rhythm for turning strategy into results. Strategy becomes a living process, reviewed and adjusted quarterly. Portfolio governance becomes evidence-based rather than schedule-based. Delivery teams understand not just what to build, but why it matters, why it is urgent and why now. Delivery teams can bring their learnings from the trenches upwards to the strategy and planning decision makers.”
For change leaders, this alignment means moving from administrative oversight to system orchestration. The PMO’s role is not to collect updates, but to design and support the rhythms, artefacts, and decision rules through which strategy is executed.
While technology leaders often initiate cadence alignment, PMOs are the only function structurally positioned to sustain it over time. They span strategy, finance, delivery, and governance. This gives them a unique ability to turn shared cadence from a leadership practice into an organizational system.
Without PMO ownership of these rules, shared cadence remains a leadership preference rather than an organizational enabling constraint.
How Cadence Misalignment Creates Portfolio Friction
For PMOs, cadence misalignment shows up less as theory and more as persistent portfolio friction.
Level of abstraction
There is a structural misalignment between strategy and execution: strategy is formulated at an abstract level, while implementation happens within concrete operational constraints. This mismatch is a common cause of implementation gaps.
Show example
Example: Leadership sets a priority like “Become a digital-first organization.” Delivery teams then spend months untangling integrations, compliance blockers, and data issues. Progress appears slow, not because teams are underperforming, but because strategy never translated into executable steps.
Disconnected cadences
Strategy is planned annually, while delivery teams operate on shorter and more frequent cycles. Without synchronization, priorities drift and progress becomes hard to interpret.
Show example
Example: Annual planning funds Initiative A as a top priority. By Q2, market conditions shift and Initiative B matters more. Leadership assumes teams pivot automatically, but teams continue delivering Initiative A because that’s what funding, commitments, and roadmaps still say. Everything moves, but not in the same direction.
Rigid budgets
Project-based funding promotes a “big bet” mindset. Once a business case is approved, it is rarely re-examined. Initiatives continue without systematic evidence that they are still delivering the value originally promised.
Show example
Example: A large transformation programme is funded to modernise customer onboarding. Halfway through, market demand shifts and a simpler solution would work better. Yet the programme continues because budget approval, vendor contracts, and sunk costs make stopping politically and financially uncomfortable. Money flows to yesterday’s problems.
Fragmented reporting
Each team or department has its own metrics and dashboards, making it impossible to see a unified picture of progress.
Show example
Example: Technology reports delivery velocity is improving. Finance reports spend is on plan. Marketing reports campaign success. Operations reports increased workload. Meanwhile, customer experience and revenue remain flat. Each function optimises locally, while enterprise outcomes stall.
Inconsistent working practices
Business teams use familiar strategic frameworks, while delivery teams rely on technical rituals and methods that can feel opaque to non-engineers. Without shared terminology or working norms, progress can become difficult to interpret and easy to miscommunicate.
Show example
Example: Executives talk outcomes and priorities. Delivery talks sprints, backlog refinement, and technical dependencies. Both discussions describe the same work but in languages that rarely connect. Trust erodes because neither side feels understood.
Superficial governance
Steering committees often review timelines rather than outcomes. This creates the illusion of control but hides whether initiatives are achieving their purpose.
Show example
Example: A programme stays green on status reports while adoption is low and benefits fail to materialise. Governance confirms delivery activity, not value delivery. The organization feels in control while outcomes quietly miss the mark.
Portfolio overload
Even with shared cadence, organizations often maintain too many concurrent initiatives. Teams split attention, dependencies multiply, and delivery slows. Cadence alignment without portfolio focus results in synchronized overload rather than effective execution. PMOs must actively manage portfolio WIP, not just portfolio reporting.
Show example
Example: An organization successfully aligns quarterly strategy and delivery planning, yet progress remains slow. The portfolio still contains 40 active initiatives, with teams split across multiple priorities and dependencies piling up. Everything moves, but little finishes. Only when the PMO reduces active initiatives to a focused set aligned to strategy do teams regain capacity and outcomes start landing.
The result is familiar: too many priorities, too little focus, and no shared sense of success.
These symptoms are the portfolio-level expression of the execution gaps described in Part One, and they are where PMOs have both visibility and leverage.
From a SEM360™ perspective, these portfolio-level symptoms indicate low execution maturity across multiple dimensions at once. Misaligned cadence weakens Align by obscuring strategic intent, constraints Execute through conflicting priorities, limits Improve by reducing learning cycles, prevents Scale by locking resources, and undermines Empower by centralizing decisions without context.
Five Ways PMOs Reconnect Strategy, Governance and Delivery
PMOs can drive meaningful alignment through five practical levers that make cadence, language, and governance work together. These five levers should not be treated as independent improvements. Together, they form a closed execution loop that connects strategic intent, portfolio decisions, delivery evidence, and learning. PMOs are responsible for maintaining this loop.
1. Build a Common Language Across Functions.
Create a shared vocabulary for objectives, outcomes, and results. When every department uses the same terminology, coordination becomes easier and progress clearer. Include OKRs in steering packs and templates so that progress is framed in terms of outcomes, not milestones. This shared language must be embedded in portfolio templates, steering materials, and funding discussions, not limited to delivery teams.
2. Synchronize Planning Cadences.
A shared cadence alone is not enough. Organizations can move faster while still moving in different directions. Synchronization must be anchored in a shared understanding of the outcomes being pursued.
Quarterly strategy reviews, portfolio prioritisation, and delivery planning should operate within a single decision rhythm, guided by explicit outcomes and clear decision rights. This ensures that every planning moment connects strategic intent, funding choices, and delivery commitments. Leadership can refine direction, reallocate resources, and review evidence of progress without waiting for annual cycles.
3. Integrate OKRs into Portfolio Governance.
Use OKRs to connect the portfolio with strategic intent. Each major initiative should have linked Key Results that define success in measurable terms. Finance and governance reviews should evaluate these outcomes alongside budget use and delivery progress. Initiatives without clear, measurable Key Results should not pass portfolio review gates.
4. Anchor Execution in the Transformation Office.
The Transformation Office or Lean-Agile Center of Excellence must own cadence integrity, evidence flow, and escalation paths across the portfolio. It should ensure that OKRs inform portfolio reviews, planning templates, and decision gates. Over time, this creates a single thread of accountability from strategy to team delivery.
5. Shift to Evidence-Based Decision Making.
Replace traditional RAG (red-amber-green) reporting with evidence reviews that assess value delivered. If an initiative achieves its intended outcomes, funding can increase. If it underperforms, resources can shift. This approach builds agility into governance and ensures that money follows impact. Evidence reviews should explicitly result in one of three decisions: continue, pivot, or stop.
Together, these five levers raise execution maturity across all SEM360™ dimensions. Shared language and cadence strengthen Align. Outcome-linked and cadence governance improves Execute. Evidence-based reviews reinforce Improve. Portfolio-level decision rhythms enable Scale. Clear decision rights and funding flexibility increase Empower. The value lies not in any single lever, but in their combined effect on the execution system.
From Compliance Governance to Optimizing Governance
In SEM360™, cultural change is not a separate initiative, it is the byproduct of how governance, learning, and decision rights are designed.
Structural alignment fails if governance behaviour does not change. Many PMOs still operate as control centers, verifying compliance instead of enabling performance. The next evolution is to become enablers of learning and adaptation.
From approval-heavy decision gates to evidence-backed autonomy. Governance should guide rather than dictate. Teams need space to experiment, learn, and adjust. PMOs can create this trust by focusing on transparency and support / coaching rather than enforcement.
From milestone tracking to outcome-based funding discussions. Reporting should emphasize value achieved, not volume delivered. When outcomes are visible, teams become intrinsically motivated to improve.
From fixed plans to explicit portfolio-level learning cycles. The PMO should act as a feedback hub that captures insights from delivery teams and uses them to refine strategy and process. Over time, this turns the organization into a continuously learning system.
From treating technology as delivery support to managing it as strategic infrastructure. Portfolio agility depends on architectural health. PMOs must ensure platform investment and technical debt reduction are built into portfolio decisions, enabling priorities to shift without being constrained by legacy systems.
Cultural change follows decision patterns. When funding, prioritisation, and escalation are consistently tied to outcomes and evidence, behaviour adapts quickly. Trust increases because the system becomes predictable, not permissive.
What Changes When PMOs Institutionalise Shared Cadence
A European financial services group adopted this integrated approach across its Transformation Office. By embedding OKRs into quarterly portfolio reviews and aligning cadence with delivery teams, they eliminated redundant projects and accelerated time-to-value. Governance meetings shifted from status reporting to strategic dialogue.
The critical shift was not delivery speed, but the ability to make consistent quarterly portfolio decisions based on outcomes rather than sunk cost.
Another company in the manufacturing sector linked strategic OKRs to product development portfolios. By aligning funding with quarterly outcome reviews, they reduced budget reallocation time by 40 percent and achieved higher consistency in cross-functional initiatives.
What changed structurally was the funding cadence, which allowed resources to move without reauthorising the entire portfolio.
Signals that indicate sustained cadence alignment at portfolio level include:
- Percentage of initiatives with measurable Key Results.
- Number of quarterly decisions based on outcome evidence.
- Time from strategy update to delivery adjustment.
- Ratio of active projects contributing directly to strategic objectives.
In SEM360™ assessments, organizations that institutionalise shared cadence through PMOs consistently score higher across all five dimensions, particularly in Scale and Empower. These metrics focus on alignment and agility rather than administrative throughput.
From Leadership Intent to Institutional Execution
When PMOs, Change, and Transformation leaders align strategy, funding, and delivery through shared language and cadence, they transform their role and the organization’s effectiveness.
Part One showed how shared cadence improves execution maturity when led by technology leadership. Part Two demonstrates how PMOs and Transformation Offices turn that cadence into organizational muscle memory. When cadence, governance, and evidence are institutionalised, strategy execution no longer depends on heroics. It becomes repeatable.
The future of transformation lies in institutionalised alignment, where continuous cadence replaces episodic planning and governance becomes a learning system. But shared cadence without shared intent simply accelerates misalignment. Cadence must be anchored in clear strategic outcomes, or organizations risk making faster decisions about the wrong work.
At the same time, portfolio agility depends on technology foundations. Many PMOs still treat technology as delivery support rather than strategic infrastructure, yet legacy architecture and technical debt often dictate how quickly priorities can shift. Architectural health and platform investment must therefore become part of portfolio decision-making, not optional delivery concerns.
When intent, cadence, and technology constraints are aligned, progress becomes observable, comparable, and actionable. That is how strategy becomes execution, and execution becomes impact.