We scan new podcasts and send you the top 5 insights daily.
Frameworks like RACI or DACI work for execution but break down during annual planning when leaders pass accountability across organizational seams. Without clear decision owners, teams swirl, make backdoor changes in Slack, and repeatedly renegotiate decisions after meetings end.
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.
The Directly Responsible Individual (DRI) model is not just for accountability. Its primary purpose is to eliminate product slowdowns caused by "silent vetoes" from cross-functional teams. It empowers a single person to cut through bureaucracy and drive decisions across the entire product lifecycle.
As companies grow, decision-making can slow down due to ambiguity. Plaid combats this by explicitly naming one person as the on-point decision-maker for every task at the conclusion of meetings. This clarifies accountability and accelerates execution.
Frameworks like RACI and DACI suit program execution and approvals, but fall apart during annual planning negotiations. Without designated owners for specific decisions, leaders either avoid accountability or negotiate changes through back-channel emails and Slacks to wield influence after meetings conclude.
The RACI matrix is frequently a fictitious document, created once by a project manager and then filed away. It doesn't reflect the reality of how decisions are made and is typically only referenced after something has gone wrong to assign blame, rather than to provide proactive clarity.
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.
Not all decisions are equal, and treating them the same causes micromanagement. Frame decisions at three levels: Level 1 for strategic bets (owned by the CEO), Level 2 for product bets (owned by product leaders), and Level 3 for daily execution (owned by teams).
As teams grow, ambiguity over ownership increases, causing key tasks to be dropped. The RACI model (Responsible, Accountable, Consulted, Informed) combats this by clarifying roles upfront for any project, ensuring clear ownership and preventing the diffusion of responsibility that paralyzes larger groups.
The primary source of friction between product and project functions isn't a lack of skills but rather unclear ownership, siloed planning, and conflicting success metrics. The solution is proactive, early alignment on roles, tools, and a shared definition of success.
Enforce a strict separation between who provides input and who makes the decision. Input should be broad (customers, data, stakeholders), but the decision must be singular and accountable. When the input group is also the decision group, you get a committee that optimizes for safety, not outcomes.