The Operations Architecture track of the OAC Fellowship addresses this gap directly. It begins where most lean programmes end — with leaders who already understand production tools and have implemented them with varying degrees of success — and asks the architectural question: how does the coordination system between supply chain and manufacturing actually work, and is it designed or merely inherited? This is why the track deliberately combines supply chain and manufacturing rather than treating them as separate functions. In reality, the architecture that determines operational performance crosses both. A production scheduling decision is simultaneously a supply chain commitment. A supplier development initiative reshapes what is possible on the manufacturing floor. Separating them in a development programme would reproduce the very functional boundary that creates coordination failure in practice.
The method follows the OAC eight-phase structure but with domain-specific content. In the compression and observation phases, participants map their own operations architecture — not the process flow, which they already understand, but the information flow, decision flow, and coordination routines that sit above the process. Where does planning information originate and how does it degrade as it crosses functional boundaries?
Most executives encounter lean through its production tools. Value stream maps, standard work, kanban, andon, hourly boards, FMDS — these are the visible mechanisms of operational excellence, and they work. But they work at the level of the process. The question that most organisations never ask is why these tools, applied diligently for years, produce local improvements that fail to compound into system-level performance. The answer is architectural. Production tools operate within a coordination structure that was never itself designed. The interfaces between manufacturing and supply chain, between planning and execution, between quality systems and production flow — these were accumulated through decades of organisational growth, reorganisation, and expedient problem-solving. The tools are lean. The architecture they operate within is not.
Where do supply chain signals reach manufacturing too late to act on? Where does daily management on the floor generate knowledge that never reaches the people making supplier decisions? These are not process problems. They are architectural problems, and they require architectural tools to make visible.
The Field Reconnaissance takes on particular significance for this track. Participants observe not individual production tools but the management architecture that connects them — how Floor Management Development Systems link to KPI Management, how daily management connects vertically to hoshin kanri, how supplier relationships are structured as architectural extensions of the production system rather than as transactional procurement. What becomes visible in visits to places like Japan supply chains is not better tools but better design of the system within which tools operate.
The synthesis and action phases then ask participants to redesign their own operations architecture using what they have observed. The Four-Level framework — MBO, MBF, FMDS, PEFF — provides the structural logic. Compositional Hoshin provides the strategy formation method. The Architectural Linkage Diagram reveals where the organisation’s operational architecture aligns or misaligns with its industry’s trajectory. Participants design KPI architectures that distinguish results from process signals, that trace from strategic intent to controllable daily action, and that work across the supply chain and manufacturing boundary rather than optimising each side independently.
This is lean at the level it was originally conceived — not as a collection of production tools but as the design of an operating system. The executives who built Toyota’s production and supply chain architecture were not doing shopfloor improvement. They were designing how coordination, learning, and capability accumulation would work across an entire value system. The Operations Architecture track develops executives who can do the same for their own organisations.
Architectural Disciplines
Fields of Practice
theme
1
Cross-Boundary Coordination Architecture
— designing the information and decision architecture that connects supply chain and manufacturing as one system rather than two functions.
theme
2
KPI Architecture
— building vertical integration of measurement from strategic result through cross-functional process through daily controllable signal using the PEFF framework.
theme
3
Four-Level Management System Design
— understanding and installing the MBO, MBF, FMDS, and PEFF layers as an integrated operating system rather than separate management initiatives.
theme
4
Visual Management as Information Architecture
— designing FMDS boards, daily management routines, and escalation systems as signal detection architecture rather than display mechanisms.
theme
5
Supplier Integration Architecture
— extending the management architecture beyond organisational boundaries so that supplier coordination operates through designed information flow rather than transactional procurement.
theme
6
Flow and Constraint Diagnosis
— applying Total Lean Supply Chain thinking to identify where information flow, not material flow, is the binding constraint on system performance.