Reference
Key terms and concepts in the Triad Flow™ execution operating model. Each term is defined in the context of the framework’s structural principles.
The conditions defined by the Driver that determine whether delivered work achieves its purpose. Acceptance is a Driver domain decision — the Maker and Guardian cannot override it.
A structured recurring event in a delivery process. In Triad Flow™, ceremonies are minimized because sound structure provides the confidence that ceremonies attempt to create. When structure is sound, there is less to compensate for.
The core structural principle of Triad Flow™. Complete decision authority resides at the point of execution within the Execution Triad. No external approvals, handoffs, or coordination are required for the triad to deliver value.
The organizational expense of aligning, synchronizing, and communicating across fragmented ownership boundaries. At enterprise scale, coordination cost frequently exceeds execution cost — a condition Triad Flow™ terms the Coordination Cost Inversion.
The condition where an organization spends more time and resources coordinating than executing. The ratio may reach 60:40 or worse. This inversion is a structural condition, not an operational failure.
An enterprise structural role that protects the operating model itself. Watches for ownership erosion, ceremony creep, and boundary violations. Does not manage triads — protects the conditions under which triads function.
A distinct sphere of authority within the Execution Triad. Each role (Driver, Maker, Guardian) owns a specific decision domain. Domains are sovereign — no role outranks another within its domain.
The first role in the Execution Triad. Owns intent, outcomes, and acceptance. Defines the problem, sets priorities, establishes success criteria, and determines whether delivered work achieves its purpose.
The minimal execution unit in Triad Flow™, consisting of three co-equal roles: Driver, Maker, and Guardian. Together, the three domains encompass everything required to deliver value. Authority and accountability are co-located.
The unit of work progression in Triad Flow™, replacing fixed-duration sprints. A flow cycle begins when intent is clear and completes when readiness is achieved. Duration is determined by the work, not the calendar.
The third role in the Execution Triad. Owns risk, readiness, and release confidence. Assesses quality, security, compliance, and operational preparedness. Exercises judgment about whether work is safe to ship.
Triad Flow™’s approach to governance where risk assessment is embedded in execution rather than positioned as an external checkpoint. The Guardian applies organizational standards directly, with escalation only for non-routine situations.
The second role in the Execution Triad. Owns design and implementation. Determines architectural choices, technical approach, and sequencing. Has full authority over how the solution is constructed.
An enterprise structural role that maintains directional coherence across autonomous triads. Clarifies strategic intent, surfaces conflicts early, and prevents dependency sprawl. Aligns direction through constraints and intent rather than coordinated activity.
The governing constraint in flow-based progression. Work progresses when the Guardian determines it is ready to ship, not when a calendar boundary is reached. Readiness replaces time as the primary flow governor.
An enterprise structural role warranted only at very large scale. Observes systemic patterns that no individual triad can see — enterprise-wide friction, structural drag, flow health variations. Operates through insight, not mandate.
Enterprise-level roles (Custodian, Orchestrator, Steward of Flow) that protect the conditions enabling flow as organizations scale beyond individual triads. They do not coordinate work — they protect structural integrity.
An execution operating model built from first principles for enterprise delivery. Centers on consolidated ownership through the Execution Triad and flow-based progression. Not a methodology or prescriptive framework — a structural pattern for organizing delivery.
See how these terms come together in the operating model, or explore the book series for the complete treatment.