ARC™ — Discipline 05 | Renew the Enterprise
ARC™ converts facts into focused decisions, owned execution, and repeatable learning across the Compass Operating System. Analyze reality. Refine the better way. Commit to execution — so improvements endure, leaders learn, and the organization continuously renews.
Start where it hurts
Leadership teams rarely describe a process failure in process language. They describe a symptom. Each one below maps to a specific stage of the cycle — and to the discipline that resolves it.
“Everyone agrees it's broken — nobody agrees on what 'it' is.”
No problem statement, no scope, no baseline. The work starts by naming the problem in terms the whole team can measure.
“The process on paper is not the process people run.”
Hand-offs, queues, and workarounds are invisible until the actual work is mapped on the wall and validated by the people doing it.
“The same failure keeps coming back after we fix it.”
Symptoms are being treated, not causes. Pareto, 5 Whys, and Fishbone separate the recurring driver from the noise.
“We're busy, but the work doesn't feel like it's creating value.”
Value-adding, required non-value-adding, and pure waste have never been separated — so effort scales faster than results.
“We keep doing it this way because we've always done it this way.”
Legacy policy and approval habits go unchallenged. Remove — Combine — Reorder — Simplify puts real alternatives on the table.
“Everything is a priority, so nothing finishes.”
Without impact-versus-effort discipline, act-now work competes with build-the-plan work and both stall.
“Decisions get made in the room and evaporate outside it.”
No roadmap, no named owner, no milestone. RACI and decision rights turn intent into an assignment.
“We rolled it out enterprise-wide and it broke on contact.”
Change went live without a pilot. Test with representative users, learn, and refine before broad launch.
“The improvement worked for a quarter, then quietly eroded.”
Gains without standard work, controls, and a leadership cadence revert to the old system every time.
Most engagements begin with two or three of these at once. ARC™ runs the full cycle regardless of where the symptom shows up — because a symptom in Commit is usually a cause that was never found in Analyze.
ARC™ is the fifth discipline and renewal engine that runs through the entire Compass Operating System — keeping FOUNDATION™, SIMPLIFY™, LEAD™, and GROW™ responsive, measurable, and alive.
Analyze
Understand reality before acting
Frame the work, map what actually happens, and find the cause before proposing a single change.
Methods Charter • Brown Paper • SIPOC • Pareto • 5 Whys • Fishbone
Core QuestionWhat is actually happening — and why?
Refine
Design and prioritize the better way
Classify the work, design future-state options, and prioritize by impact, effort, and risk.
Methods VA/NVA classification • Remove-Combine-Reorder-Simplify • Impact/effort • FMEA
Core QuestionWhat is the simplest change that creates the greatest improvement?
Commit
Execute, sustain, and learn
Plan the change, pilot before broad launch, and lock in results with standard work and cadence.
Methods Roadmap • RACI • Pilot • Standard work • Control plans • Lessons learned
Core QuestionHow do we make the new way the way — and keep learning?
Clarity
Decisions made on what is actually happening
Cycle times, handoffs, queues, rework, and approvals become visible facts a leadership team can act on — not competing opinions.
Ownership
End-to-end accountability, not shared responsibility
Every redesigned process has a named owner, explicit decision rights, and a cadence that surfaces drift before it becomes damage.
Sustained improvement
Gains that hold after the project ends
Standard work, controls, and a leadership review rhythm convert one-time fixes into how the organization operates.
Analyze, Refine, and Commit form the ARC cycle. Sustained results generate the learning that renews the system and begins the next cycle.
Analyze
A cross-functional team mapped the actual order-to-cash process on the wall — exposing duplicated approvals, unclear decision rights, and orders sitting in queue between sales, operations, and finance.
Refine
Redundant approvals were removed, handoffs were redesigned around a single end-to-end owner, and the remaining changes were sorted into act-now versus build-the-plan.
Commit
The new flow was piloted with a representative order set, standard work and escalation rules were published, and a monthly control cadence kept the gains from eroding.
Composite example drawn from Compass engagements; details anonymized.
Real work, on the wall — the artifact of the Analyze phase.
The Brown Paper Exercise gathers the frontline and cross-functional team around a shared wall, exposes hand-offs, queues, rework, and approvals, and turns opinion into a fact-based picture everyone can validate before a single change is proposed.
Golden rule — map what actually happens, not what should happen.
Download the reference
For practitioners leading the work. Expand each phase to see the methods Compass uses inside the cycle — always the simplest tool that clarifies the problem and improves the decision.
Frame the Work
Map and Validate
Find the Cause
Classify the Work
Generate Options
Evaluate and Prioritize
Plan the Change
Pilot and Implement
Measure and Sustain
FOUNDATION™
Keeps the honest picture current — ARC re-tests what leadership believes to be true against what the work actually shows.
SIMPLIFY™
Turns simplification from an event into a habit — each cycle removes friction the last one exposed.
LEAD™
Gives leaders a disciplined way to decide, assign ownership, and hold a cadence rather than escalate.
GROW™
Protects scale — growth adds volume, and ARC keeps the system able to absorb it without dilution.
Brown paper exposes reality. Reality drives better decisions. Better decisions drive results.
The ARC™ Cycle
Sustained results generate the learning that renews the system and begins the next cycle across FOUNDATION™, SIMPLIFY™, LEAD™, and GROW™.
The Compass Operating System
Freedom Within a Framework™ | Clarity. Alignment. Execution. Results.
The next step
If the same failure keeps returning — missed dates, rework, unclear ownership, decisions that stall — that is an ARC™ conversation.
