RACI Responsibility Matrix
Clarify project roles: Responsible, Accountable, Consulted, Informed. Map who does what on complex projects.
v3
Last updated: November 5, 2025
General
Engineering Manager
template
Loading...
Clarify project roles: Responsible, Accountable, Consulted, Informed. Map who does what on complex projects.
You are an engineering manager creating a RACI matrix for a project or initiative. Generate a comprehensive responsibility matrix: **Project Context:** - Project Name: [What is this project?] - Scope: [Team-level / Cross-team / Company-wide] - Duration: [How long will this take?] - Key Activities: [List major activities/tasks] **Generate a RACI matrix:** ## RACI Roles Explained **R - Responsible** (Can be multiple) - Does the actual work - Completes the task - "The doer" - Typically: Engineers, Designers, QA **A - Accountable** (Only 1 per activity) - Ultimately answerable for the outcome - Has veto power - "The buck stops here" - Typically: Engineering Manager, Tech Lead, Product Manager **C - Consulted** (Multiple) - Provides input before work is done - Subject matter experts - Two-way communication - Typically: Security, DevOps, Architects, Legal **I - Informed** (Multiple) - Told about progress/completion - One-way communication - No input required - Typically: Stakeholders, Leadership, Other Teams ## RACI Matrix Template **Project:** [Project Name] | Activity/Task | [Person 1] | [Person 2] | [Person 3] | [Team/Group] | Notes | |---------------|------------|------------|------------|--------------|-------| | [Activity 1] | A | R | C | I | [Why this assignment] | | [Activity 2] | A | R,R | C | I | [Multiple responsible] | | [Activity 3] | R | A | C,C | I | [Multiple consulted] | | [Activity 4] | R | A | C | I,I | [Multiple informed] | ## Key Activities to Map **Planning & Design:** - [ ] Requirements gathering - [ ] Architecture design - [ ] Technical design review - [ ] Security review - [ ] Project planning **Execution:** - [ ] Backend development - [ ] Frontend development - [ ] API development - [ ] Testing - [ ] Code review **Deployment & Operations:** - [ ] Infrastructure setup - [ ] Deployment - [ ] Monitoring setup - [ ] Documentation - [ ] Training **Communication:** - [ ] Stakeholder updates - [ ] Team standups - [ ] Status reports - [ ] Demo preparation ## RACI Best Practices โ **Only ONE Accountable per activity** - Multiple As = confusion โ **Multiple Responsible is OK** - Teams work together โ **Consulted early** - Don't consult at the last minute โ **Informed consistently** - Regular updates, not surprises โ **Document exceptions** - If someone is R and A, note why ## Common RACI Mistakes โ **Too many As** - "Who's really accountable?" becomes unclear โ **No A assigned** - Work falls through cracks โ **C treated as R** - Slows down work, creates bottlenecks โ **I not informed** - Creates confusion and resentment โ **Matrix too complex** - Hard to understand and maintain ## Responsibility Clarity Checklist Before starting work: - [ ] Everyone knows their R/A/C/I roles - [ ] Accountable person identified for each activity - [ ] Consulted roles know when they'll be asked - [ ] Informed roles know how they'll receive updates - [ ] Conflicts resolved (e.g., multiple As) ## Communication Plan **To Responsible:** - "You're responsible for [activity]. Here's what needs to be done: [details]" **To Accountable:** - "You're accountable for [activity]. [Person] is responsible. Check in [frequency]." **To Consulted:** - "We'll consult you on [aspect] before we proceed. Here's when: [timeline]" **To Informed:** - "We'll keep you informed via [channel] on [schedule]. Updates include: [what]" ## Project RACI Example **Project: New Authentication System** | Activity | Engineering Manager | Tech Lead | Backend Engineer | Frontend Engineer | Security | DevOps | Product | Leadership | |----------|-------------------|-----------|-----------------|-------------------|----------|--------|---------|------------| | Requirements | A | R | C | C | C | C | C | I | | Architecture | A | R | R | C | C | C | C | I | | Backend Dev | A | C | R | C | C | C | I | I | | Frontend Dev | A | C | C | R | C | C | I | I | | Security Review | A | C | C | C | R | C | I | I | | Infrastructure | A | C | I | I | C | R | I | I | | Testing | A | R | R | R | C | C | C | I | | Deployment | A | C | I | I | C | R | I | I | | Documentation | A | R | R | R | C | C | C | I | | Stakeholder Updates | A | R | I | I | I | I | C | C |
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...