S t r a t e g i c
R e g i m e s C y b e r n e t i c s
T e c h n i c a l
**F R A M E W O R K · C O M P A N I O N** # **PDCA+ Companion v 1.0** _The connector and pathfinder for PDCA+ v 2.0_ _This is PDCA+: The work itself still needs doing. What PDCA+ gives is visibility as a structural feature of what is actually being done. Success or failure is determined by the level of honesty and intent of the implementing organisation — the kind of intent that any honest posture for assurance carries with or without PDCA+._ **A U T H O R Joacim Brandell** _The connector and pathfinder_ PDCA+ Companion v 1.0 ## **How to read this compass** This document is the companion centerpiece of the PDCA+ supporting material. The framework itself — the structural model — lives in the PDCA+ v2.0 whitepaper. The supporting material that makes the framework legible from different starting points is organised into four bearings: cybernetics, regime, technical, and strategic. Together the four bearings form a compass through which the framework's territory can be entered from any of four directions. This companion's work is to make the compass itself visible — to bring the four bearings into one place where their relationship can be seen, and to provide the orientation that lets a reader find their own starting point. The companion is short by design. It is not a substitute for the bearings themselves, and it does not summarise their substance. It points. A reader who finishes the companion should know which of the four bearings to engage with first, which others to engage with subsequently, and how the four together form a single compass that addresses the same framework from four directions that complement each other rather than competing. Several reading patterns are appropriate. A practitioner who wants to understand the intellectual tradition the framework belongs to can begin with the cybernetics leg and follow it through to the others. An executive whose first concern is what the framework changes for the organisation can begin with the strategic leg and work outward from there. A technical architect who needs to know what operationalisation looks like can begin with the technical leg and find the strategic implications afterward. A practitioner working in a specific regulatory regime can begin with the regime leg and locate the framework within the regimes they already know. None of these paths is preferred; each enters the compass at a different bearing and reaches the same framework through a different first encounter. The whitepaper is the framework. The bearings are how the framework is made legible. This companion is the center of the compass. ## **The four bearings** Each of the four bearings addresses the framework from a particular bearing. The bearings are not arbitrary; they were chosen because together they offer the four directions from which the framework most usefully becomes accessible to its readers. North orients toward strategic decision. East toward intellectual foundation. South toward operational grounding. West toward the regulatory territory the framework engages with. The compass is not a hierarchy; the bearings are equally valid entries into the same territory. Each leg is complete on its own terms. A reader who engages with one leg substantively will understand the framework from that bearing without needing to engage with the others. A reader who engages with all four will see the framework from four directions simultaneously, which produces a deeper understanding than any single bearing can offer. Joacim Brandell 2 / 6 _The connector and pathfinder_ PDCA+ Companion v 1.0 **B E A R I N G · N o r t h Strategic and business** **Focus:** What changes when the framework is in place — operationally, relationally, financially, in governance, in competitive position, in leadership posture, and in the structural trust the framework produces directly. The leg builds the strategic case for engagement with the structural absence the framework addresses. **Written for:** Senior management, CEOs, board members, audit and risk committees, strategy leadership, and those who prepare board materials. **Pieces:** _The structural absence · Inside the organisation · External relationships · The economics of compliance · Risk vocabulary for the board · Competitive and market positioning · The leadership posture · The trust architecture_ **B E A R I N G · E a s t** **Cybernetics** **Focus:** Where the framework sits in the intellectual tradition of cybernetics — Stafford Beer's Viable System Model, the law of requisite variety, second-order observation, the language of variety engineering that the framework rests on without renaming. The leg gives the framework its intellectual ancestry and shows what it contributes to a longer tradition that has been seeing systems for sixty years. **Written for:** Cyberneticists, systems thinkers, organisational theorists, practitioners interested in the intellectual provenance of the framework, and anyone who wants to know what the framework owes to its tradition. **Pieces:** _Cybernetics companion · The Viable System Model account · Variety engineering vocabulary · Secondorder observation_ **B E A R I N G · S o u t h** **Technical operationalisation** **Focus:** What it takes to build a substrate that operates the framework — infrastructure foundations, the substrate's data model and governance, the production face (observability and integration), and code-ascompliance as the methodology that runs on top. The leg specifies what an organisation has to commit structurally to make the framework operate in real infrastructure. **Written for:** Technical architects, GRC technology leads, enterprise architects, technically-oriented CISOs, and new-era developers building substrate-based systems. **Pieces:** _Infrastructure foundations · The substrate, in detail · Observing and integrating the substrate · Code-ascompliance_ **B E A R I N G · W e s t** **Regime application** **Focus:** How the framework engages with the regulatory regimes organisations actually face — multi-regime supply-chain assurance, the control-objective chain that addresses regimes coherently, the three modes of compliance (check, continuous, strategic), and the structural distinction between tensions and risks. The leg shows the framework at work in the regulatory territory the world has produced. **Written for:** Risk and compliance professionals, GRC managers, regulatory affairs leaders, supply-chain compliance practitioners, and practitioners working in specific regulated industries. **Pieces:** _Multi-regime supply-chain assurance · The control-objective chain · The three modes of compliance · Tensions and risks_ Joacim Brandell 3 / 6 _The connector and pathfinder_ PDCA+ Companion v 1.0 ## **What the framework is, and what it is not** Several distinctions matter before the closing reflection. The framework is a structural model. It specifies what an organisation needs to hold in order to do management-system integration well — the substrate as the place where the integration content lives, the chain as the architecture that connects regime intent to operational reality, the conjunction as the apparatus that observes the substrate continuously, the second-order observation that lets the framework see its own observing. These are structural commitments, expressed at a level of abstraction that admits many implementations. The framework is not a specific implementation. An organisation that adopts the framework can build many different operating systems — different infrastructure choices, different tool sets, different data models, different integration patterns, different governance approaches. Each of these is an implementation of the framework's structural commitments; none of them is the framework itself. Some implementations may take particular shapes that become familiar across the industry — a substrate-centred operating system is one possibility, with its own architecture that may emerge as a recognisable pattern. But the operating system is the implementation; the framework is the model the implementation realises. This distinction matters because it preserves the framework's openness. Organisations adopting PDCA+ will make implementation choices appropriate to their context, their existing infrastructure, their organisational culture, their strategic priorities. The framework's structural commitments are the same across all these contexts; the implementations will differ substantially. A framework that prescribed a single implementation would be less useful, not more useful, because it would constrain choices that should remain with the implementing organisation. The framework is also not the work itself. Adopting the framework does not produce compliant operations, well-governed organisations, or trust-based external relationships. Those have to be produced by substantive operation, by the kinds of leadership posture the strategic leg named, by the substrate stewardship the technical leg described, by the regime engagement the regime leg developed. The framework supports the work; the work is the implementing organisation's. This is what the leading text of this companion names directly: the work itself still needs doing. ## **What this companion is and is not** Three honest framings to keep the companion in its appropriate role. First, the companion is not a substitute for the bearings themselves. The four bearings developed across twenty pieces of supporting material have substance and depth that the companion cannot reproduce. A reader who reads only the companion has located the compass but has not entered any of its bearings. The companion's purpose is to direct the reader to where the substance lives, not to provide the substance itself. Joacim Brandell 4 / 6 _The connector and pathfinder_ PDCA+ Companion v 1.0 Second, the companion is not a comprehensive guide to the framework. The framework lives in the whitepaper, with the four bearings of supporting material extending what the whitepaper establishes. The companion connects the bearings but does not replace the whitepaper. A reader interested in the framework itself should read the whitepaper; readers interested in how the framework becomes legible from particular directions should read the bearing the companion points to. Third, the companion is not the framework's marketing material. PDCA+ does not require advertising. The companion is for readers who have already encountered the framework and want to know how to engage with the supporting material that surrounds it. The connector function and the pathfinder function are the companion's contributions; neither requires promotional rhetoric. ## **An initial reflection** PDCA+ is the correction and completion of a tradition that has served the world well for decades. The Plan-Do-Check-Act cycle that ISO carried into management-system standards through generations of practitioners is the foundation on which PDCA+ rests. The practitioners who built that foundation — through ISO 9001, ISO 14001, ISO 27001, and the many other management-system standards that followed — produced something the world needed and that the world has used. PDCA+ does not erase that tradition. It points to a fault, corrects it, and adds a missing piece. The fault is the absence of structural ground for the integration the disciplines need to do together. The correction is the conjunction layer — the substrate where the integration content lives, observable to those who need to observe it, governable by those who hold authority over it, traceable across the years of its operation. The missing piece is second-order observation — the framework's capacity to see its own apparatus, to detect drift in its categories, to notice when its own classifications are no longer fitting what they classify. The conjunction and the second-order observation together are what PDCA+ contributes to the tradition that produced PDCA. What the implementing organisation brings to the framework remains the implementing organisation's. The framework provides visibility as a structural feature of substantive operation; it does not provide the substantive operation itself. Organisations that operate the framework with honesty produce structural trust that compounds over years; organisations that operate the framework without honesty produce visibility that eventually shows what they actually are. The framework is, in this sense, a substantive instrument rather than a rhetorical one. It rewards what is substantively done and exposes what is not. The four bearings are available to readers who want to engage with the framework from any of the four directions the compass offer. The whitepaper remains the framework itself. The implementing organisations that engage with all of this will do the work that the framework supports — and the work is theirs. What the supporting material has been able to do is make the framework legible in language that practitioners in many positions can recognise, so that Joacim Brandell 5 / 6 _The connector and pathfinder_ PDCA+ Companion v 1.0 the decision to engage with it can be made with the framework's structural commitments understood and the consequences of engagement available for examination. The compass is ready. The reader's bearings are the reader's own. **T H E C O M P A N I O N , I N O N E S E N T E N C E** _PDCA+ Companion v 1.0 is the connector and pathfinder of the supporting material that surrounds the PDCA+ v2.0 whitepaper — twenty pieces of work organised into four bearings forming a compass, with this centerpiece making the compass itself visible so that readers can enter the framework's territory from whichever bearing serves their current concern. The work itself still needs doing; the framework supports the work; the implementing organisation does it._ Joacim Brandell 6 / 6