What goes wrong when you ignore that role-based authority?

The most common reason fails: Role ambiguity — defining roles so vaguely that authority overlaps, gaps exist, and conflicts arise about who has the authority to decide. The most common role-based authority failure is poorly defined role boundaries: two roles that both claim authority over the same decision domain, or a decision domain that no role covers. This ambiguity recreates the dysfunction that role-based authority was designed to solve — decisions escalate because no one is confident they have the authority to decide. The antidote is explicit role definition: clear statements of the decisions each role authorizes, the boundaries between roles, and the protocols for handling decisions that fall in boundary zones.

The fix: Map the authority structure of your team or department. For each type of decision (technical, hiring, resource allocation, process, quality, communication), identify: (1) Who currently has the authority to make this decision? (2) Is this authority attached to a person (because of their position) or to a function (because of their expertise)? (3) Could this authority be defined as a role that could be held by anyone with the relevant expertise? Draft role definitions for three authority domains in your team. For each role, specify: the role name, the decisions the role authorizes, the accountabilities the role carries, the information the role needs, and the criteria for who should hold the role. Share these drafts with your team and discuss: would this redistribution of authority improve decision speed and quality?

The underlying principle is straightforward: Authority flows from roles, not from hierarchy — anyone in a role has the authority that role requires. In traditional organizations, authority is personal — it belongs to the individual who holds a position in the hierarchy. A manager has authority because they are a manager, and they carry that authority across all the domains their position encompasses. In role-based authority, authority is functional — it belongs to the role, not the person. A person exercises authority when they are acting within a role they hold, and they hold no authority outside that role. This separation of person from role enables distributed authority: one person can hold multiple roles (and exercise different authorities in each), and authority can be reassigned by reassigning the role rather than reorganizing the hierarchy.