Decision Rights at the Cross-Functional Interface

The problem to solve

At an interface, multiple functions often have legitimate expertise and risk exposure. Confusion begins when input is mistaken for authority, a decision is never named, or the organization has not stated what requires escalation.

The symptom may look like poor collaboration. The underlying condition is often a missing agreement about how the work moves and who has the right to decide when perspectives differ.

The Work & Theory principle

Design makes coordination visible. Effective decision rights do not remove consultation; they distinguish contribution, accountability, and escalation so that consultation can lead somewhere.

Diagnostic questions

Use a recent decision with a visible delay or rework cycle.

• What specific decision is being made—not the entire project?
• What outcome or customer promise does it affect?
• Who is accountable for deciding after input is gathered?
• Whose input is necessary because of expertise, risk, or execution responsibility?
• What information must be available before the decision is made?
• What condition should trigger escalation rather than routine disagreement?
• How will the decision and rationale be communicated to affected teams?

Practical next actions

Run a 60–90 minute working session with the roles closest to the decision. Map the current handoff, name the decision, and write a decision-right statement before discussing technology, meeting cadence, or structural changes.

Test the statement on the next real decision. If people still escalate, examine whether the guardrails, authority, or information flow remain incomplete.

Related artifact and pathway

Capture repeatable decisions in the Organization Blueprint and connect role-level authority to Performance Contracts. The Role Clarity and Decision Rights path is designed for leaders who need to move from symptoms to a working agreement.