Change & Transformation · supporting methodology

The deeper method, placed beneath the five phases.

The public page teaches five phases and the nine-step methodology beneath them. The supporting material — the equation, the layers, the seven gates, the team, the scales, the published documents, the research — is here in full, each block labeled with the step it serves. Nothing was deleted, and none of it is a competing process.

Change & Transformation

Strategic Intent sets direction. 80/20 focuses. Kotter mobilizes. ADKAR enables. CompassOS orchestrates. ARC sustains.

← The process architecture carries the nine steps at executive altitude. This page is the depth beneath them.

The equation

Change begins with an equation, not an announcement.

Serves03 Define the Change 05 Assess Readiness

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. It is read in step 3 as the case for change and re-read in step 5 as the organizational readiness view.

D × V × F₁ > 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.

Dissatisfaction

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

Worked in FOUNDATION

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

Resistance

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

Worked in GROW

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.

Serves08 Execute & Enable Adoption 09 Sustain / ARC

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.

Flywheel momentum diagram: a proportionate wheel turning clockwise, symbolizing compounding directional force in change work — Jim Collins on the flywheel concept from *Good to Great*.
Watch the discussion

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 earlier integrated model

Four layers, operating at the same time — now placed inside the nine steps.

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. The layers still hold; the nine steps are the order in which they are worked.

Layer 1 — Charter the work

Serves03 Define the Change

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

The charter fields are step 3's product.

Layer 2 — Move people through adoption

Serves05 Assess Readiness 06 Configure the Intervention 08 Execute & Enable Adoption

The ADKAR® individual adoption journey, from Prosci.

ADKAR® is read in the individual readiness view, configured in step 6 and worked in step 8.

Layer 3 — Execute through the operating framework

Serves every step

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

FOUNDATION, SIMPLIFY, LEAD and GROW carry every step; the discipline never becomes a sixth box.

Layer 4 — Improve through ARC™

Serves09 Sustain / ARC

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

ARC™ runs beside every step and closes the sequence.

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 seven-stage value stream

Seven stages, seven gates — and the step each one now serves.

The seven stages were the earlier spine of this page. They remain valid as the gate detail beneath the nine steps; each stage below names the step it belongs to, and the full gate — question, pass, evidence, owner, failure mode — is on its own page.

01
Frame
Serves01 Strategic Intent 02 80/20 Focus 03 Define the Change
Establish the business case, strategic intent, sponsor, initial scope and desired outcomes.
The gate
What is the problem, in measurable terms, and who owns it?
Gate detail, desks and instruments · 1
Pillar · ADKAR® · ARC
FOUNDATION · Awareness · Assess
Outputs
Initial Transformation Charter
02
Assess
Serves04 Determine Intervention Breadth & Depth 05 Assess Readiness
Evaluate organizational readiness, stakeholder impact, capacity, risk, adoption barriers and system conditions.
The gate
Is this organization able to absorb and sustain the change?
Gate detail, desks and instruments · 3
Pillar · ADKAR® · ARC
FOUNDATION · Awareness · Desire · Assess
Outputs
Readiness heat map · Stakeholder impact map · Initial ADKAR® assessment · Risk and dependency profile
03
Charter
Serves03 Define the Change 06 Configure the Intervention
Confirm the future state, essential outcomes, scope, governance, decision rights, measures, resources and the ARC event question.
The gate
Are scope, governance, decision rights and measures agreed in writing?
Gate detail, desks and instruments · 2
Pillar · ADKAR® · ARC
FOUNDATION · SIMPLIFY · Awareness · Desire · Knowledge · Refine · Commit
Outputs
Approved Compass Transformation Charter · Formal ARC kickoff
04
Design
Serves06 Configure the Intervention
Translate the charter into future-state processes, roles, technology, communication, learning requirements, measures and implementation plans.
The gate
Has the future state been designed — process, roles, measures — before build?
Gate detail, desks and instruments · 1
Pillar · ADKAR® · ARC
SIMPLIFY · Knowledge · Refine
Outputs
Current-to-future-state map · Adoption strategy · Communication strategy · Manager enablement plan · Training and capability plan
05
Activate
Serves07 Mobilize 08 Execute & Enable Adoption
Launch the change, run ARC events, enable managers, build ability, observe the work at Gemba and resolve emerging barriers.
The gate
Are decisions being made, and is ability being built where the work happens?
Gate detail, desks and instruments · 5
Pillar · ADKAR® · ARC
LEAD · Knowledge · Ability · Assess → Refine → Commit
Outputs
ARC decisions and action register · Implementation rhythm · Adoption scorecard · Issue and system-signal log
06
Stabilize
Serves08 Execute & Enable Adoption 09 Sustain / ARC
Measure adoption and business performance, address workarounds, strengthen ability, refine the system and reinforce expectations.
The gate
Is adoption holding, and is business performance actually moving?
Gate detail, desks and instruments · 3
Pillar · ADKAR® · ARC
LEAD · GROW · Ability · Reinforcement · Assess · Refine
Outputs
Adoption and performance review · Refined standard work · Corrective ARC cycles · Leadership reinforcement actions
07
Institutionalize
Serves09 Sustain / ARC
Embed the change into governance, standard work, measures, onboarding, leadership routines, capability systems and continuous improvement.
The gate
Who owns this after the project ends — and what triggers the next review?
Gate detail, desks and instruments · 2
Pillar · ADKAR® · ARC
GROW · Reinforcement · Commit
Outputs
Institutionalization plan · Benefit-realization review · Ownership transfer · Scale, refine or stop decision

The operating table

Seven gates. One question each. A live desk beneath every one.

The value stream is only as good as the gates inside it. Each stage asks one question, passes on stated criteria, and records evidence produced by a named online instrument. Read across a row and you have the whole engagement: question, criteria, evidence, owner, and the desk where the work is actually done.

Change & Transform gates: stage, question, pass criteria, evidence, owner and the online instruments used at each gate
Stage	The question	Passes when	Evidence · owner	Do the work here
01 Frame	What is the problem, in measurable terms, and who owns it?	A named sponsor, a baseline number, and an outcome worth the effort.Skipped, and: A project with energy and no baseline — success can never be proven.Best practice for this gate →	One-page charter opening: present reality, intent, measure, owner.Executive sponsor	Project Charter Enterprise Readiness Assessment Enterprise Concentration
02 Assess	Is this organization able to absorb and sustain the change?	Readiness gaps named with an owner, and change load compared against capacity.Skipped, and: A design built on conditions that do not exist — adoption stalls at go-live.Best practice for this gate →	Readiness heat map, stakeholder impact map, ADKAR® barrier read.Sponsor with the change lead	Change Readiness Diagnostic Stakeholder Impact & Adoption Map ADKAR® Barrier Diagnostic
03 Charter	Are scope, governance, decision rights and measures agreed in writing?	Approved charter, decision rights explicit, measures baselined, ARC question set.Skipped, and: Scope drift and re-litigated decisions consuming the delivery window.Best practice for this gate →	Approved Compass Transformation Charter and governance record.Sponsor and steering group	Project Charter Governance Readiness Change Team Plan Project Methods
04 Design	Has the future state been designed — process, roles, measures — before build?	Current-to-future map, opportunities costed and ranked, adoption plan written.Skipped, and: A system installed on top of an undesigned process, hard-coding the old waste.Best practice for this gate →	Process map, improvement register with economics, adoption and enablement plan.Process owner with the design team	SIPOC Builder Process Architecture Tailored Plan Builder
05 Activate	Are decisions being made, and is ability being built where the work happens?	ARC decisions logged with owners and dates; managers observed reinforcing.Skipped, and: Training delivered, behavior unchanged, and workarounds becoming the standard.Best practice for this gate →	ARC working board, Gemba observations, live adoption measures.Change lead with line managers	ARC Working Board Gemba Observation Sheet Gemba Walk Stage Checklists
06 Stabilize	Is adoption holding, and is business performance actually moving?	Adoption and performance measured side by side; corrective ARC cycles running.Skipped, and: Green status reports over a process people have quietly abandoned.Best practice for this gate →	RAG scorecard, health-check read, corrective action register.Process owner	Adoption & Performance Scorecard Project Health Check Change & Transform Scorecard
07 Institutionalize	Who owns this after the project ends — and what triggers the next review?	Standard work, measures and ownership transferred; ARC review triggers set.Skipped, and: Regression within two quarters, and the same problem re-chartered next year.Best practice for this gate →	Institutionalization plan, benefit-realization review, ownership record.Line leadership, accepting transfer	Reinforcement & Institutionalization Plan Recognition & KPI Dashboard Change Audit

Every instrument listed here is live online. Compass leaves business architects, not dependency: the desks stay usable by the client team after transfer.

Earlier vocabulary · retained and flagged

READY → FOCUS → MOBILIZE → PERFORM → SUSTAIN, and where each band now lands.

The five-band line was the plain-language way this page once summarized the work. The nine-step process architecture supersedes it as the sequence; the bands are kept here because the printable stage briefs and the Workbench methodology phases still carry them. The mapping is explicit so nothing written under the old vocabulary is stranded.

READY
- 01 Strategic Intent
- 05 Assess Readiness
FOCUS
- 02 80/20 Focus
- 03 Define the Change
- 04 Determine Intervention Breadth & Depth
- 06 Configure the Intervention
MOBILIZE
- 07 Mobilize
PERFORM
- 08 Execute & Enable Adoption
SUSTAIN
- 09 Sustain / ARC

Printable stage briefs · earlier vocabulary

Change & Transform

Open any stage for its printable brief — what it decides, the evidence it needs, the test that closes it.See how transformation is managed

Building the team

Large change is carried by people. Design for their endurance.

Serves06 Configure the Intervention 07 Mobilize

A large initiative — an ERP implementation, an acquisition integration, a plant consolidation — is carried for eighteen to thirty-six months by people who still hold their day jobs. The program does not fail because the software is wrong. It fails when the team runs out of energy in month fourteen and no one designed for it. Team structure and recognition are architecture, not morale extras: they are chartered at Frame and governed to closeout, and they include the families who absorb the late nights.

See the roles and recognition architecture

The cadence

WeeklyTeam stand-up opens with one specific recognition, named out loud by the program lead.
MonthlyPeer-nominated change agent recognition; team health and attrition risk reviewed at steering.
Each gateMilestone marked the week it is passed — sponsor briefing, contributors named, coin or pin added.
Twice a programLetter home to the family, signed by the sponsor, at design freeze and at closeout.
Once a programFamily open house, and one awards night after the measures move.

The six rules

Recognition is chartered and budgeted at Frame — a line item in the business case, not a discretionary spend fought for in month twelve.
Released capacity is written down and honoured. Recognition cannot substitute for a day job no one took off someone's plate.
Citations name the specific act. 'Thanks for your hard work' does not register; 'you rebuilt the cycle-count standard and trained forty people' does.
Families are a named stakeholder group with their own communications, addressed to the home.
Adoption work is recognized as visibly as technical delivery, or the organization learns which one leadership actually values.
Nothing is promised that the program cannot deliver — a missed recognition commitment costs more trust than never making it.

How small work is led

A small improvement project is chartered, not launched.

Serves04 Determine Intervention Breadth & Depth 03 Define the Change

Most change is not an ERP program. It is a two-to-six-week improvement inside one process or team. The value stream does not change for small work — it compresses. Seven stages become seven short conversations governed by one charter, and the charter is written online before anything starts.

In the breadth × depth reading this is Local × Limited: all nine steps in short conversations, carried primarily by ADKAR®.

Start here

The online Project Charter

Compass already runs a live online Project Charter builder. Complete it with the sponsor in one sitting, print the branded PDF, and the improvement has a scope, an owner, decision rights and a measure before a single meeting is scheduled.

Open the Project Charter

The five rules

One charter, one owner, one measure. If any of the three is missing, the project has not started.
Six weeks maximum. Longer work is an ARC Project, chartered as such.
Adoption is measured beside performance from the first week — never assumed at closeout.
Resistance is treated as a signal about the design, not a problem with the people.
The closeout decision is explicit: scale it, refine it, or stop it.

How a small improvement project is led, stage by stage
Stage	Window	The question it answers	What leadership does	Evidence to move on
01Frame	Day 1 · 30 minutes	What is the problem, in measurable terms, and who owns it?	The sponsor names the problem, the measure and the owner out loud. No team is stood up without those three.	One-line problem statement with a baseline number.
02Assess	Days 1–3	Is the organization actually able to hold this change?	Check capacity, competing priorities and who is affected before committing the team.	Readiness read and a short list of the people whose work changes.
03Charter	Day 3 · 60 minutes	What are we changing, inside what boundary, measured how?	The charter is completed in the online builder and approved by the sponsor in the room.	Approved charter: scope, outcomes, owner, measures, decision rights.
04Design	Week 1–2	What does the work look like once the change holds?	Map current to future state at the work itself, not in a conference room.	Future-state standard work and the list of people to prepare.
05Activate	Week 2–4	Are people able to work the new way today?	Run the ARC cycle, observe at Gemba, clear barriers within the week they appear.	Decisions with owners and dates; observed use of the new way.
06Stabilize	Week 4–6	Is the measure moving, and are workarounds appearing?	Review adoption and performance together. Refine the design rather than pushing harder.	Measure trend against baseline; workarounds resolved or designed in.
07Institutionalize	Week 6 · closeout	Who owns this after the team stands down?	Transfer standard work, measure and ownership into the operating rhythm — then close, scale or stop.	Named process owner, standard work in place, closeout decision recorded.

One method, four scales

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

Serves04 Determine Intervention Breadth & Depth

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 material · Phase One release · retained and flagged

Two documents teach the earlier value stream. Both are on Compass standards.

The deck carries the executive argument — Select, Charter, Prepare, Execute, Sustain. The guide teaches it module by module. Both pre-date the nine-step process architecture and are retained here as published material; re-issuing them on the nine steps is a separate decision.

Facilitator & practitioner deck · 15 pages

Change & Transform — Phase One Release

The executive premise, the selection gate, the seven-stage value stream, four scales of work, the eight working instruments, the five executive gates, and governance ownership.

Download the Phase One deck

Facilitator & practitioner guide · 31 pages

Facilitator & Practitioner Guide — Phase One

Ten teaching modules, a slide-by-slide teaching guide, three delivery formats, a multi-site ERP application case, glossary and facilitator checklist.

Download the facilitator guide ↓

Both documents were rebranded to Compass standards before posting — navy, gold and slate only, with the Compass lockup, the FOUNDATION · SIMPLIFY · LEAD · GROW · ARC rule and consistent typographic hierarchy. ADKAR® is a registered trademark of Prosci, Inc., referenced as an attributed adoption model.

Evidence

Two structures run at once. Only one of them is usually drawn.

Compass architects against both structures at once: the visible hierarchy and the invisible network through which the work actually travels. That is why an adoption gap reads here as a design signal rather than a willingness problem. Published figures are cited beneath each reading as support.

Compass architects both. The formal structure is drawn — decision rights, accountabilities, cadence — and the informal network is made deliberate rather than left to proximity, because an undesigned network reverts to whoever absorbs ambiguity.
Supporting evidence
“Organizations operate with 2 structures simultaneously. The first is visible: the formal hierarchy of the organization. The second is invisible: the informal network of relationships through which information travels, influence operates, and work happens.”
The report describes a visible hierarchy and an invisible relational network operating at the same time.
Center for Creative Leadership, Challenge Report CS4647
This is the same law we state about enterprises: architecture determines performance. Capable people executing in parallel is not a talent failure. It is a design that never specified how the work moves between them.
Supporting evidence
“When connection is left to chance, capable individuals execute in parallel.”
The report's central assumption check: connection no longer happens naturally in distributed, layered, disrupted organizations.
Center for Creative Leadership, Challenge Report CS4647
Compass reads derailment as an architecture question before a person question: whether the role had a decision it owned, a cadence that closed commitments, and a boundary it was designed to cross.
Supporting evidence
The report's research on executive derailment shows that leaders fail more often because of relational breakdowns — difficulty building trust, inability to span boundaries, failure to create the conditions for others to follow — than technical incompetence.
Center for Creative Leadership, Challenge Report CS4647
In our engagements the misattribution runs the same way — a strategy is rewritten when the constraint was an unwritten decision right. That is why Compass establishes an accurate current state before proposing any redesign.
Supporting evidence
“Yet, the real cause is often relational.”
The report notes that organizational gaps are frequently misattributed to poor strategy or a lack of talent.
Center for Creative Leadership, Challenge Report CS4647

How to read this band: every reading above is Compass's own interpretation, written from Compass engagements and the Compass Enterprise Operating Architecture. The published figures beneath each reading are supporting evidence only — they are cited to test the reading, not to make the argument, and none of them was produced for or with Compass.

Full citation: Center for Creative Leadership, “The Space Between People: Building the Human Connections That Make Leadership Work at Scale,” Challenge Report CS4647. © Center for Creative Leadership. All rights reserved. ccl.org

Resistance, read correctly

Every adoption gap points at a system condition.

Serves08 Execute & Enable Adoption

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

Optional · The leader in the change · retained and flagged

The pattern you bring to a change is part of the design.

Serves05 Assess Readiness

Everything above governs the work. This is the one read that governs the person doing it. Take the two Positive Intelligence® instruments, enter your two results, and Compass will write a short summary — your top three Saboteurs, your PQ® quotient, and how that combination may play into the way you manage change. Individual awareness is never an intervention on its own; it is read beside the individual readiness view, with a system change required alongside it.

1 · The Saboteur Assessment

Which internal patterns run the show when the pressure rises. About 7–10 minutes. Note your top three. You register once with Compass, then it opens.

2 · The PQ® score

How quickly you return to a clear response once a saboteur has taken control. About 7–10 minutes. Note the number. It opens after the first is finished.

Enter your two results

Two numbers in. One summary out.

Nothing here is stored. The summary is written for this screen, and the PDF is built on your own device.

First name (optional)

PQ® score (1–100)

Your top three Saboteurs, strongest first

The change you are preparing to lead (optional)

If you want to go further

A summary tells you where you stand. A cohort is where the practice holds.

The Mental Fitness Lab is an eight-week virtual cohort — ninety minutes a week, about ten minutes of daily practice, $1,500 for the eight weeks. It is especially worth doing before you embark on a significant change: the pattern this summary names is the one that will be under load for the whole of it.

About the PQ cohort Discuss joining a cohort

Positive Intelligence®, the PQ® Score, and the Saboteur model are trademarks and the work of Shirzad Chamine and Positive Intelligence, LLC. Compass Performance, Inc. does not own them and claims no rights in them; Compass is an independent user of these licensed instruments. The Compass service is Mental Fitness™, and the reading, interpretation and commentary here are Compass's own.

The register

Where every earlier block went.

Nothing was deleted. Every earlier block is mapped to the step it serves or retained and flagged here until it has a decision.

Retained and flagged Change & Transformation content blocks
Block	Serves	Now at	Status
Gleicher's Formula for Change (D × V × F₁ > R)From /change-and-transform — The philosophy	03 Define the Change · 05 Assess Readiness	Method depth — Gleicher	Mapped
The flywheel and how adoption spreads (adoption curve)From /change-and-transform — Momentum	08 Execute & Enable Adoption · 09 Sustain / ARC	Method depth — momentum	Mapped
The four layers of the integrated modelFrom /change-and-transform — The architecture	03 Define the Change · 08 Execute & Enable Adoption · 09 Sustain / ARC	Method depth — four layers	Mapped
The seven-stage value stream and the operating table of seven gatesFrom /change-and-transform — The value stream · The operating table	Every step	The seven gates in full	Mapped
Printable stage briefs under the earlier READY → FOCUS → MOBILIZE → PERFORM → SUSTAIN vocabularyFrom /change-and-transform — the chevron band	—	Method depth — earlier vocabulary	Retained · flagged The briefs still teach the five-band line. Retained and reachable through the band → step mapping until re-issued on the nine steps.
The change team: eight roles, recognition architecture, cadence and rulesFrom /change-and-transform — Building the team	06 Configure the Intervention · 07 Mobilize	Roles and recognition architecture	Mapped
How a small improvement project is led (chartered, not launched)From /change-and-transform — How small work is led	04 Determine Intervention Breadth & Depth · 03 Define the Change	Method depth — small work	Mapped
One method, four scales (ARC™ Sprint, Project, Initiative, Transformation)From /change-and-transform — Scale	04 Determine Intervention Breadth & Depth	Method depth — scales	Mapped
Phase One deck and facilitator guideFrom /change-and-transform — The material	—	Method depth — published material	Retained · flagged Both documents teach Select · Charter · Prepare · Execute · Sustain and the seven-stage stream. Retained as published material; re-issue on the nine steps is a separate decision.
CCL research band — the visible hierarchy and the invisible networkFrom /change-and-transform — Evidence	07 Mobilize	Method depth — research	Mapped
Resistance as a system signal; what changes (before → after)From /change-and-transform — Resistance, read correctly	08 Execute & Enable Adoption	Method depth — resistance	Mapped
The leader in the change — optional Positive Intelligence® readFrom /change-and-transform — Optional · The leader in the change	05 Assess Readiness	Method depth — the leader	Retained · flagged Individual awareness is never an intervention on its own. Kept as an optional read beside the individual readiness view, with a system change required alongside it.
Transformation Center — the eight operable desksFrom /transformation-center	Every step	Transformation Center	Mapped
Transformation Journey — the six-stage assessment record (Charter → ARC™ After-Action Review)From /transformation-journey	—	Transformation Journey	Retained · flagged This is the assessment record of one transformation, not the process sequence. Retained unchanged; it is read alongside the nine steps, not instead of them.
The five-gate plain-language line (READY → FOCUS → MOBILIZE → PERFORM → SUSTAIN) on the architecture pageFrom /operating-system/architecture — Transformation management	—	Architecture — transformation management	Retained · flagged Retained as the plain-language line for how the WORK moves across the five components; it now carries the step mapping and defers to the nine-step process architecture for Change & Transformation.