Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Costolo argues against the common reaction to add process steps to prevent future mistakes, which leads to bloat like 17-page launch checklists. Instead, he advises assigning a clear DRI and managing for outcomes, not adherence to processes.

Related Insights

In a highly collaborative and fast-paced environment, assign explicit ownership for every feature, no matter how small. The goal isn't to assign blame for failures but to empower individuals with the agency to make decisions, build consensus, and see their work through to completion.

If two people are responsible for watering a plant, it dies from either overwatering or neglect. This is why scaling companies must be zealous about assigning a single Directly Responsible Individual (DRI) for every key initiative. Shared ownership means no ownership, especially for cross-functional projects.

To combat diffused responsibility, starting a committee at Coinbase requires explicit CEO or COO approval. This forces the assignment of a single "Directly Responsible Individual" (DRI), ensuring clear ownership, accountability, and faster decision-making.

To combat methodical slowness at Twitter, Costolo's first move as CEO was to end consensus-based decision-making. He pushed ownership down the org chart to individual leaders, holding them accountable and dramatically increasing the cadence of execution.

To make a project successful, it must be the top priority for a specific individual. Giving them the title "CEO of their domain" inspires founder-level ownership and prevents important initiatives from being neglected or de-prioritized.

A common mistake when systemizing a business is trying to document every single process, which is inefficient and overwhelming. Instead, identify the few critical processes that are absolutely vital to your value delivery and focus all documentation and systemization efforts on those mission-critical areas first.

When a project stagnates, it's often because "everyone's accountable, which means no one's accountable." To combat this diffusion of responsibility, assign one "single-threaded owner" who is publicly responsible for reporting progress and triaging issues. This clarity, combined with assigning individual names to action items, fosters true ownership.

Owning a project launch means being accountable for its success, requiring more than execution. It involves proactively identifying all possible failure modes (technical, infrastructural, etc.) and systematically working backward to prevent them. This active risk mitigation is the essence of strong ownership.

To inject responsibility into a speed-obsessed culture, frame the conversation around specific risks. Create documented assumptions about what might break and, crucially, identify who bears the impact if things go wrong. This forces a deliberate consideration of consequences.

A Tech Lead can't do everything. Using "recursive accountability," the lead (as the Directly Responsible Individual) delegates ownership of sub-problems to others. While they own their pieces, the lead remains ultimately accountable for the entire project, preventing a "that wasn't my part" mentality.

Solve Operational Problems With Directly Responsible Individuals (DRIs), Not More Processes | RiffOn