Align authority with accountability
Compare responsibility against real decision rights and rebalance ownership, escalation, authority, or accountability so the system stops punishing powerless owners.
- Situation
- A person or team is being held responsible for outcomes they do not have enough authority, access, or influence to change.
- Goal
- Make accountable owners capable of changing the outcomes they are judged on.
- Do not use when
- the accountable owner already has authority and is avoiding use of it
- Primary owner
- engineering manager
- Roles involved
engineering managerteam leadproduct ownerdecision sponsorgovernance owneraffected team representatives
Context
The situation
Deciding whether to reach for this playbook: when it fits, and when it doesn't.
Use when
Conditions where this playbook is the right tool.
- Ownership and authority do not match
- Teams are accountable for cross-team outcomes they cannot influence
- Decision rights are unclear
- Governance asks teams to own risks without giving them control
Stakes
Why this matters
What this playbook protects against, and why skipping or half-running it tends to be expensive.
Accountability without authority creates learned helplessness, blame, and weak decision-making. Authority without accountability creates unmanaged risk.
Quality bar
What good looks like
The observable qualities of a team or system that is actually doing this well. Not just going through the motions.
Signs of the playbook done well
- Owners can name the decisions they control
- Escalation paths exist for decisions outside their authority
- Accountability is tied to influence, not wishful assignment
- Governance forums know who can accept trade-offs
- Teams stop being blamed for outcomes they cannot change
Preparation
Before you start
What you need available and true before running the procedure. Skipping this is the most common reason playbooks fail.
Inputs
Material you'll want to gather first.
- Ownership map
- Decision record
- RACI or DRI model
- Recent escalation history
- Team responsibilities
Prerequisites
Conditions that should be true for this to work.
- Named accountability area
- Willingness to inspect decision rights
- Leadership access for authority changes
Procedure
The procedure
Each step carries its purpose (why it exists), its actions (what you do), and its outputs (what you produce). Read the purpose. It's what keeps the step from degenerating into checklist theatre.
Name the accountable outcome
Clarify what the team or person is being judged on.
Actions
- Write the accountable outcome in plain language
- List the decisions and dependencies that affect it
- Identify who currently controls each decision
Outputs
- Accountability statement
- Decision influence map
Find authority gaps
Separate performance problems from structural control problems.
Actions
- Mark decisions the owner can make directly
- Mark decisions requiring approval or escalation
- Identify dependencies the owner cannot influence
Outputs
- Authority gap list
- Escalation map
Rebalance ownership or authority
Make accountability fair and operational.
Actions
- Move authority closer to the accountable owner where possible
- Move accountability to the real decision owner where needed
- Define escalation rules for shared decisions
Outputs
- Updated decision rights
- Rebalanced accountability map
Make the model visible
Ensure people use the new authority model during real work.
Actions
- Update ownership docs and decision records
- Review the next decision using the new model
- Check whether blocked decisions now route correctly
Outputs
- Updated ownership record
- Decision review note
Judgment
Judgment calls and pitfalls
The places where execution actually diverges: decisions that need thought, questions worth asking, and mistakes that recur regardless of good intent.
Decision points
Moments where judgment and trade-offs matter more than procedure.
- Should authority move to the owner, or accountability move to the authority holder?
- Which decisions require escalation?
- What can the owner decide without approval?
- How will shared accountability be handled?
Questions worth asking
Prompts to use on yourself, the team, or an AI assistant while running the procedure.
- Which outcomes is this team accountable for but unable to change?
- Who controls the decisions that affect this metric?
- Where does this decision record name responsibility but not authority?
Common mistakes
Patterns that surface across teams running this playbook.
- Telling teams to take ownership without changing decision rights
- Creating shared accountability with no escalation path
- Treating authority gaps as attitude problems
- Documenting a RACI that nobody uses
Warning signs you are doing it wrong
Signals that the playbook is being executed but not landing.
- The same decisions still block on the same people
- Owners still cannot accept trade-offs
- Teams are accountable for metrics controlled elsewhere
- Decision records still use passive language
Outcomes
Outcomes and signals
What should exist after the playbook runs, how you'll know it worked, and what to watch for over time.
Artifacts to produce
Durable outputs the playbook should leave behind.
- Accountability statement
- Decision influence map
- Authority gap list
- Updated decision rights
- Escalation map
Success signals
Observable changes that mean the playbook landed.
- Accountable owners can make or escalate required decisions
- Blocked decisions route faster
- Teams stop being blamed for unreachable outcomes
- Governance conversations name who can accept risk
Follow-up actions
Moves that keep the playbook's effects compounding after it finishes.
- Review authority gaps after major team changes
- Audit decision records for named owners
- Connect service ownership to decision rights
Metrics or signals to watch
Longer-horizon indicators that the underlying problem is receding.
- Blocked decision age
- Escalation frequency
- Decisions without named owner
- Accountability/authority mismatch count
AI impact
AI effects on this playbook
How AI-assisted and AI-driven workflows help execution, and the ways they can make it worse.
AI can help with
Where AI tooling genuinely reduces the cost of running this playbook well.
- Extracting decisions and owners from artifacts
- Summarizing escalation history
- Highlighting passive accountability language
- Drafting decision-rights maps
AI can make worse by
Distortions AI introduces that make the underlying problem harder to see.
- Creating ownership matrices that look complete but do not match operating reality
- Softening authority gaps into neutral coordination language
- Hiding unresolved accountability under polished summaries
Relationships
Connected playbooks
Failure modes this playbook tends to address, decisions behind the situation, red flags that motivate running it, and neighboring playbooks.