PMIU-X360
The five layers of a SaaS business that determine whether execution actually works - and a framework for diagnosing which ones are breaking.
PMIU-X360 is used diagnostically during Execution System Diagnostics - to find where the system is structurally breaking - and prescriptively during Execution Resets to redesign the failing layers. It is not a project management methodology. It is a structural diagnostic and intervention framework: five layers, nineteen sub-properties, and a defended cascade architecture that sequences interventions in causal order.
Five layers. Diagnosed, designed, operated, evolved.
One framework. Applied consistently.
Most consultants improvise methodology per engagement. The result is diagnostic inconsistency - findings that reflect the consultant's instincts more than the organization's actual structure.
PMIU-X360 creates a consistent diagnostic lens across every engagement. The same five layers are assessed in every organization, which means findings are comparable, root causes are more reliably identified, and interventions are more precisely targeted.
The framework is not sold. It is embedded in every engagement Agilocrats delivers.
Product Decisions
Whether the organization can decide what to do, what not to do, and what to undo - at the velocity and quality the business demands.
Product Decisions is the spine of the framework. Its weakness cascades into every other layer faster and more thoroughly than any other layer's weakness - most notably into Data & AI and Unit Economics of Delivery. It is structurally the largest layer, with five sub-properties: Rights & Authority, Velocity & Reversibility, Propagation & Execution Translation, Provenance & Re-litigation Hygiene, and Meta-Decision Hygiene.
Diagnostic Focus
- Whether five executives give the same answer to "who decides X?"
- Median time from a decision to the first code change reflecting it
- Whether the same decisions get re-debated instead of referenced from a log
Market & Customer Signals
Whether market, customer, operational, and engineering reality reaches decision-makers intact, in time - including the signals the organization would prefer not to hear.
This is the nervous system of the framework. Organizations that fail catastrophically are rarely missing signal - they are unconsciously filtering inconvenient signal. Its four sub-properties are Signal Generation, Pathways & Latency, Signal Fidelity, and Signal Acceptance: the structural capacity to take inconvenient signal seriously.
Diagnostic Focus
- Median latency from signal generation to decision-maker awareness, per source
- Whether signals arrive undistorted, or smoothed and optimistically reframed in transmission
- Whether inconvenient signals get the same analytical weight as confirming ones
Data & Artificial Intelligence
Whether data converts to decisions and execution-changes before or during the moment they're made - faster than the conditions producing the data shift.
The tightest, most temporally pure layer in the framework: forward-looking and in-flight only. Retrospective learning belongs to Layer 5, not here. Its two sub-properties are Decision Intelligence (pattern detection augmenting leadership decisions) and Execution Intelligence (AI embedded in the workflow, not bolted on, with measured impact).
Diagnostic Focus
- Count of decisions per quarter where data or pattern detection visibly changed the outcome
- Number of workflows with AI embedded and measurably changing cycle time or quality
- Whether AI usage is individual and anecdotal, or institutional and measured
Unit Economics of Delivery
Whether decisions reliably become shipped work - through nested rhythms that ladder up coherently from individual work to strategic horizon - and whether output scales with investment.
The rhythm of the system, and the most-sink layer in the cascade: it receives influence from Layers 1, 2, 3, and 5, and emits very little of its own. That is why it is almost always a symptom layer in diagnostics, not a root layer. Its sub-properties are Rhythm Architecture, Cadence Coupling, Throughput Integrity, and Ritual-to-Outcome Discipline.
Diagnostic Focus
- Whether sprint work is traceable to a current OKR, and OKRs to strategic bets
- Whether throughput per engineer holds as headcount grows
- Meeting load per IC and whether retrospective actions actually close
Cross-Functional Feedback Loops
Whether past outcomes - wins, failures, customer responses, execution results - produce behavioral change and durable institutional memory, on a timescale that matters.
Layer 5 is the self-correcting loop of the system, and the only layer with strong outbound influence into every other layer. Without it, every other layer's fixes can be installed once and decay. Its sub-properties are In-Function Learning Loops, Cross-Function Learning Loops, Loop-to-Decision Coupling, and Institutional Memory.
Diagnostic Focus
- Whether the same failure recurs within a function within eighteen months
- Median time from an outcome in one function to behavioral change in another
- Whether a new hire can retrieve what was tried before, and why, within thirty minutes
Interventions are sequenced in causal order, not visibility order.
The five layers are not independent. Weakness in one cascades into others, and the cascade is not symmetric. Layer 1 is the spine - it emits the most causal influence. Layer 4 is the most-sink layer - it absorbs influence from every other layer and emits almost none. Layer 5 is a loop layer - both a major source and a major sink, feeding learning back into the entire system. This asymmetry produces three non-negotiable rules for every diagnostic.
Fix Layer 1 first if it is below Stage 3
Product Decisions is the spine. Fixing Layer 4 with a broken Layer 1 produces faster theatre - visible symptoms recede temporarily and return, often worse, within two cycles.
Build Layer 5 alongside Layer 1, not after it
Layer 5 is the only layer with strong outbound pathways into every other layer. Without it, Layer 1 fixes drift within twelve to eighteen months as the organization has no loop to detect and correct the decay.
Don't enter the system through Layer 4
Layer 4 is the most visible symptom and the most tempting entry point - the missed sprints, the meeting overhead. It is structurally a sink, not a source. We receive the complaint, validate it as real pain, and trace it upstream before intervening.
Diagnostically first. Prescriptively second.
Execution System Diagnostic
All five layers are assessed to identify structural gaps. The diagnostic produces a map of where the execution system is breaking and why - not just where symptoms appear.
SaaS Execution Reset
The diagnostic findings are used to prescribe and implement targeted interventions in the failing layers. The framework ensures interventions address root causes rather than surface symptoms.
AI-in-Execution Enablement
A narrow, deep engagement targeted specifically at Layer 3B (Execution Intelligence) - embedding AI inside one workflow with measured impact. It is not sold if Product Decisions scores below Stage 3, Feedback Loops below Stage 2, or Unit Economics below Stage 2 - the capacity would not be absorbed or compounded.
AWS Modernization
Cloud modernization programs are assessed through Layers 1 and 4 - examining how architectural decisions flow and whether the unit economics of delivery can absorb modernization without disrupting product velocity.