Course 11
DRI & Ownership
Owning Outcomes Without a Chain of Command
Block inverted the org chart. Intelligence in the system. People at the edge. This is how you operate as a DRI — a Directly Responsible Individual.
The Problem with Hierarchy
Roman Army
Span of Control
Layers = Latency
Prussian General Staff
Staff Officers
Information Routing
Modern Corporation
Matrix Organization
Bureaucracy = Speed Tax
What if you replaced what hierarchy does —
not just the people?
What Is a DRI?
A DRI owns a specific problem or customer outcome for a defined period — with full authority to pull resources across functional teams.
Example Mandate
Problem
Merchant churn in restaurant segment
Scope
QSR restaurants, < $500K annual processing, US only
Success Metric
Reduce 90-day churn from 18% to 12%
Time Horizon
90 days
Example Mandate
Problem
Square Capital deployment experience
Scope
End-to-end merchant journey, iOS + Android
Success Metric
Increase conversion from application to funded from 34% to 45%
Time Horizon
90 days
Example Mandate
Problem
Cash App direct deposit conversion
Scope
New Cash App users, first 60 days of activation
Success Metric
Lift direct deposit activation by 22% in test cohort
Time Horizon
90 days
The Edge Person's Toolkit
Sensing what the model can't perceive
Context Reading
The model sees data. The edge sees the room. Intuition, trust dynamics, cultural context, the feeling in a space — these are unmeasurable but real.
How to Practice
Before every major decision, write down three things the data can't tell you about this situation.
The 90-Day DRI Arc
Days 1-7
+
Understand + Map
Days 8-30
+
Execute + Signal
Days 31-60
+
Evaluate + Adjust
Days 61-90
+
Resolve + Handoff
Failure as Signal
Failures are not disasters to bury. They are signals to extract. A structured postmortem generates the insights that improve the system.
What happened
API integration failed during peak transaction hour
Why it happened
Timeout threshold was set too low; no circuit breaker existed; monitoring alert fired 4 minutes after failure began
What it signals
The payments capability lacks a resilience layer that composes gracefully under load. This gap exists in other capabilities too. Future compositions that depend on payments need this capability to exist first.
DRI Mandate Builder
Live Preview
Problem
[not defined]
Scope
In:
[not defined]
Out:
[not defined]
Metric
[not defined]
Horizon
90 days
Resources
[not yet identified]