Install · Transfer

Operating Cadence Install

A plan that lives in a document is an opinion. The same plan, with baselined measures, dated actions and a standing agenda, run every week in one place, is a management system. Compass architects the system first, then installs it in a live platform and hands over the chair.

The position

The platform is the deck. Compass designs what crosses it.

Small and mid-sized businesses rarely fail for want of software. They open a capable platform, type in what they already believed, and discover a month later that the measures have no baselines, the priorities exceed the hours available, and the meetings still run the way they always did. The tool faithfully records the same problem in a cleaner format.

Compass does the architecture first — plan, measures, action plans, meeting map — and only then loads it. Leaders open a populated system on day one, run the first cycle with Compass in the chair, and take the chair themselves in the second. Compass leaves architects, not dependency.

What the platform holds

Four objects, each architected before it is loaded

Every one of these can be typed straight into a platform in an afternoon. Each is also the place where an operating system quietly fails. The desk beneath each object is where Compass produces the content that gets loaded.

Object 01

The one-page strategic plan

“What are we trying to become, and what must be true this year?”

Architected first
Present reality, strategic intent, future state and the essential outcomes — written as decisions, not aspirations, with a named owner against each one.
Loaded on day one
A single page: purpose, three-year picture, annual outcomes, quarterly priorities, and the owner of each.
Skip the architecture, and
A plan page filled with departmental wish lists. Nothing is refused, so nothing is prioritized, and the platform becomes a filing cabinet.

Produced at these desks

Object 02

Metrics and the scorecard

“How will we know, weekly, whether the plan is working?”

Architected first
A measure set with a baseline pulled from the system of record, a target, a frequency, a red/amber/green rule and one accountable person per line.
Loaded on day one
A weekly scorecard with real baselines, so the first review compares performance against a number rather than an opinion.
Skip the architecture, and
Measures invented at go-live with estimated baselines. Every reading is arguable, and the scorecard is quietly abandoned by quarter two.

Produced at these desks

Object 03

Action plans and priorities

“Who is doing what, by when, and what does done look like?”

Architected first
Priorities sized against real capacity, sequenced by dependency, each with a completion test that a third party could verify.
Loaded on day one
Quarterly priorities broken into dated actions with single owners, and the dependencies between them made visible.
Skip the architecture, and
Forty priorities held by eight people. Everything is in progress, nothing closes, and the platform records the drift in detail.

Produced at these desks

Object 04

Meeting agendas and minutes

“Where do decisions get made, and how do they leave the room?”

Architected first
A meeting map: which forum owns which decision, at what cadence, with a standing agenda and a rule for what escalates and what does not.
Loaded on day one
A standing agenda per forum, decisions and commitments captured as they are made, and last period's actions opened first.
Skip the architecture, and
Status meetings that review the same slide each month. Decisions are made in the corridor, and the minutes record attendance rather than accountability.

Produced at these desks

The install

Five steps, each with a gate that has to pass

  1. 01Read the current cadence

    Week 1

    Sit in the meetings that already exist, list the measures already reported, and find where decisions are actually made. Most organizations already run a cadence — it is simply undeclared.

    Gate — Every recurring leadership forum is named, with its owner, frequency and the decision it holds.

  2. 02Architect the plan and the measures

    Weeks 2–4

    Write the one-page plan and the measure set at a Compass desk, before any platform is opened. Baselines come from the system of record.

    Gate — One page, signed by the executive sponsor, with a baseline against every measure.

  3. 03Size the priorities against capacity

    Week 4

    Sequence the quarterly priorities, test them against the hours that actually exist, and refuse what does not fit. This is where the plan becomes deliverable.

    Gate — Priority count fits stated capacity, each with one owner and a completion test.

  4. 04Load and go live

    Week 5

    The architected plan, measures, priorities and meeting agendas are loaded into the platform. Leaders arrive to a populated system, not an empty one.

    Gate — First scorecard review runs from real data, and every line has a person's name against it.

  5. 05Run, then transfer

    Quarters 1–2

    Compass facilitates the first cycle, then hands the chair to the client's own leaders. ARC™ — Analyze, Refine, Commit — reviews the cadence itself each quarter.

    Gate — Two consecutive cycles run by the client's leaders without Compass in the chair.

Before the platform is opened

Five tests that decide whether a cadence will hold

If any of these fails, the install is not refused — the failing condition is fixed first. That work is short, and it is the difference between a system that survives quarter two and one that does not.

  • Test 01

    One executive sponsor is named as a person, not a committee.

    The cadence collapses the first time a priority has to be refused if nobody owns the refusal.

  • Test 02

    Every proposed measure has a source system and a current baseline.

    A measure without a baseline cannot show movement, and the first review becomes a debate about the number.

  • Test 03

    The leadership team can state the annual outcomes without reading them.

    If the plan is not held in the room, no platform will hold it.

  • Test 04

    A weekly leadership forum already exists, or a date is set for one.

    The platform records a cadence; it does not create one.

  • Test 05

    Priorities have been sized against real capacity, and some were refused.

    A list nobody has cut is a wish list, and the first quarter will prove it.

The wider readiness read sits in the Compass Enterprise Readiness Assessment™.

How it is bought

Included at the flagship tier, licensed separately beneath it

Where it sitsPlatformWhat Compass does
Compass Enterprise Architecture Engagement™IncludedThe cadence install sits inside INSTALL and TRANSFER. Platform licensing is arranged in the client's name; Compass architects, loads, facilitates the first cycle and transfers the chair.
Executive & Leadership Advisory · ForumsSeparate subscriptionThe client licenses the platform directly. Compass architects the plan, measures and meeting map, then reviews the cadence at agreed intervals.
Standalone cadence installSeparate subscriptionA defined five-week install for organizations that want the operating rhythm without a full architecture engagement — with the readiness tests applied first.
Begin a conversationSee the offerings

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.

Not sure? Answer three questions Or browse every instrument