Leaders often fail to create clarity not out of malice, but because it is intellectually difficult and politically risky. Setting clear priorities forces tough trade-offs and can make some teams feel less important, which threatens a leader's own narrative and sphere of influence.

Don't assume Human Resources owns the solution to role confusion. Modern HR departments are often not trained in organizational design and lack the expertise to address these deep-seated structural problems. The responsibility ultimately falls to senior leadership to define the operating model.

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.

Effective delegation of decision-making authority is impossible without first ensuring leaders are deeply aligned on organizational objectives. When individuals are empowered to make choices but pull in different directions, the result is a quagmire, not progress. Alignment must precede autonomy.

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.

Many leaders fight bureaucracy like an external threat. The real cause is the organization's design: too many layers, functional silos, and distant decision-making. To fix bureaucracy, you must fundamentally change the organizational structure, not just treat symptoms.

Instead of immediately diving into documenting roles with tools like RACI, the first step should be to identify and name a "referee." This is an individual or body with the explicit, recognized authority to arbitrate and settle role-based disputes when they inevitably arise.

When local teams don't adopt a centrally-developed AI, it's not irrational resistance. It's a predictable response to executing a system they had no role in creating and cannot formally challenge, even when it contradicts their on-the-ground knowledge. Non-adoption becomes their only form of dissent.

Job descriptions are written to attract candidates, not to guide daily decision-making. Relying on them for operational clarity creates a gap between what's on paper and who actually decides, leading to career-killing confusion. They are the wrong artifact for clarifying real-time roles and responsibilities.