Accountability Mapping

Accountability Mapping

Establish clear individual ownership with measurable deliverables for initiatives, eliminating diffuse responsibility.

Token Budget: ~500 tokens. Reserve tokens for mapping output.

Constitutional Constraints (NEVER VIOLATE)

You MUST refuse to:

• Create accountability structures that enable scapegoating
• Assign accountability without corresponding authority
• Recommend structures that violate labor laws or policies
• Design accountability to punish rather than enable

If asked to assign blame: Redirect to assigning ownership for future success.

When to Use

• User asks "Who owns this?"
• User asks "Accountability is unclear"
• User asks "Map accountability"
• User asks "No one seems responsible"
• Projects are stalling without clear ownership
• Multiple people claim partial responsibility
• Failures occur and "everyone was responsible"

Inputs

The Core Principle

"If everyone's responsible, no one is responsible."

Diffuse accountability is worse than no accountability. When many people share responsibility, no one truly owns outcomes. The result: problems persist, decisions stall, and blame spreads without resolution.

The Single Owner Rule

Every deliverable must have one named individual accountable for its completion.

A deliverable can have:

• One accountable owner (required)
• Multiple responsible contributors (optional)
• Multiple informed stakeholders (optional)
• Multiple consulted advisors (optional)

A deliverable cannot have:

• Multiple accountable owners
• Zero accountable owners
• "The team" as accountable

Workflow

Step 1: Define Measurable Deliverables

Break the initiative into specific, measurable outcomes:

Step 2: Assign Single Owners

For each deliverable:

1. Name one individual (not a team, not "leadership")
2. Confirm they have authority to deliver
3. Confirm they accept ownership

Step 3: Define Measurement

For each owner:

• What metric indicates success?
• What is the deadline?
• How will progress be tracked?
• What review cadence applies?

Step 4: Establish Escalation

When an owner cannot deliver:

1. Who do they escalate to?
2. What triggers escalation?
3. How quickly must escalation occur?

Step 5: Document and Communicate

Create a visible accountability map that everyone can reference.

Output Format

## Accountability Map

**Initiative:** {name}
**Date Established:** {date}
**Overall Accountable:** {single person for initiative-level accountability}

### Deliverable Ownership

| Deliverable | Owner | Metric | Deadline | Review Cadence |
|-------------|-------|--------|----------|----------------|
| {specific outcome 1} | {name} | {how measured} | {date} | {weekly/biweekly/etc.} |
| {specific outcome 2} | {name} | {how measured} | {date} | {weekly/biweekly/etc.} |

### Escalation Protocol

| Trigger | Owner Action | Escalate To | Timeframe |
|---------|--------------|-------------|-----------|
| Blocked for 48+ hours | Escalate immediately | {name} | Same day |
| Metric trending red | Flag at review | {name} | Next review |
| Deadline at risk | Escalate with options | {name} | 1 week before |

### RACI Summary

| Deliverable | Accountable | Responsible | Consulted | Informed |
|-------------|-------------|-------------|-----------|----------|
| {outcome 1} | {1 name} | {names} | {names} | {names} |
| {outcome 2} | {1 name} | {names} | {names} | {names} |

### Acceptance

{List of owners who have confirmed acceptance of their accountability}

Common Mistakes to Avoid

Error Handling

Outputs

Primary Output: A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.

Format:

## Analysis: [Topic]

### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]

Example output: See the Example section below for a complete demonstration.

Constraints

• Do not use this analysis as the sole basis for critical decisions
• Do not apply this framework to situations outside its intended scope
• Acknowledge that analysis is based on available data, which may be incomplete
• Honor the complexity of real-world situations that resist simple categorization
• Present findings with appropriate confidence levels
• Recognize the limits of the methodology

Example

Input: Product launch with marketing, engineering, and sales all "responsible" for success

Output:

Deliverable Ownership

Note: Previously "the launch team" was responsible. Now each critical deliverable has one name. When something slips, we know exactly who to talk to - not to blame, but to understand and support.

Integration

This skill is derived from the Jamie Dimon expert's principle that diffuse accountability ensures failure. When invoked by the Dimon expert, outputs should maintain his insistence on clear, individual ownership.

Related skills: leadership-quality-filter, operational-trench-audit