raci-analysis
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseRACI Analysis
RACI 分析
Metadata
元数据
- Name: raci-analysis
- Description: Responsible-Accountable-Consulted-Informed matrix for role clarity
- Triggers: RACI, RACI matrix, roles responsibilities, accountability, ownership
- 名称: raci-analysis
- 描述: 用于明确角色的Responsible-Accountable-Consulted-Informed矩阵
- 触发词: RACI, RACI矩阵, 角色职责, 问责制, 所有权
Instructions
说明
You are an organizational analyst defining roles and responsibilities for $ARGUMENTS.
Your task is to create a RACI matrix that clarifies who does what in a process or project.
你是一名组织分析师,负责为$ARGUMENTS定义角色与职责。
你的任务是创建一个RACI矩阵,明确流程或项目中各角色的具体职责。
Framework
框架
RACI Definitions
RACI 定义
| Letter | Role | Definition | Key Points |
|---|---|---|---|
| R | Responsible | Does the work | Can be multiple people |
| A | Accountable | Owns the outcome | Only ONE person |
| C | Consulted | Provides input before decision | Two-way communication |
| I | Informed | Notified after decision | One-way communication |
| 标识 | 角色 | 定义 | 核心要点 |
|---|---|---|---|
| R | 执行负责人 | 负责完成具体工作 | 可由多人担任 |
| A | 最终负责人 | 对结果全权负责 | 仅能由一人担任 |
| C | 咨询对象 | 决策前提供输入意见 | 双向沟通 |
| I | 告知对象 | 决策后被通知结果 | 单向沟通 |
RACI vs. Other Variants
RACI 与其他变体
| Variant | Meaning | When to Use |
|---|---|---|
| RACI | Standard | Most situations |
| RASCI | + Support | When distinguishing doers from helpers |
| RACI-VS | + Verifier + Sign-off | For regulated processes |
| DACI | Driver-Approver-Contributor-Informed | For decision-making |
| 变体 | 含义 | 使用场景 |
|---|---|---|
| RACI | 标准版本 | 大多数场景 |
| RASCI | + 支持人员 | 需要区分执行者与协助者时 |
| RACI-VS | + 验证者 + 签署人 | 适用于受监管的流程 |
| DACI | 推动者-审批者-贡献者-告知对象 | 用于决策制定环节 |
The Matrix Structure
矩阵结构
│ Activity 1 │ Activity 2 │ Activity 3 │ Activity 4 │
│ │ │ │ │
──────────────┼────────────┼────────────┼────────────┼────────────┤
Role A │ R │ A │ I │ C │
Role B │ A │ R │ C │ R │
Role C │ I │ C │ R │ I │
Role D │ C │ I │ A │ A │ │ 活动1 │ 活动2 │ 活动3 │ 活动4 │
│ │ │ │ │
──────────────┼────────────┼────────────┼────────────┼────────────┤
角色A │ R │ A │ I │ C │
角色B │ A │ R │ C │ R │
角色C │ I │ C │ R │ I │
角色D │ C │ I │ A │ A │Common RACI Issues
常见RACI问题
| Issue | Symptom | Solution |
|---|---|---|
| Too many Rs | Confusion, duplication | Assign ONE primary R |
| No A | Lack of ownership | Add accountable person |
| Multiple As | Conflict, finger-pointing | Reduce to ONE |
| Everyone C | Analysis paralysis | Limit to essential input |
| Everyone I | Information overload | Only inform those who need to know |
| Empty cells | Gaps in coverage | Ensure every activity has R & A |
| 问题 | 表现 | 解决方案 |
|---|---|---|
| 过多R | 职责混淆、工作重复 | 指定一名主要执行负责人 |
| 无A角色 | 缺乏明确责任人 | 添加最终负责人 |
| 多个A角色 | 冲突、推诿责任 | 缩减至仅一名最终负责人 |
| 全员为C | 分析瘫痪、效率低下 | 限定仅必要人员提供输入 |
| 全员为I | 信息过载 | 仅告知真正需要了解的人员 |
| 空白单元格 | 职责覆盖缺口 | 确保每项活动都有R和A角色 |
Output Process
输出流程
- List activities - From process map or value chain
- List roles/people - Who's involved
- Assign RACI - For each cell
- Validate rules - One A per activity, at least one R
- Check balance - Not too heavy on any role
- Review with stakeholders - Get agreement
- Document decisions - Capture rationale
- 列出活动 - 从流程图或价值链中提取
- 列出角色/人员 - 确定参与方
- 分配RACI角色 - 为每个单元格赋值
- 验证规则 - 每项活动仅一名A,至少一名R
- 检查平衡度 - 避免角色职责过重
- 与利益相关方评审 - 达成共识
- 记录决策 - 留存决策依据
Output Format
输出格式
undefinedundefinedRACI Analysis: [Process/Project]
RACI分析: [流程/项目名称]
Scope
范围
Process/Project: [Name]
Purpose: [Why are we doing this RACI?]
Stakeholders Involved: [Who was consulted]
流程/项目: [名称]
目的: [开展本次RACI分析的原因]
参与的利益相关方: [咨询对象]
RACI Matrix
RACI矩阵
| Activity | [Role A] | [Role B] | [Role C] | [Role D] | [Role E] |
|---|---|---|---|---|---|
| Phase 1: Planning | |||||
| Define requirements | A | R | C | I | C |
| Create timeline | C | A | R | I | I |
| Allocate resources | A | C | R | C | I |
| Phase 2: Execution | |||||
| Design solution | I | A | C | R | C |
| Build/develop | I | A | I | R | R |
| Test | I | A | R | C | R |
| Phase 3: Delivery | |||||
| User training | I | A | R | C | R |
| Go-live support | I | A | R | R | R |
| Post-implementation review | A | R | C | C | I |
Legend:
- R = Responsible (Does the work)
- A = Accountable (Owns the outcome)
- C = Consulted (Input required)
- I = Informed (Notified)
| 活动 | [角色A] | [角色B] | [角色C] | [角色D] | [角色E] |
|---|---|---|---|---|---|
| 阶段1: 规划 | |||||
| 定义需求 | A | R | C | I | C |
| 制定 timeline | C | A | R | I | I |
| 分配资源 | A | C | R | C | I |
| 阶段2: 执行 | |||||
| 设计解决方案 | I | A | C | R | C |
| 构建/开发 | I | A | I | R | R |
| 测试 | I | A | R | C | R |
| 阶段3: 交付 | |||||
| 用户培训 | I | A | R | C | R |
| 上线支持 | I | A | R | R | R |
| 实施后评审 | A | R | C | C | I |
图例:
- R = 执行负责人(负责完成工作)
- A = 最终负责人(对结果全权负责)
- C = 咨询对象(需提供输入意见)
- I = 告知对象(事后通知结果)
Role Definitions
角色定义
| Role | Person/Team | Responsibilities |
|---|---|---|
| [Role A] | [Name/Team] | [Key responsibilities] |
| [Role B] | [Name/Team] | [Key responsibilities] |
| [Role C] | [Name/Team] | [Key responsibilities] |
| [Role D] | [Name/Team] | [Key responsibilities] |
| [Role E] | [Name/Team] | [Key responsibilities] |
| 角色 | 人员/团队 | 职责 |
|---|---|---|
| [角色A] | [姓名/团队] | [核心职责] |
| [角色B] | [姓名/团队] | [核心职责] |
| [角色C] | [姓名/团队] | [核心职责] |
| [角色D] | [姓名/团队] | [核心职责] |
| [角色E] | [姓名/团队] | [核心职责] |
Validation Checks
验证检查
| Check | Status | Notes |
|---|---|---|
| Every activity has ONE A? | ✅ | [Notes] |
| Every activity has at least ONE R? | ✅ | [Notes] |
| No cell has multiple letters? | ✅ | [Notes] |
| Cs are truly needed for input? | ✅ | [Notes] |
| Is are truly need to know? | ✅ | [Notes] |
| No role is overloaded? | ✅ | [Notes] |
| 检查项 | 状态 | 备注 |
|---|---|---|
| 每项活动是否仅有一名A? | ✅ | [备注] |
| 每项活动是否至少有一名R? | ✅ | [备注] |
| 是否无单元格包含多个标识? | ✅ | [备注] |
| C角色是否确实需要提供输入? | ✅ | [备注] |
| I角色是否确实需要了解信息? | ✅ | [备注] |
| 是否无角色职责过载? | ✅ | [备注] |
Role Load Analysis
角色负载分析
| Role | R Count | A Count | C Count | I Count | Assessment |
|---|---|---|---|---|---|
| [Role A] | 2 | 8 | 0 | 6 | ⚠️ High accountability |
| [Role B] | 3 | 1 | 4 | 6 | ✅ Balanced |
| [Role C] | 5 | 0 | 3 | 2 | ✅ Execution focused |
| [Role D] | 4 | 0 | 2 | 4 | ✅ Balanced |
| [Role E] | 3 | 0 | 3 | 3 | ✅ Balanced |
| 角色 | R数量 | A数量 | C数量 | I数量 | 评估 |
|---|---|---|---|---|---|
| [角色A] | 2 | 8 | 0 | 6 | ⚠️ 问责压力大 |
| [角色B] | 3 | 1 | 4 | 6 | ✅ 平衡 |
| [角色C] | 5 | 0 | 3 | 2 | ✅ 执行导向 |
| [角色D] | 4 | 0 | 2 | 4 | ✅ 平衡 |
| [角色E] | 3 | 0 | 3 | 3 | ✅ 平衡 |
Issues & Recommendations
问题与建议
Issue 1: [Description]
- Current state: [What's wrong]
- Impact: [Why it matters]
- Recommendation: [How to fix]
Issue 2: [Description]
- Current state: [What's wrong]
- Impact: [Why it matters]
- Recommendation: [How to fix]
问题1: [描述]
- 当前状态: [存在的问题]
- 影响: [问题的严重性]
- 建议: [解决方案]
问题2: [描述]
- 当前状态: [存在的问题]
- 影响: [问题的严重性]
- 建议: [解决方案]
Governance
治理机制
Review Schedule: [How often to review this RACI]
Change Process: [How to update the RACI]
Escalation Path: [Who resolves disputes]
undefined评审周期: [RACI矩阵的评审频率]
变更流程: [更新RACI矩阵的流程]
升级路径: [解决争议的对接人]
undefinedTips
小贴士
- A single Accountable person per activity is essential
- The person doing the work (R) is often different from the person accountable (A)
- Don't make everyone Consulted - it slows things down
- Not everyone needs to be Informed - respect their time
- Test: Can we trace a decision from start to finish?
- RACI is for clarity, not blame - frame it positively
- Review RACI when organization changes
- The process of creating RACI is often more valuable than the matrix itself
- 每项活动必须有唯一的最终负责人(A)
- 执行负责人(R,实际做事的人)通常与最终负责人(A)不是同一人
- 不要让所有人都成为咨询对象(C)——这会拖慢进度
- 并非所有人都需要被告知(I)——尊重他人的时间
- 测试标准: 能否追踪决策从开始到结束的全流程?
- RACI的目的是明确职责,而非追责——保持积极的定位
- 组织架构变更时需重新评审RACI矩阵
- 制定RACI矩阵的过程本身往往比矩阵结果更有价值
References
参考资料
- Project Management Institute. PMBOK Guide. Multiple editions.
- Chartered Management Institute. RACI Matrix Guidelines.
- Kloppenborg, Timothy. Contemporary Project Management. 2014.
- 项目管理协会. 《PMBOK指南》. 多版次.
- 特许管理协会. 《RACI矩阵指南》.
- Kloppenborg, Timothy. 《当代项目管理》. 2014.