From Balanced Scorecard to TOGAF: Turning Strategy Execution into an Engine

February 25, 2026

Over the years, I've observed a pattern across organizations.

Strategy is rarely the problem.

Execution is.

Leadership teams define priorities. Strategic themes are articulated. Initiatives are announced. Energy is high at the beginning of the year.

But somewhere between intention and impact, momentum diffuses.

What's missing is not intelligence.
It's structure.

This Architecture Note reflects on how a strategy execution model built around the Balanced Scorecard evolved, and how, viewed through the lens of TOGAF, it was actually Enterprise Architecture in motion.

When Initiatives Are Just Activities

In many organizations, internal initiatives emerge organically,

• Employee engagement programs
• University partnerships
• Certification drives
• Process maturity efforts
• Website improvements
• Department-level improvement campaigns

They are often volunteer-driven. Passion-based. Well-intentioned.

But without architectural alignment, they risk becoming activity instead of capability.

The turning point comes when you ask a different question,

Are these initiatives systematically moving the enterprise toward a defined target state?

That is an architecture question.

Strategy as a System, Not a Presentation

The Balanced Scorecard introduced an important discipline; strategy must be measurable.

Strategy maps clarified cause and effect,

• Learning & Growth enables
• Process Excellence, which drives
• Customer Value, which delivers
• Financial Outcomes

But what became evident over time was this,

The strategy map was not just a visualization tool.
It was an architectural blueprint of the enterprise.

Each objective implied a capability.
Each KPI implied a performance requirement.
Each initiative implied a structural intervention.

Without explicitly calling it architecture, the organization was defining a target operating model.

Where TOGAF Changes the Lens

When later studying TOGAF, something became clear.

What had been practiced through the Balanced Scorecard was structurally aligned with,

• Architecture Vision
• Business Architecture
• Capability Gaps
• Work Packages
• Migration Planning
• Governance Cycles

The terminology was different.

The intent was identical.

TOGAF formalizes the structural side of transformation.

Balanced Scorecard formalizes the performance side.

One defines how the enterprise must evolve.
The other ensures that evolution produces measurable value.

Together, they form a closed loop.

Initiatives as Capability Increments

The real shift happened when initiatives stopped being "good ideas" and became,

• Deliberate capability investments
• Time-bound transformation units
• Measurable value contributors

An initiative to improve process maturity was no longer a compliance activity.

It was,

• A Business Architecture enhancement
• A risk-reduction mechanism
• A maturity uplift
• A measurable performance shift

An initiative to improve university relationships was not HR marketing.

It was,

• A talent pipeline architecture intervention
• A long-term capability sustainability mechanism

When initiatives are framed this way, they stop being optional enthusiasm projects.

They become transition architectures.

Governance Is What Sustains Momentum

Annual workshops. SWOT discussions. Strategy maps. KPIs.

Those are not administrative rituals.

They are governance mechanisms.

When initiative outcomes are quantified,
When contributions are recognized,
When performance systems reflect enterprise value creation,

Strategy execution becomes self-reinforcing.

Over time, a pattern emerges.

Leaders who consistently drive initiatives develop broader enterprise visibility.
Cross-functional collaboration becomes normal.
Transformation becomes expected, not exceptional.

This is where the "flywheel" effect described in Good to Great becomes visible in practice.

Not as a motivational metaphor, but as an operational outcome of structural alignment and consistent governance.

The Hidden Insight

Most organizations operate in one of two modes,

• Measurement without structure
• Structure without measurable impact

Balanced Scorecard alone risks the first.

TOGAF alone risks the second.

But when strategic objectives are mapped to capabilities,
When capabilities are realized through structured work packages,
When work packages are measured through KPIs,
When governance reinforces accountability,

Strategy execution stops depending on individual heroics.

It becomes institutional.

That is the difference between transformation as an event and evolution as a system.

Architecture Beyond IT

One of the biggest misconceptions about Enterprise Architecture is that it belongs to IT.

It does not.

Enterprise Architecture is about,

• Capability design
• Structural alignment
• Strategic traceability
• Change governance

The tools may vary.
The vocabulary may differ.

But when strategy, structure, execution, and measurement operate as one coherent system, that is Enterprise Architecture.

Whether you call it TOGAF or not.

Looking back, the real insight was this,

Strategy should not be managed as a document.

It should be engineered as a system.

A system where,

• Vision defines direction.
• Architecture defines structure.
• Initiatives define movement.
• KPIs define proof.
• Governance defines continuity.

When those elements align, momentum builds.

And once momentum builds, transformation no longer requires force.

It sustains itself.