KD-019 · Framework
Status → Constraint → Decision
Show why executive reporting should expose the constraint and decision hidden behind a status color.
- Evidence level
- Experience based
- Executive audience
- CEO, COO, program sponsor
- Publication status
- Published after human review
Inspect the operating model
Rendering diagram…
Text alternative and Mermaid source
Status → Constraint → Decision. Show why executive reporting should expose the constraint and decision hidden behind a status color. Business problem: Status reporting can describe local progress while the enterprise-level constraint remains invisible. Claim boundary: Experience-based operating model. It does not establish a client outcome, budget result, recovery result, or universal delivery prescription.
flowchart LR
G[Green / amber / red status] --> C[Named constraint]
C --> E[Evidence and exposure]
E --> D[Decision owner]
D --> A[Action, escalation, or stop]Why this matters
Status reporting can describe local progress while the enterprise-level constraint remains invisible.
Executive decision
- Require each material status signal to resolve to a constraint, evidence, decision owner, and next action.
Claim boundary
Experience-based operating model. It does not establish a client outcome, budget result, recovery result, or universal delivery prescription.
Evidence summary
tko:ev-operational-intelligence-vs-reporting
Across healthcare, RachelOS, and CRE engagements, dashboards and reports describe what happened, but the decision about what to do next still depends on a person — reporting is not the same capability as operational intelligence.
Boundary: Generalized finding from cited code- and pattern-backed records. No metric.