Responsibility Chart
- Typical duration:
- 30m
A visual chart that assigns clear ownership for each key deliverable or workstream in a project, ensuring nothing falls through the cracks.
Purpose
The Responsibility Chart provides a clear, visual mapping of who owns which deliverable, workstream, or area of a project. Unlike a full RACI matrix, it focuses primarily on ownership (who is the single person on the hook) and support (who helps), making it simpler and faster to create.
At a glance
| Attribute | Detail |
|---|---|
| Group size | 3–12 participants |
| Duration | 30 minutes |
| Difficulty | Easy |
| Facilitation style | Collaborative, structured |
| Setting | In-person or remote |
How to run
- List deliverables (5 min): Identify all major deliverables, milestones, or workstreams.
- List team members (2 min): Name the people or roles involved.
- Assign owners (15 min): For each deliverable, assign one owner (primary responsibility) and optionally a supporter. Discuss disagreements openly.
- Check balance (5 min): Ensure no one is overloaded and no deliverable is unowned.
- Post visibly (3 min): Make the chart a living document visible to the whole team.
Materials needed
- Whiteboard, flip chart, or digital spreadsheet
- Deliverable list
- Team member list
Pitfalls & common mistakes
- Shared ownership: When two people "co-own" something, nobody truly owns it. Insist on one owner.
- Too detailed: Keep deliverables at a level where ownership is meaningful.
- Set and forget: Review the chart at regular intervals.
- Missing people: Ensure everyone who will be affected is represented.
Inclusion & accessibility
- Use large, clear text for wall-posted charts.
- Discuss assignments openly so everyone can voice concerns.
- Digital format ensures remote team members can access it.
Variations
- Swim Lane Chart: Visual variation using horizontal lanes per person.
- RACI Extension: Evolve into a full RACI if more granularity is needed.
- Color-coded Chart: Use colours per team or department.
When NOT to use this
- When ownership is already clear and documented.
- For a one-person project.
- When the team structure is too fluid for fixed assignments.
Source & further reading
- Richard Beckhard & Reuben T. Harris, *Organizational Transitions* (1987)
- Project Management Institute (PMI)
- MindTools: Responsibility Assignment
Turn the building blocks into an agenda
Create the day, drag the blocks into the order you have in mind, and let the times work themselves out. Or describe what you are planning to your AI and let it write the first draft.
Try it free for 14 days