Principles Library

Entrowise's Principles Library contains 38 fundamental delivery principles organized by domain. Each principle captures a truth about how healthy delivery systems behave—and what goes wrong when it is violated. These principles form the backbone of the PPA Method (Problem → Principle → Action).

Browse by category. Each principle page includes the principle intent, early warning signs of violation, systemic consequences, coaching questions, anti-patterns to avoid, and recommended practices for making the principle a system property.

Five Diagnostic Territories

Each category targets a distinct class of system problem. Start with the territory that matches what you are facing.

Flow & Delivery Dynamics

Diagnose why work moves slowly, unpredictably, or accumulates hidden delay.

System Question: How efficiently and predictably does value move through the system?

This category contains principles that govern how work enters, moves through, and exits the delivery system. Violations produce long lead times, delivery unpredictability, firefighting, and release instability. In agentic systems, execution speed increases dramatically while coordination overhead shifts from humans to pipelines, making invisible queue buildup and downstream error amplification harder to detect.

Learning, Adaptation & Decision Quality

Diagnose whether the organization is learning fast enough to make valid decisions under uncertainty.

System Question: Is the system capable of updating itself based on evidence?

This category contains principles that govern how organizations form beliefs, test them, and change direction based on what they learn. Violations produce output without impact, strategy drift, false confidence, and metrics disconnected from reality. In agentic systems, prediction replaces observation, velocity hides decision degradation, and automation scales assumptions before they are validated.

Governance, Accountability & Decision Authority

Diagnose whether the organization can safely govern increasingly autonomous systems.

System Question: Who is allowed to decide, who is accountable, and how is control maintained?

This category contains principles that govern how authority is structured, how accountability is assigned, and how decisions are made visible and traceable. Violations produce accountability fragmentation, governance ambiguity, escalation bottlenecks, and unsafe autonomy. Most organizations treat governance as security review or model approval. Entrowise treats governance as continuous operational system design.

System Integrity & Architectural Coherence

Diagnose whether the system can maintain coherence as complexity increases.

System Question: Can the organization still understand, reason about, and safely evolve the system?

This category contains principles that govern how systems hold together as they grow, accumulate change, and add new components. Violations produce hidden dependencies, cascading failures, and an inability to explain or evolve the system safely. In agentic systems, complexity compounds faster and system coherence degrades without deliberate architectural discipline.

Human-AI Collaboration Dynamics

Diagnose whether humans and agents are reinforcing each other or degrading each other.

System Question: Is AI augmenting human judgment — or replacing it prematurely?

This category does not exist in classical Agile, Lean, or Scrum. It is Entrowise's most differentiated diagnostic territory. As AI agents take on more execution, whether humans remain capable of governing what they have built becomes a first-order delivery risk. Violations produce human disengagement, blind trust in AI outputs, oversight collapse, and judgment atrophy. This category will grow as agentic delivery patterns mature.

Flow & Delivery Dynamics

• Build Quality In — Design the system so defects are unlikely to occur and quickly visible when they do. Quality is shaped by how work is created, verified, and learned from across human and AI-assisted delivery.
• Eliminate Waste — Remove activities that do not directly contribute to customer value. Waste consumes time, attention, and capacity without improving outcomes.
• Deliver Value Fast (Reduce Lead Time) — Reduce the time from idea to validated value in order to lower risk and accelerate learning. Shorter lead times tighten feedback loops and expose problems when they are still inexpensive to fix.
• Incremental Delivery — Deliver value in small, meaningful increments to reduce uncertainty and enable learning. Incremental delivery exists to discover the right solution when outcomes cannot be known upfront.
• Constraints Create Focus — Use clear, intentional constraints to enable focus, prioritization, and effective decision-making. In complex systems, constraints make trade-offs explicit and allow autonomy to function.
• Every Hand-Off Has a Cost — Every transfer of work between people, teams, or systems introduces delay, context loss, and diluted accountability. Hand-offs are a system design choice, and their cost compounds as work flows across boundaries.
• Visualize Work — Make all work and work states visible so flow can be understood, managed, and improved. Visibility enables shared understanding, early intervention, and better decisions.
• Limit Work in Progress (WIP) — Limit the amount of work in progress to reduce overload, improve flow, and increase predictability. Finishing work faster requires starting less work at the same time.
• Manage Flow — Actively manage how work moves through the system to improve predictability, reliability, and learning. Flow must be observed, guided, and adjusted—not assumed.
• Small Batches — Reduce batch size to improve flow, surface problems earlier, and lower delivery risk. Small batches optimize flow and learning by shortening feedback cycles, not by fragmenting work arbitrarily.

Learning, Adaptation & Decision Quality

• Defer Commitment (Last Responsible Moment) — Make irreversible decisions as late as responsibly possible, when sufficient information is available. Preserving options enables better economic decisions while maintaining accountability.
• Continuous Improvement (Kaizen) — Continuously improve the system through learning, feedback, and small experiments. Improvement depends on evidence, follow-through, and the ability to learn from outcomes.
• Embrace Change — Adapt plans and priorities based on learning and emerging realities. In complex systems, change is evidence of learning—not a failure of planning.
• Frequent Feedback Loops — Create frequent, meaningful feedback loops that inform decisions and guide adaptation. Feedback is how learning enters the system and influences behavior.
• Value Is Contextual and Time-Dependent — Recognize that value is not fixed. It evolves based on timing, context, and changing conditions. Decisions about what is valuable must be continuously revisited as assumptions, needs, and environments change.
• Learning Before Scaling — Stabilize, understand, and improve systems before expanding them. Scaling amplifies existing behavior; without learning, it accelerates dysfunction.
• Empiricism — Base decisions on observation, evidence, and learning rather than prediction or assumption. Empiricism governs how decisions remain legitimate under uncertainty.
• Timeboxed Learning Cycles — Enforce a fixed cadence for inspection and adaptation so learning cannot be postponed by delivery pressure. Timeboxing exists to protect learning and decision quality, not to optimize delivery speed.
• Commitment to Outcome Intent — Commit to a clear outcome intent within a fixed timebox, not to predefined scope or output. Commitment exists to create stability for learning and decision-making, not rigidity of execution.

Governance, Accountability & Decision Authority

• Empowered, Cross-Functional Teams — Design teams with the skills, authority, and context required to deliver end-to-end value. Empowered, cross-functional teams reduce dependencies, speed decisions, and improve ownership.
• Transparency — Make work, risks, progress, and outcomes visible so decisions are grounded in shared reality. Transparency enables informed action; without it, decisions are based on assumptions and perception.
• Accountability Must Match Control — Responsibility for outcomes must be aligned with the authority and control required to influence those outcomes. Accountability only works when people can actually change the result.
• Alignment over Compliance — Create shared understanding and intent so people can make good decisions without constant enforcement. Sustainable performance depends on judgment guided by purpose, not obedience to rules.
• Vague Guidance Creates False Alignment — Guidance that is abstract or underspecified creates the illusion of alignment while allowing divergent behavior. Alignment exists only when expectations are clear, observable, and actionable.
• Human Accountability Cannot Be Delegated — Ensure that humans remain accountable for outcomes, even when decisions or actions are supported, recommended, or executed by AI systems. AI may assist or automate—but responsibility for results must remain human.
• Decision Authority Must Be Explicit — Make decision authority between humans and AI systems explicit, deliberate, and visible. AI may recommend, advise, or execute actions only within clearly defined decision boundaries.
• Observability Before Autonomy — Ensure AI systems are observable and understandable before granting them autonomous action. Humans must be able to see, interpret, and learn from AI behavior before autonomy is expanded.
• Make Policies Explicit — Make decision rules, working agreements, and boundaries explicit so work can flow predictably and fairly. Explicit policies reduce ambiguity, unnecessary escalation, and inconsistent outcomes.

System Integrity & Architectural Coherence

• Optimize the Whole — Optimize the end-to-end value delivery system rather than individual teams, functions, or components. System performance is determined by flow across the whole, not by local efficiency.
• More Choices Make Decision-Making Harder — Limit the number of active choices so decisions can be made quickly, confidently, and owned clearly. As option sets grow, decision quality and accountability decline.
• New Solutions Create New System Constraints — Every solution introduced to address a problem creates new constraints elsewhere in the system. System health depends on anticipating and managing these second-order effects, not just solving the immediate issue.
• Understand the Original Intent Before Removing or Replacing Existing Capabilities — Before removing or replacing existing capabilities, understand why they were introduced and what risks they were designed to manage. Many systems encode historical learning that is no longer obvious but still relevant.

Human-AI Collaboration Dynamics

• Respect People — Design the system so people closest to the work can take ownership, make decisions, and learn. Respect is expressed through clear authority, meaningful responsibility, and conditions that enable people to think.
• Feedback Loops Must Include AI Behavior — Explicitly include AI behavior in feedback loops so learning, accountability, and improvement apply to the full human–AI system. AI-influenced decisions must be inspectable, reviewable, and learnable—just like human ones.
• Context and Intent Precision Determines Outcome Quality — In an AI-augmented delivery system, the quality of outcomes is determined upstream, at the point where context is established and intent is specified. Agents execute faithfully against what they are given. If the context is incomplete or the intent is vague, no amount of execution quality recovers the outcome.
• Agent Trust Must Be Continuously Earned, Not Historically Assumed — Trust in an agent system must be grounded in current, observed behavior — not in historical performance. An agent that performed reliably in the past provides no guarantee of reliable performance today. As context shifts, configurations age, and novel situations arise, trust based on history becomes a governance liability.
• Traceability Must Be Designed In, Not Added After — The ability to trace a decision to its cause, its inputs, and its reasoning must be built into a system before it operates — not retrofitted after something goes wrong. In systems where decisions cannot be traced, accountability is symbolic, learning cannot occur, and the same failures recur without explanation.
• Agents Must Surface Uncertainty Explicitly — Agent systems must be designed to surface uncertainty, ambiguity, and boundary conditions rather than proceeding with false confidence. An agent operating outside its reliable range must flag it rather than execute as if the range were sufficient. The human can only intervene at the right moment if the system signals when intervention is needed.

How to Use This Library

When facing a recurring delivery problem, use the PPA Method: first understand the problem at the system level, then identify which principle from this library is being violated, then take deliberate action that reinforces the principle. Each principle page includes coaching lens questions and anti-patterns to guide this process.

Learn how principles are applied in the PPA Method | Use the AI agent to identify violated principles in your situation | Join a leadership cohort program