← Case studies

Industrial group · ~$210M revenue · four business units, one shared plant network

Renewing the operating system of a $210M industrial group that had outgrown its own design

An ARC™ renewal loop retired 23 of 31 competing initiatives, returned 22 points of executive calendar from work owned two levels down, and lifted EBITDA margin 2.4 points in eighteen months — with no new strategy.

Disciplines deployed
SIMPLIFY → LEAD
Measurement window
18 months
Measures reported
4

Condition 08 of eight

The operating system itself needs renewal

The design was right for a company you no longer are. The organization improves inside a limit no one has moved.

All eight conditions

Present reality

Nothing was broken. The management system that carried the group from $60M to $210M — a monthly review built around unit P&Ls, a rolling initiative list and an annual plan — was still being run faithfully, and it was producing less every year. Thirty-one initiatives were open, most of them started by a prior year's priority, and the executive team spent its meetings hearing status rather than deciding anything.

Constraint

The operating system had never been re-designed for the company the group had become: it measured units that now shared capacity, reviewed work no one had authority to stop, and had no mechanism to retire an initiative or a measure once it stopped earning its place. Improvement kept moving results toward the limit of a design nobody had touched in nine years.

Intervention — architecture installed

ARC™ renewal read of the whole operating system — Assess what the current design was actually producing, Refine the measures, cadence and decision rights that no longer fit a shared-capacity network, Commit to a bounded portfolio with named owners and stop criteria. Cadence re-architected around enterprise value streams instead of unit P&Ls, initiative portfolio cut to what the enterprise could staff and gate, and a standing quarterly renewal cycle installed so the design is re-read rather than inherited.

FOUNDATION → SIMPLIFY → LEAD → GROW

Mapped to the operating system

What was architected inside each discipline, and the measured consequence. Disciplines held out of scope are shown with the reason — nothing is implied by omission.

  1. 1. FOUNDATION

    Build

    Held out of scope

    Deliberately not reopened: structure, ownership and the strategic frame were sound. The design fault was in what the operating system reviewed and retired, not in the foundation beneath it.

    Result: Renewal work stayed inside eighteen months because the foundation did not have to be rebuilt to move the limit.

    FOUNDATION
  2. 2. SIMPLIFY

    Focus

    Loaded in this engagement

    The initiative portfolio bounded to what the enterprise could staff and gate, with stop criteria written for every survivor, and the cadence re-architected around enterprise value streams rather than business-unit P&Ls that now shared capacity.

    Result: Active enterprise initiatives fell from 31 to 8 (−23).

    SIMPLIFY
  3. 3. LEAD

    Execute

    Loaded in this engagement

    Decision rights and review questions rewritten so each meeting decides rather than hears status, with owners, dates and standing evidence at every gate.

    Result: Executive time on work owned two levels down fell from 41% to 19% (−22 pts) and commitments closed on the promised date rose from 61% to 92%.

    LEAD
  4. 4. GROW

    Scale

    Held out of scope

    Held out of scope: the group did not need more demand, it needed a design capable of converting the demand it already had. Growth work resumed only after the renewal cycle was running.

    Result: EBITDA margin rose 2.4 points with no new strategy and no new growth spend.

    GROW

ARC™ — the renewal loop around all four

ARC™ is the engagement: a standing quarterly renewal cycle now re-reads measures, cadence and portfolio against the company the group has become, and has already retired two measures and one review that had stopped earning their place.

ARC™ →

Measured result — what moved, and by how much

Industrial group · ~$210M revenue · four business units, one shared plant network — measured change over 18 months
MeasureBeforeAfter (18 months)Change
Active enterprise initiatives318−23
Executive time on work owned two levels down41%19%−22 pts
Commitments closed on the date promised61%92%+31 pts
EBITDA margin9.6%12.0%+2.4 pts
Before → after, measure by measure · 18 months
  • Active enterprise initiatives

    −74%

    Before31
    After8

    Standardized against Concurrent enterprise initiatives Initiatives with a named owner and a live commitment; retired work counts as closed.

  • Executive time on work owned two levels down

    −22 pts

    Before41%
    After19%

    Standardized against Executive time on work owned two levels down Two-week calendar sample of the eight-person executive team at both readings.

  • Commitments closed on the date promised

    +31 pts

    Before61%
    After92%

    Standardized against Commitments closed on the date promised Commitments recorded in the operating cadence; re-dated commitments count as missed.

  • EBITDA margin

    +2.4 pts

    Before9.6%
    After12%

    Standardized against EBITDA margin Trailing twelve months, same adjustments at both readings.

The group now re-reads its own operating design every quarter instead of inheriting it, and stops work on evidence rather than on fatigue.

Transfer — what the client now owns

The executive team runs the ARC™ renewal cycle itself — it owns the assess read, the refine decisions and the commit gate, and has completed two full cycles without Compass in the room.

Compass leaves architects, not dependency.

Client identities, brands, and locations are withheld under confidentiality. Metrics are client-reported and measured over the window shown; they describe those engagements and are not a projection of results for any other enterprise.

Start with your own present reality

Every engagement above began with an honest read of the architecture already producing the results. Score yours, or schedule a conversation.

Share this

Share on LinkedIn

Not sure where to start?

Three questions, and we point you to the right instrument.

Under a minute. From this page, most leaders begin with The organization.