Skip to content

Role Rights and Duties Matrix

Structuring tool — instantiates Institutional Rule–Role Stabilization

Lays out, office by office, who may do what, who owes what, and where two roles' authority collides — so obligations are predictable and turf conflicts surface before they fester.

When responsibilities live only in people's heads, two failures recur: gaps, where a task turns out to be nobody's job, and collisions, where two offices each believe a decision is theirs. Role Rights and Duties Matrix replaces that fog with an explicit map — for each office (not each person), its rights and powers, its duties, and its limits — crossed against the institution's decisions so overlaps and holes become visible. Its defining move is pairing the role map with an explicit conflict register: it doesn't just list what each office does, it names where two offices' authority genuinely collides and how the tie is broken. That combination is what turns role clarity from a wall poster into a working instrument, and — because it describes offices rather than incumbents — what lets authority stay stable as the people rotate through.

Example

A nonprofit that grew up around a charismatic founding executive director gains a newly assertive board, and the two keep colliding: who signs major contracts, who hires senior staff, who speaks for the organization in public. Each collision is handled ad hoc and leaves bruises. They build a role rights and duties matrix. For each class of decision they mark which office is empowered to act, which must be consulted, and which is merely informed; alongside it, each office's standing duties and hard limits.

The overlaps that caused the fights — hiring the deputy director, approving spending above a threshold — go into a conflict register with an explicit rule for each: who prevails, or how it escalates. The next contract doesn't reopen the who-decides fight, because the matrix already answered it. And when the founder eventually leaves, the office of executive director still has defined powers and limits, so the institution doesn't have to be reinvented around whoever comes next.

How it works

  • Enumerate offices, not people. Define the roles as standing positions, so the map survives whoever currently fills them.
  • Specify rights, duties, and limits. For each office, what it may do, what it owes, and — just as important — what it may not do.
  • Cross offices against decisions. Lay roles against decision types to expose both gaps (no owner) and overlaps (two owners).
  • Register and resolve collisions. Record each genuine overlap in a conflict register with an explicit tie-breaker — precedence, negotiation, or escalation — rather than leaving it to the next fight.

Tuning parameters

  • Granularity — broad role sketches versus decision-by-decision assignment. Fine grain removes ambiguity but multiplies upkeep and can create false precision.
  • Rights framework — simple responsible/consulted/informed labels versus a full rights–duties–powers–limits breakdown. Richer frameworks capture more but demand more literacy.
  • Conflict-resolution default — whether collisions resolve by hierarchy, by negotiation, or by escalation to a third office.
  • Deliberate overlap — hard, exclusive boundaries versus intentional redundancy. Some overlap adds resilience; too much reintroduces turf wars.
  • Coverage — only the contested roles versus the whole organization. Narrow coverage is cheap; broad coverage catches the gaps nobody thought to ask about.

When it helps, and when it misleads

Its strength is predictability and fewer turf wars: obligations become knowable in advance, gaps and double-ownership become visible on the page instead of in a crisis, and — by binding authority to the office rather than the occupant — the arrangement outlasts individual tenures. A clean matrix distinguishes having a right from having a power, which stops the common confusion of "I'm allowed to" with "I get to decide."[1]

Its failure modes are rigidity and gaming. Over-specified, a matrix hardens into bureaucracy that can't flex for a novel situation, and the seams between the cells become their own gaps. Because the boundaries are written down, ambitious actors negotiate their definitions — drawing the role to capture power or shed duties — so the map itself becomes contested terrain. The discipline is to treat the matrix as a living document paired with a conflict register that is actually consulted and revised, not a one-time drawing that ossifies the moment the marker caps.

How it implements the components

  • role_office_architecture — it is the structured definition of the offices, their powers, their duties, and their limits, held at the level of the role rather than the person.
  • role_conflict_register — it logs where offices' authority overlaps or collides and records the tie-breaking rule, converting recurring turf fights into a settled reference.

It does not establish that the offices exist in the first place (that's the Charter, Bylaws or Operating Agreement) or hand them off across turnover (that's the Succession and Stewardship Plan).

Notes

The matrix maps offices, not the people in them — that separation is exactly what lets authority survive turnover. But a matrix drawn once and never revisited drifts from how roles are actually played; the gap between the written role and the lived role is precisely what the Norm and Expectation Audit exists to surface, which is why the two work best in tandem.

References

[1] Wesley Hohfeld's analysis of jural relations distinguishes rights, duties, privileges, powers, liabilities, and immunities — clarifying, for instance, that holding a power (to change others' obligations) is not the same as holding a right. A rights-and-duties matrix is a practical descendant. ↩