Compass Enterprise Architecture™ · Depth
The architecture, one level deeper.
The Operating System page answers what the architecture is and how the disciplines work together. This page carries the method detail beneath it — the common language, the wall, the enablers, the engagement structure, and the record that closes a stage.
This page answers one question: What sits beneath the architecture?
The common language
Market Rate of Demand is an alignment tool, not a factory metric.
When every function answers its question against the same demand signal, alignment stops being a workshop outcome and becomes an operating habit.
Sales
“What is the market buying?”
Operations
“How fast must we produce?”
Supply chain
“What materials support that demand?”
People
“What capabilities do we need?”
Finance
“Are we investing in the right value streams?”
Leadership
“Are we aligned around today's demand?”
Same number. Same conversation. Every week.
The dashboard
Visual management is the operating system made visible.
One wall instead of twenty reports — readable by the chief executive and the operator in the same ten seconds.
The operating wall
Customer
- Market rate of demand
- On-time delivery
- Backlog
Operations
- Hour-by-hour production
- Today's bottleneck
- Planned vs. actual
People
- Staffing
- Safety
- Skills
Improvement
- Top problems
- Countermeasures
- ARC projects
Front to Back 80/20
Enterprise systems are enablers of the management system — not the management system
Compass reads the enterprise front to back — from demand through decisions to delivery — and applies 80/20 to find the small number of markets, customers, products, and decisions that carry most of the result. That reading defines the management system. ERP, CRM, and the rest of the technology stack then enable it: they carry the architecture, they do not create it.
- 01Front
Demand and the customer
Market, customer, and product concentration — where revenue, margin, and attention actually come from.
- 02Middle
Decisions and hand-offs
Who decides what, on what information, at what cadence — the joints where most performance is lost.
- 03Back
Delivery and the ledger
Operations, supply, service, and financial truth — where the promise is either kept or quietly subsidized.
| System | Enabling role | Common misuse |
|---|---|---|
| ERP | One version of operational and financial truth | Bought to impose a process no one has designed |
| CRM | Visibility into demand, pipeline, and customer concentration | Bought to create a sales discipline that does not yet exist |
| BI / analytics | Measures the few numbers that govern the business | Bought to produce reports nobody uses to decide |
| HRIS / talent | Makes roles, capability, and accountability visible | Bought to replace clear decision rights |
Install technology on top of an unarchitected system and you automate the confusion.
How the work unfolds
Three steps. Then it belongs to you.
Present reality
Name what the organization is actually navigating. No service is assumed at this point.
A discovery conversation
A focused 30–45 minutes. Not a sales presentation. Both sides evaluate the fit for the work in front of you.
Architect and install
The right path is designed, built and then run by your leaders — so the capability compounds inside your organization.
The record
Close each stage on paper before you move to the next.
A stage is complete when the evidence can be shown, dated and audited — not when the meeting ends.
Worked example
Stage Completion Record
One sign-off sheet for the whole operating system. A stage closes when the evidence can be shown, dated and audited — not when the meeting ends. The reading below is an anonymized example of a record part-way through an engagement; the sheet itself is cumulative, so the record printed at the end of SIMPLIFY still carries the FOUNDATION sign-off with it.
FOUNDATION™
Decision rights written and published; two standing meetings retired.
14 March · signed Chair, executive team
SIMPLIFY™
Portfolio banded; two product lines de-invested and the capacity reallocated.
22 May · signed Chief executive
LEAD™
Goal cascade through the value streams; two of five stream owners named.
In progress
GROW™ · ARC™
Not started. A stage cannot be signed off ahead of the one beneath it.
—
This page shows the example only. The working instrument — exit criteria, the items your enterprise completed, the date, the auditor and the cumulative printed record — is on the tools desk: open the working instrument.
On the record
Leaders have been saying this for seventy years.
A defined system, standards you can improve against, and a measure of how well the organization actually runs it. The words below are quoted from the published record; the composites come from Compass engagements and are labeled as such.
Quoted from the published record and attributed to its source. Compass does not paraphrase or edit these words. An illustrative composite drawn from Compass engagements. Not a client testimonial and not attributable to one organization. Select any quotation to read its full reference and how it ties to Compass.
Any transformation
The trigger changes. The architecture does not. Every transformation passes the same five gates — only the content of each gate is different.
Choose what you are actually navigating. The five gates stay the same — only what has to be true at each one changes.
ERP or system implementation · what is really changing
A system implementation is a decision-rights and process change wearing software. The technology is the enabler; the management system is what actually changes.
- Gate 01
READY
Data, process and decision-rights readiness assessed before configuration begins; sponsor and capacity confirmed against everything already in flight.
- Gate 02
FOCUS
Processes simplified and standardized before they are automated, with a stop list for reports, hand-offs and workarounds that will not be carried forward.
- Gate 03
MOBILIZE
Role-based capability built before cutover; super-users named; the operating rhythm runs on the new data from week one.
- Gate 04
PERFORM
Benefits measured on the original baseline — cycle time, inventory, close, margin visibility — not on modules deployed.
- Gate 05
SUSTAIN
ARC cycles retire the shadow spreadsheets and hold the standard configuration against local drift.
How this type usually failsAutomating the existing mess, then blaming the software.
Same architecture, different language
One transformation. One operating system. Different language for different levels of the organization.
CEO and board · their version
Are we ready, focused, aligned, capable, and realizing value?
- Why the transformation is necessary
- Strategic and financial value
- Readiness and major risks
- Leadership ownership
- Investment and capacity
- Benefits realization
- Governance and decision gates
Level of detailValue, risk and governance. One page, five stages, decision gates.
Adoption, in plain language
- 01Understand it
- 02Choose to support it
- 03Learn it
- 04Do it
- 05Keep doing it
For executive audiencesMethods that stay behind the scenes
These are instruments Compass and leadership use to design and govern the change. The workforce never needs the vocabulary — only the plain steps beside this panel.
Gleicher's Change Formula · ADKAR® · Kotter · PMBOK · Stakeholder-impact architecture · Benefits-realization methodology
READY · Case for changeFOUNDATION
- Case for change
- Present-reality pressure
- Vision clarity
- Leadership alignment and sponsorship
- Organizational capacity and change load
- Where resistance already sits
Supporting methodsGleicher's Change Formula · Sponsor alignment
FOCUS · ImpactSIMPLIFY
- What must change — and what should stop
- Which stakeholders are most affected
- Which processes and structures create the most friction
- What must be sequenced
- Where capacity has to be released first
Supporting methodsStakeholder mapping · Change-impact assessment · Front-to-Back 80/20
MOBILIZE · AdoptionLEAD
- Strategy linked to purpose
- Engagement and psychological safety
- Alignment and accountability activated
- Capability developed
- Adoption managed
- Reinforcement begun
Supporting methodsADKAR® · Communication and engagement plans · Standard work
PERFORM · PerformanceGROW
- Operating the new model
- Developing successors
- Building repeatable capability
- Transferring knowledge
- Scaling leadership
- Capturing value
Supporting methodsBenefits realization · Capability development · Succession planning
SUSTAIN · ReinforcementARC
- Measure whether adoption is holding
- Refine what is not working
- Commit to the improved standard
- Reinforce ownership
- Capture lessons
- Convert project change into operating discipline
Supporting methodsReinforcement mechanisms · Benefits realization · ARC countermeasures
The architecture stays constant. Only the language, examples and level of detail change — never a separate framework for the board, the manager and the floor.
Every system has a lifecycle. The second curve is the start of a new lifecycle — and it should begin way before the first one ends.
The second curve is not an extension of the first. It is a new system with its own architecture, begun from strength while the current one is still creating value.
Three-minute stage read
Which stage is your business in right now?
Fifteen statements, about three minutes, and the eight-stage read comes back with what the stage is costing.
Seven things most firms treat separately. Compass integrates them into one Enterprise Architecture.
- Strategy
- Leadership
- Operating systems
- Execution
- Culture
- Governance
- Continuous improvement
Architecture determines performance.
Owners don’t buy alignment. They buy what alignment makes possible.
Organizations are designed systems, not collections of people.
Steve Kopecky is the architect behind this methodology — a distinct body of work, not a collection of borrowed consulting tools.
- Why strategy fails
- Strategy is not defeated by competitors. It is defeated by the architecture asked to carry it.
- Why growth creates complexity
- Every unmanaged exception becomes permanent structure.
- Why founders become bottlenecks
- When judgment lives in one person, the system cannot scale past them.
- Why culture follows architecture
- Behavior follows what the system rewards, measures and makes easy.
The Compass language
- Architect
- Operating System
- Front-to-Back
- Outside-In
- 80/20
- FIRST Values
- ARC
- Freedom Within a Framework
Go one layer deeper
Back to the Compass Enterprise Architecture™
The architecture this depth sits beneath.
- Enterprise readiness
Read the architecture through six Readiness Lenses.
- Offerings
How the work is scoped and installed.
The next step
Ready to see the architecture differently?
A focused introductory conversation. We will clarify what is happening, why it matters, and whether a deeper dialogue makes sense.
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 What comes next.