Home  /  Hoshin Alignment
Pillar V · Flagship

Strategy that survives the journey from headquarters to a desk.

Most alignment fails silently. Intent is set in one hemisphere and interpreted in another, and nobody discovers the drift until a quarter has been spent. Hoshin Alignment makes the descent explicit and the cadence non-negotiable.

The Cascade

Four levels, and no unexplained gaps between them.

Level 01

Global CEO Priorities

The small number of things the enterprise has decided actually matter this year.

Level 02

GCC Scorecard

Translated into what the centre specifically owns, with measures it can genuinely move.

Level 03

Function Objectives

Distributed across engineering, operations, analytics and shared services.

Level 04

Individual KRAs

Every person able to trace their quarter back to a line in the boardroom.

I

Strategy Cascade

Global priorities converted into centre scorecards and individual KRAs through a governed Hoshin matrix.

II

Performance Visibility

Live dashboards headquarters can read without a translation layer or a monthly deck.

III

Cultural Alignment Programme

Deliberate work on the behaviours, rituals and language that make a distant centre feel like the same company.

IV

Productivity Architecture

Value stream mapping and output-based measures, replacing effort proxies with evidence of delivered value.

V

Cadence Governance

Weekly, monthly and quarterly review rhythms with defined owners, escalation paths and decision rights.

The Hoshin Matrix

The instrument itself, not a description of it.

Four quadrants around a single breakthrough intent. Each quadrant correlates to its neighbours, which is what prevents an objective existing without a measure, or a measure without an owner.

North · Breakthrough objectives — three to five years

  • Own end-to-end product capability for two global platforms
  • Become the group’s primary analytics capability

West · Annual objectives

  • Transfer two platform modules to full centre ownership
  • Establish a data engineering function of thirty
  • Reduce dependency on external vendors by half
Breakthrough IntentFrom delivery capacity to owned capability

East · Metrics and targets

  • Modules under sole centre ownership
  • Vendor spend as a proportion of function cost
  • Defect escape rate against group standard
  • Retention of the critical population

South · Improvement priorities and owners

  • Capability ladder for data engineering — CHRO mandate
  • Knowledge transfer protocol — function heads
  • Vendor exit sequencing — centre head
A Worked Example

One enterprise priority, traced to a named individual objective.

This is the artefact that distinguishes a cascade from an assertion. If the trace cannot be drawn, the alignment does not exist — whatever the strategy deck says.

Level 01 · Global CEO priority

“Reduce time-to-market for new product releases across all regions.”

Measure  Release cycle time, group-wide

Level 02 · GCC scorecard

“The centre assumes full release-engineering ownership for two platforms.”

Measure  Cycle time on owned platforms; number of releases requiring headquarters intervention

Level 03 · Function objective

“Platform Engineering delivers automated release validation for both platforms by Q3.”

Measure  Proportion of validation automated; manual gate count

Level 04 · Individual KRA

“Build and operate the automated regression suite for Platform B.”

Measure  Suite coverage; false-positive rate; time from commit to validated build

An engineer who can trace their quarter to a line the chief executive actually said is a different employee from one who cannot. That difference is what Pillar V is for.
Cadence Governance

The rhythm, with owners and decision rights attached.

Weekly

Operating review

OwnerChief of Staff

InputDelivery position, blockers, escalations

DecidesReallocation within agreed structure

Monthly

Scorecard review

OwnerCentre head

InputScorecard movement, leading indicators, people position

DecidesCorrective action within the annual objective

Quarterly

Catchball and reset

OwnerClient sponsor

InputQuarter performance; proposed objective amendment from function heads

DecidesObjective revision; resource reallocation across functions

Annual

Hoshin planning

OwnerEnterprise leadership with centre head

InputBreakthrough intent; prior-year evidence

DecidesNext annual objectives and matrix

Catchball is the part most programmes omit. Objectives move downward and evidence moves upward — a cascade with no return path is dictation, and it decays within two quarters.

Culture & Productivity

The two dimensions most programmes assert rather than architect.

Dimension III

Cultural Alignment

Behaviours are designed, installed and measured rather than described in a values statement. The work covers decision-making norms, escalation behaviour, meeting conduct, written communication standards, and the specific rituals that make a centre five thousand miles away feel like the same company.

  • Behaviour definition tied to observable action
  • Ritual design and installation calendar
  • Manager capability as the transmission mechanism
  • Measurement through the anonymous instrument, not sentiment surveys
Dimension IV

Productivity Architecture

Value stream mapping applied to knowledge work, replacing utilisation and effort proxies with evidence of delivered value. The shift is from measuring how busy a centre is to measuring what leaves it.

  • Value stream mapping by function
  • Wait-state and handoff identification
  • Output measures replacing activity measures
  • Baseline established before any AI transition begins
The Resource Pool

Join as a GCC Resource.

Successgini maintains a proprietary pool of enterprise-ready professionals and fractional executives who build and operate capability centres. Registration is open to those with genuine centre-building experience.