Abrigo·Marrón Systems

El Enfoque The Approach

A system is governed by functions, not by an organization chart.

The chart tells you who reports to whom. It does not tell you whether anyone is scanning the environment, whether coordination is happening, or where a decision goes when it has no obvious owner. Those are the questions that decide whether the thing stays viable.

Primera Distinción First Distinction

Management runs the work. Governance keeps the enterprise able to run work at all.

The two get collapsed into each other constantly, usually by people who are good at the first one. Management is concerned with execution: the schedule, the budget, the crew, the deliverable. Governance is concerned with whether the enterprise doing the executing can still identify itself, direct itself, coordinate its own parts, learn from its own mistakes, and notice the world changing around it.

An organization can be superbly managed and ungoverned. It happens all the time, and it looks like this: every individual project is well run, every department hits its numbers, and the enterprise as a whole drifts, duplicates itself, re-learns the same lesson in four places, and is surprised by developments its own people saw coming two years earlier. Nobody failed. The functions that would have caught it were never assigned to anyone.

El Metasistema The Metasystem

Nine functions that must be performed somewhere.

The complex system governance reference model names the functions a complex system must perform to remain viable, and separates them from the productive units that do the actual work. The functions are not boxes on a chart and not job titles. They are activities. In any real organization they are distributed across people, committees, habits, spreadsheets, and a few individuals who hold things together without being asked to.

The diagnostic value is in the asking. For each function: who performs this, how do they know they are performing it, and what happens when they do not?

Below the metasystem sit the productive subsystems that generate the enterprise's actual output. They are governed; they are not part of the governance. Treating them as interchangeable with the metasystem is one of the more reliable ways to produce an organization that cannot get out of its own way.

Los Axiomas The Axioms

Why any of this should be believed.

The governance model is not a consulting framework someone invented in a hotel conference room. It is an attempt to make a century of systems theory operational. That theory has been organized into a small set of axioms, each gathering a family of underlying laws and principles. They are stated below in plain language rather than in their scholarly form.

El Método Diagnosis Before Prescription

Name the pathology, then design the fix.

The practical contribution of this literature is that governance dysfunction has been catalogued. Deficiencies in these functions recur with enough regularity across enough organizations that they can be described, looked for, and distinguished from one another — a missing function is a different problem from a starved one, which is different again from two groups quietly performing the same function in competition.

This is why we do not open an engagement with a recommendation. A recommendation offered before diagnosis is an opinion wearing a deliverable's clothes. The sequence is: establish the context honestly, determine which functions are actually being performed and by whom, identify the deficiencies, and only then design something — in the specific situation, with the specific constraints, for the people who will have to live inside the result after we are gone.

The useful question is almost never what should this organization do. It is what is preventing this organization from already knowing what to do.

Primary source for the governance model: Keating, Katina, Jaradat and Bradley, Complex System Governance: Theory and Practice (Springer, 2022), standing on Beer's management cybernetics and the general systems theory tradition that precedes it. The framework is theirs. The field testing, the plain-language rendering, and any errors in it are ours.