Show notes
Delegation, Daniel argues, is a trap: you offload the doing but keep the deciding, so you're still the bottleneck with extra coordination on top. The fix is explicit decision rights — who can decide what, up to what threshold, without asking.
He shares Meridian's framework for assigning decision rights, the guardrails that make founders comfortable letting go, and the failure mode where rights are given but authority isn't.
The compounding angle: a team that can decide gets faster every quarter; a team that can only execute needs you forever.
Key takeaways
- Delegating tasks keeps you as the bottleneck; delegating decisions removes you
- Decision rights need thresholds and guardrails, not just permission
- Giving rights without real authority breeds learned helplessness
- A team that can decide compounds; a team that only executes doesn't
Transcript excerpt
Marcus
What's the difference between delegation and decision rights, in one sentence?
Daniel
Delegation is 'do this and check with me.' Decision rights is 'own this up to here, and I'll trust the call.'
Resources
