One Operating System. One Core Architecture.

01

The core architecture establishes and renews the operating system

FOUNDATION™, SIMPLIFY™, LEAD™ and GROW™ form the core architecture. ARC™ renews them continuously. The numbering gives the reader an index; it does not place renewal at the end of a one-time program. The next three areas carry the architecture into resource choices, adoption and governed delivery.

02

06 — Front-to-Back 80/20™

Front-to-Back 80/20™ connects strategic choices to daily activity. Leaders examine where customer value and business contribution are created, then align the product or service offering, processes and resources with those priorities. The analysis must travel through the enterprise: a commercial choice changes what Operations produces, what Supply Chain supports and which capabilities people need.

Treat 80/20 as a discipline for investigating concentration, not a guaranteed numerical split. A useful review makes a resource decision visible: what receives capacity, what is simplified, what is stopped and what exceptions remain justified. The business should be able to trace a priority from the customer promise to the work scheduled this week.

03

07 — Change & Transformation™

Change & Transformation™ connects the approved future design to the people expected to operate it. For every affected role, define what changes in tasks, decisions, systems, relationships and required capability. Give the person a clear standard, a realistic learning path and the conditions needed to perform.

Communication and training attendance are inputs. Adoption requires evidence from the work itself: the new process is used, the appropriate person makes the decision, exceptions are handled correctly and performance meets the accepted standard. A supervisor needs a way to see a capability gap and act on it before the gap becomes a customer failure. Attraction starts with a credible picture of the future work; retention tests whether the organization provides the conditions, learning path and support needed to perform it.

04

08 — Program & Project Management™

Program & Project Management™ governs the temporary work required to establish the new operating state. A project owns defined deliverables; a program coordinates related changes and dependencies; portfolio decisions determine which work receives scarce resources. Acceptance criteria connect each level to the operating outcome it must produce.

Use explicit delivery gates appropriate to the program method. Each gate needs an accountable owner, evidence, open risks and an explicit decision. A completed installation is one deliverable. Closure also requires an accepted handoff, adoption evidence and an owner who can sustain the result.

05

Keep the three disciplines connected

Front-to-Back 80/20 establishes the resource choices. Change & Transformation establishes how the affected organization will adopt the design. Program & Project Management coordinates delivery and acceptance. All three depend on the same approved future state and the same record of decisions. When a material assumption changes, its effects must be reviewed across the whole system.

All three depend on the same approved future state and the same record of decisions.

06

A manufacturing example

Consider a hypothetical manufacturer planning for demand as high as five times its current level. Multiplying the existing staffing pattern may appear to be the fastest planning method. But automation, a different product mix or a redesigned material flow could change the work before the additional employees arrive.

Begin with required output, mix, quality expectations and the Required-Capacity Date. Compare feasible operating scenarios, including the work that could be removed or automated. A material handler who once transported every load might instead monitor automated replenishment and resolve exceptions. That change affects decision rights, training, maintenance support, safety controls and the job design.

Recruiting then receives an approved requirement for future productive capability. Operations owns the output requirement; the relevant technical owner establishes the qualification standard; Talent Acquisition develops the appropriate supply channels. Changes to the design trigger a review of the staffing requirement rather than allowing an obsolete requisition to continue unnoticed.

07

Start with one shared operating pilot

Select one value stream, role, location and shift. Establish the current baseline and the desired outcome. Name the people authorized to approve the design, release capacity and accept qualification. Review evidence on a regular cadence and retain a version history when assumptions change. Extend the approach only after the pilot shows that the new work can be performed and sustained.

An operating system becomes useful when leaders can follow a requirement through the design, the people who own it, the work that changes it and the evidence that proves the outcome. That is the practical purpose of one core architecture: making the enterprise coherent enough for its people to perform.