Principle 1 · Flow & Delivery Dynamics
Intake Within Capacity
Work Intake Within System Capacity Sustains Flow
When it’s ignored: Lead times stretch and grow less predictable as work waits longer in queues.
Find the principle behind the problem you keep seeing.
Each principle explains how a healthy delivery system behaves and what breaks when it is violated. Start with what you’re seeing, or browse by diagnostic dimensions.
20 Principles · 5 Dimensions
Filter by Problem Pattern
Pick up to three patterns in the interactive library.
- Lead times keep growing
- Lots started, little finished
- Problems are found late, after release
- Priorities keep shifting
- Decisions stall or keep escalating
- We ship, but outcomes don't improve
- Nobody clearly owns the outcome
- Every fix creates a new problem
- The same problems keep coming back
- We can't tell if AI output is right
Principles for the whole system
Browse by Diagnostic Dimension
Flow & Delivery Dynamics
How efficiently and predictably does value move through the system?
Principle 2 · Flow & Delivery Dynamics
Upstream Quality
Upstream Quality Reduces Downstream Failure Propagation
When it’s ignored: Defects and wrong assumptions travel through several stages before anyone catches them.
Principle 3 · Flow & Delivery Dynamics
Cut Non-Value Work
Reducing Non-Value Work Increases Value-Creating Capacity
When it’s ignored: Lead times grow as coordination and admin take a bigger share of capacity.
Principle 4 · Flow & Delivery Dynamics
Explicit Constraints
Explicit Constraints Clarify Priorities
When it’s ignored: With no agreed constraints, priorities feel subjective and keep changing.
Principle 5 · Flow & Delivery Dynamics
Handoff Cost
More Handoffs Increase Coordination Cost
When it’s ignored: Lead time grows with each handoff as work waits in the next queue.
About this territory
How work enters, moves through and exits delivery. Violations show up as long lead times, unpredictability, firefighting and release instability.
Learning, Adaptation & Decision Quality
Is the system capable of updating itself based on evidence?
Principle 6 · Learning, Adaptation & Decision Quality
Evidence over assumption
Evidence-Based Decisions Reduce Assumption Risk
When it’s ignored: Wrong assumptions persist, and risk builds quietly behind confident narratives.
Principle 7 · Learning, Adaptation & Decision Quality
Progressive Commitment
Progressive Commitment Reduces Uncertainty Exposure
When it’s ignored: Late discoveries force expensive rework, rollback or abandonment.
Principle 8 · Learning, Adaptation & Decision Quality
Closing the Learning Loop
Continuous System Learning Sustains Performance
When it’s ignored: Known problems become fixtures that teams work around instead of removing.
About this territory
How organizations form beliefs, test them and change direction based on what they learn. Violations show up as output without impact, strategy drift and false confidence.
System Integrity & Architectural Coherence
Can the organization still understand, reason about, and safely evolve the system?
Principle 13 · System Integrity & Architectural Coherence
Optimize the Whole
Optimizing the System as a Whole Improves and Sustains System Outcomes
When it’s ignored: The constraint keeps moving as each team's local fix creates a new bottleneck.
Principle 14 · System Integrity & Architectural Coherence
End-to-end capability
End-to-End Capability Reduces Dependency and Improves Flow
When it’s ignored: Lead time grows while work waits for capabilities the team lacks.
Principle 15 · System Integrity & Architectural Coherence
Second-Order Effects
New Solutions Create New System Constraints
When it’s ignored: Each new solution adds constraints faster than old ones get resolved.
Principle 16 · System Integrity & Architectural Coherence
Original Intent
Understand the Original Intent Before Removing or Replacing Existing Capabilities
When it’s ignored: Problems you'd already solved come back under new names.
About this territory
How systems hold together as they grow and change. Violations show up as hidden dependencies, cascading failures and an inability to evolve the system safely.
Human-AI Collaboration Dynamics
Is AI augmenting human judgment or replacing it prematurely?
Principle 17 · Human-AI Collaboration Dynamics
Observe Before Expanding
Greater Observability Enables Safer Expansion of Autonomy
When it’s ignored: Learning about agent behavior has slowed because nobody can inspect it as it runs.
Principle 18 · Human-AI Collaboration Dynamics
Task-fit delegation
Automate by Task Nature, Not Capability
When it’s ignored: Rule-based work is slower, less predictable and harder to audit than fixed code.
Principle 19 · Human-AI Collaboration Dynamics
Earned Agent Trust
Agent Trust Must Be Continuously Earned, Not Historically Assumed
When it’s ignored: Reviews thinned by past success miss early signals of serious agent failures.
Principle 20 · Human-AI Collaboration Dynamics
Surface agent uncertainty
Agents Must Surface Uncertainty Explicitly
When it’s ignored: Failures arrive with no warning because the agent never raised a signal.
About this territory
Whether humans and agents reinforce or degrade each other. Violations show up as human disengagement, blind trust in AI outputs, oversight collapse and judgment atrophy.
How to use this library
Problem → Principle → Action. Explore an Overview, check your observations in Diagnose, then consider practices in Act.