Change & Transform™

Architect the change. Build adoption. Sustain the result.

Most change fails in the space between intent and adoption. Change & Transform™ is the horizontal value stream that closes it — one method, applied at any scale, for any type of change.

The principle

Change does not fail because people resist. It fails because the system was never designed to hold it.

This is not a sixth pillar of the operating framework. It is a value stream that runs across FOUNDATION™, SIMPLIFY™, LEAD™, GROW™ and ARC™ — using all five to move a change from intent to sustained performance, whether that change is a single process or an entire enterprise.

Compass partners with leadership to architect the change, build adoption deliberately, execute through disciplined cycles, and embed the result so it survives the people who launched it.

Transformation Architecture

Clarify present reality, strategic intent, desired outcomes, scope, governance, dependencies and the operating conditions success requires.

Change Adoption

Translate enterprise change into the Awareness, Desire, Knowledge, Ability and Reinforcement individuals and stakeholder groups need to adopt a new way of working.

Execution and Continuous Improvement

Use chartering, Gemba, performance measures and ARC™ cycles to convert assumptions into learning, decisions, ownership and measurable execution.

Institutionalization and Scale

Embed what works into operating rhythms, processes, systems, leadership expectations, measures and organizational capability.

The philosophy

Change begins with an equation, not an announcement.

Gleicher’s Formula for Change is the cleanest statement of why change moves or stalls. Dissatisfaction with present reality, multiplied by a clear vision of the future, multiplied by credible first steps, must exceed the resistance to leaving the current state.

D × V × F1 > R

It is multiplication, not addition. If any factor is zero, the product is zero — no vision, no dissatisfaction, or no first step, and nothing moves regardless of how strong the other two are.

D

Dissatisfaction

The felt cost of present reality. Until the cost of staying the same is named out loud, nothing moves.

Worked in FOUNDATION™

V

Vision

A specific picture of the future state — what work looks like once the change holds.

Worked in SIMPLIFY™

F₁

First Steps

Near-term action small enough to start and real enough to matter. Momentum, not a launch event.

Worked in LEAD™

R

Resistance

Fear, habit, loss, workload, and leadership systems still rewarding the old behavior.

Worked in GROW™

Download the Gleicher sheetDownload the facilitator guide

Gleicher’s Formula for Change is commonly attributed to David Gleicher and later refined by Kathleen Dannemiller.

Momentum

The flywheel turns on direction, not force.

Jim Collins described the flywheel: no single push turns it, but consistent pushes in one direction compound into momentum that becomes hard to stop. That is what ARC cycles do to a change. Each cycle — assess, refine, commit — is another push in the same direction. The discipline is not the size of the push. It is the direction never changing.

A = Assess, R = Refine, C = Commit. Each cycle is one push.

How adoption spreads

  • InnovatorsMove first on conviction. Useful for proving the future state is real.
  • Early AdoptersMove on credibility. They translate the change for peers.
  • Early MajorityMove when the new way is visibly working and supported.
  • Late MajorityMove when the old way is no longer reinforced or rewarded.
  • LaggardsMove last, and often for reasons worth hearing — unresolved risk, capacity, or a gap in the design.

These are positions on a curve at a point in time, not personality types. Where a group sits is information about the system: the case for change, the design, the support, or what leadership is still rewarding.

The architecture

Four layers, operating at the same time.

Delivery and adoption are not sequential and they are not separate workstreams. The charter governs the work, ADKAR® moves the people, the four pillars execute, and ARC™ improves the system as it runs.

Layer 1 — Charter the work

  • Present Reality
  • Strategic Intent
  • Future State
  • Essential Outcomes
  • Scope
  • Ownership
  • Measures
  • Risks

The charter establishes what the organization intends to change, and why.

Layer 2 — Move people through adoption

  • Awareness
  • Desire
  • Knowledge
  • Ability
  • Reinforcement

The ADKAR® individual adoption journey, from Prosci.

Layer 3 — Execute through the operating framework

  • FOUNDATION™
  • SIMPLIFY™
  • LEAD™
  • GROW™

Readiness and truth, then the essential change, then execution and capability, then scale and ownership.

Layer 4 — Improve through ARC™

  • Assess
  • Refine
  • Commit

ARC runs continuously beside the value stream: assess reality, refine the system, commit to decisions and action.

ADKAR® is a registered trademark of Prosci, Inc. Awareness, Desire, Knowledge, Ability and Reinforcement is the Prosci model for individual change, referenced here with attribution — not Compass intellectual property.

The value stream

Seven stages. The same seven, at every scale.

A three-week sprint and a three-year ERP transformation run the same stages. What changes is duration, governance and the number of ARC cycles inside them — never the sequence.

  1. 01

    Frame

    Establish the business case, strategic intent, sponsor, initial scope and desired outcomes.

    Pillar · ADKAR® · ARC
    FOUNDATION™ · Awareness · Assess
    Outputs
    Initial Transformation Charter
  2. 02

    Assess

    Evaluate organizational readiness, stakeholder impact, capacity, risk, adoption barriers and system conditions.

    Pillar · ADKAR® · ARC
    FOUNDATION™ · Awareness · Desire · Assess
    Outputs
    Readiness heat map · Stakeholder impact map · Initial ADKAR® assessment · Risk and dependency profile
  3. 03

    Charter

    Confirm the future state, essential outcomes, scope, governance, decision rights, measures, resources and the ARC event question.

    Pillar · ADKAR® · ARC
    FOUNDATION™ · SIMPLIFY™ · Awareness · Desire · Knowledge · Refine · Commit
    Outputs
    Approved Compass Transformation Charter · Formal ARC kickoff
  4. 04

    Design

    Translate the charter into future-state processes, roles, technology, communication, learning requirements, measures and implementation plans.

    Pillar · ADKAR® · ARC
    SIMPLIFY™ · Knowledge · Refine
    Outputs
    Current-to-future-state map · Adoption strategy · Communication strategy · Manager enablement plan · Training and capability plan
  5. 05

    Activate

    Launch the change, run ARC events, enable managers, build ability, observe the work at Gemba and resolve emerging barriers.

    Pillar · ADKAR® · ARC
    LEAD™ · Knowledge · Ability · Commit → Assess → Refine
    Outputs
    ARC decisions and action register · Implementation rhythm · Adoption scorecard · Issue and system-signal log
  6. 06

    Stabilize

    Measure adoption and business performance, address workarounds, strengthen ability, refine the system and reinforce expectations.

    Pillar · ADKAR® · ARC
    LEAD™ · GROW™ · Ability · Reinforcement · Assess · Refine
    Outputs
    Adoption and performance review · Refined standard work · Corrective ARC cycles · Leadership reinforcement actions
  7. 07

    Institutionalize

    Embed the change into governance, standard work, measures, onboarding, leadership routines, capability systems and continuous improvement.

    Pillar · ADKAR® · ARC
    GROW™ · Reinforcement · Commit
    Outputs
    Institutionalization plan · Benefit-realization review · Ownership transfer · Scale, refine or stop decision

One method, four scales

Size the work to the change, not the change to the work.

Days to several weeks

ARC Sprint

Focused improvement inside one process, team or work area.

  • Reducing quote cycle time
  • Simplifying onboarding
  • Improving meeting effectiveness
  • Eliminating a production bottleneck
  • Clarifying a recurring decision

Several weeks to several months

ARC Project

A defined body of work with outcomes, owners, deliverables and measures.

  • Redesigning a hiring process
  • Implementing a reporting system
  • Standardizing engineering reviews
  • Introducing a new workflow
  • Improving order entry

Several months to a year

ARC Initiative

A strategic or cross-functional effort composed of multiple projects and ARC cycles.

  • Product portfolio simplification
  • Sales-process redesign
  • Value-stream improvement
  • Organizational redesign
  • Leadership operating-system implementation

One to several years

ARC Transformation

Enterprise-scale change: coordinated initiatives, projects, adoption journeys and recurring ARC events.

  • ERP transformation
  • Digital or AI transformation
  • Founder succession
  • Post-merger integration
  • Global operating-model redesign

The instruments

Eight working instruments, used in one sequence.

Each instrument produces a decision or an artifact the next one depends on. Nothing is optional and nothing is filler.

  1. Transformation Charter
  2. Readiness Diagnostic
  3. Stakeholder and ADKAR® Assessment
  4. ARC Event Charter
  5. Assess → Refine → Commit
  6. Execute and observe at Gemba
  7. Adoption and Performance Scorecard
  8. Reinforce and institutionalize
  9. Next ARC cycle
01Frame · Assess · Charter

Compass Transformation Charter™

Defines present reality, strategic intent, future state, essential outcomes, scope, ownership, governance, measures and risk in one document.

When
Stages 1–3, before any work begins
Produces
The approved charter that governs the entire effort
  • Present reality
  • Strategic intent
  • Desired future state
  • Essential outcomes
  • Scope and boundaries
  • Sponsor and owner
  • Governance and decision rights
  • Measures
  • Risks and dependencies
  • Stakeholder impact
  • Initial ARC question
02Assess

Change Readiness Diagnostic™

Assesses the leadership, operating-system, adoption and execution conditions most likely to accelerate — or constrain — the change.

When
Stage 2, before the charter is approved
Produces
A readiness heat map organized by FOUNDATION, SIMPLIFY, LEAD and GROW
  • Leadership alignment
  • Case for change
  • Trust and organizational climate
  • Available capacity
  • Decision clarity
  • Process and technology readiness
  • Manager preparedness
  • Competing priorities
  • Change fatigue
  • Reinforcement infrastructure
03Assess · Design

Stakeholder Impact & Adoption Map™

Identifies who is affected, what changes for them, and the engagement each group requires.

When
Stages 2 and 4
Produces
A stakeholder map with adoption position and likely ADKAR® barriers
  • Who is affected
  • What changes for them
  • Influence and impact
  • Current support
  • Likely concerns
  • Adoption position
  • Required engagement
  • Likely ADKAR® barriers
04Assess · Activate · Stabilize

ADKAR® Barrier Diagnostic

Assesses each stakeholder population across Awareness, Desire, Knowledge, Ability and Reinforcement — and names the system condition behind each gap.

When
Stages 2, 5 and 6
Produces
Barrier profile with probable system cause per gap
  • Awareness
  • Desire
  • Knowledge
  • Ability
  • Reinforcement
05Charter · Activate

ARC Event Charter™

Converts the transformation charter into one focused improvement or decision event.

When
Stage 3 onward, at every ARC cycle
Produces
A scoped ARC event with decision authority and success measures
  • ARC question
  • Problem statement
  • Evidence and baseline
  • Event scope
  • Participants
  • Decisions required
  • Pre-work
  • Expected outputs
  • Decision authority
  • Success measures
06Activate

ARC Working Board™

The working surface of an ARC event, in three sections: Assess, Refine, Commit.

When
Stage 5, during every ARC event
Produces
Root causes, options tested, decisions with owners and dates
  • Assess — facts, process reality, stakeholder experience, root causes, constraints, barriers, risks
  • Refine — future-state options, simplification, assumptions to test, system changes, adoption actions, experiments
  • Commit — decisions, owners, milestones, resources, measures, escalation triggers, next review
07Activate · Stabilize · Institutionalize

Adoption & Performance Scorecard™

Measures adoption and business performance side by side, so technical completion is never mistaken for success.

When
Stages 5–7
Produces
One scorecard: adoption measures and performance measures
  • Adoption — awareness, support, training completion, demonstrated proficiency, system usage, workaround frequency, manager reinforcement, barrier trends
  • Performance — quality, cost, delivery, cycle time, throughput, productivity, customer outcomes, margin and benefit realization
08Institutionalize

Reinforcement & Institutionalization Plan™

Defines how the new way becomes normal operating practice — and who owns it after the project ends.

When
Stage 7
Produces
Standard work, governance, measures and a capability transfer plan
  • Standard work
  • Governance
  • Performance expectations
  • Leadership routines
  • Measures
  • Recognition
  • Accountability
  • Onboarding
  • Learning ownership
  • Process ownership
  • ARC review triggers
  • Capability transfer

The instruments themselves are used with clients under a Compass engagement. Begin a conversation to see them applied to your change.

Resistance, read correctly

Every adoption gap points at a system condition.

When adoption stalls, the diagnostic question is never “who is resisting.” It is which condition the organization failed to create.

  • Awareness gapThe business case is inconsistent or unclear.
  • Desire gapStakeholders perceive loss, risk or exclusion.
  • Knowledge gapThe future-state process or role is undefined.
  • Ability gapTools, capacity, workflow or practice are insufficient.
  • Reinforcement gapLeadership systems still reward the former behavior.

What changes

  • Activity begins before alignment

    Work starts from an approved charter

  • Change and project management operate separately

    Delivery and adoption operate as one system

  • Resistance is treated as a people problem

    Resistance is examined as system signal data

  • Training is treated as adoption

    Knowledge is converted into demonstrated ability

  • Projects close at technical completion

    Change closes after adoption and benefit realization

  • Lessons learned are documented after the fact

    ARC improves the system continuously

  • Ownership stays with the project team

    Capability and ownership transfer into operations

Where it applies

Type-agnostic by design.

The value stream does not change with the type of change. The evidence required at each stage does.

  • Enterprise and operating-model transformation
  • ERP and digital transformation
  • AI adoption
  • Organizational redesign
  • Founder succession
  • Post-merger integration
  • New facility or value-stream launch
  • Process improvement
  • Leadership-system implementation
  • Product and portfolio transformation
The five disciplines →ARC™, the renewal engine →The operating system →

The next step

Start with the change in front of you.

A short, confidential conversation about the change already underway — what is stalling, what the organization is not yet set up to hold, and what would have to be true for it to stick.

Begin with Present RealityRead the blueprint

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