RACI Chart for Beginners | One Table for Who Does, Owns, Advises, and Is Informed

Project & Development

RACI Chart for Beginners | One Table for Who Does, Owns, Advises, and Is Informed

This beginner template helps team leads fill one RACI table with who's Responsible, Accountable, Consulted, and Informed for each task, so no one has to ask who's doing what. Across 4 pages, page 1 sets the purpose and maps who's involved by influence × interest, page 2 lines up the tasks and fills the table with R, A, C, I, page 3 checks the table for gaps and narrows the owner to one person, and page 4 shares the table and sets the next review date. The task board has 5 columns - not started, assigning, checking, in use, done - with 4 parent tasks and 3 subtasks each. A RACI table lists tasks in rows and people in columns, with exactly one A and at least one R per task; this example uses a website redesign, but the same steps fit any team task.

0 Likes 0 Copies Author: WeProcess
responsibility matrix RACI who does what project management for beginners
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode RACI Chart for Beginners | One Table for Who Does, Owns, Advises, and Is Informed

Whiteboard preview

① Purpose of the project and the spli... ② Place who's involved by influence ×... High influence × low interest: keep t... High influence × high interest: manag... Low influence × low interest: monitor Low influence × high interest: keep i... ③ R = Who does the work ④ A = Who owns the outcome ⑤ C = Who to consult ⑥ I = Who to inform ⑦ Put the tasks of ① in order, start ... ⑧ Task × person RACI table (rows from... ⑨ Check the RACI table of ⑧ (note whe... ⑩ Narrow the final owner to one perso... Has authority × doesn't know the work... Has authority × knows the work well No authority × doesn't know the work ... No authority × knows the work well ⑪ Share the table fixed in ⑧⑩ and how... ⑫ Log of changes to the split ⑬ Next review date and what triggers one RACI Chart for Be... How to use (all 4... Goal: doer & ... Purpose & dec... Problems & ga... Consulted & i... 1/4 Gather who's invo... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 List out the tasks ↙ 3/4 Project name and timelinee.g. Company website redesignTimeline: October to December (3 months) What's causing trouble nowe.g. Meetings stall on "who's doing this?"We argue every time over who does the final check. What the chart should achievee.g. Every task has one person who decides last, and everyone can say their own role. 縦軸: Influence (to... e.g. Finance (only approves the budget). Ask them before big decisions, so make them a C candidate. Add a column in ⑧ for any task where they're a C. e.g. Taylor (director), Morgan (lead). Add them as columns in ⑧ and make them A candidates. e.g. Sales in another department. Don't give them a column; only tell them as an I at big milestones like launch. e.g. Casey (design), Jordan (production). Add them as columns in ⑧ and make them R or C candidates. The person who actually does the work e.g. Jordan (production) is R for page production One or more per task; more than one is fine Decides how it's done and owns the result to the end e.g. Taylor (director) is A for deciding requirements Exactly one per task; can be the same person as R Asked for input before or during the work e.g. Ask Jordan (production) about buildability when making the design Two-way, so too many people slows the decision Told the decision or the result afterward e.g. Report to Taylor (director) once it's published One-way notice only; no input requested 1 Decidee.g. Decide the requirementsWrite the task that decides what to build and how far to go. 2 Designe.g. Make the designWrite the task that makes the draft or blueprint before building. 3 Builde.g. Build the pagesWrite the task that actually makes it real. 4 Checke.g. Check the contentWrite the task that checks for mistakes and the task that fixes them. 5 Delivere.g. Publish and reportWrite the task that hands it off and the task that announces it's done. e.g. Taylor (dire... e.g. Morgan (lead) e.g. Casey (design) e.g. Jordan (prod... Set requirements AApproves requirements RDrafts the plan CAsked about look and feel IHears the decision Design ISees the draft ADecides the draft RDesigns it CAsked about buildability Page production -Not involved RBuilds part of it CAsked about images RBuilds most of it Content check AFinal check ADecides on the check IHears the result CAsked about fixes Publish & report IHears the report A&RDecides to publish IHears the result RDoes the publishing 3/4 Narrow to one owner → 4/4 4/4 Review and keep i... What to check Example from ⑧ If left alone How to fix it Two A's A row has two or more A's e.g. Content check (Taylor and Morgan) No one is sure who decides last, so work stalls Narrow to one in ⑩; make the other R or I No A A row has no A at all e.g. Page production (two R's, no A) Problems go undecided and sit unresolved Make the person closest to the top-right of ⑩ the A One overloaded One column has both A's and R's piling up e.g. Morgan (3 A's and 3 R's) If that person is out, almost everything stalls Move some R's to someone else, or split the task in two Too many C/I A row has 3 or more C's and I's combined e.g. None right now. Add one here if it comes up Too much time spent consulting and updating Drop someone from I if reading the result later is enough 縦軸: Authority to ... Can be A, but put someone who knows it well as C for input. Pick A from here only if there's no one in the top right. The first pick for A. Choose just one from here. e.g. Make Taylor (director) the A for the content check, with Morgan (lead) doing the check as R. Don't make them A. Only make them I when they need to know the result. Don't make them A; make them R or C instead. e.g. Keep Jordan (production) as R for page production, and pick A from someone closer to the top right. 1 ShareShare the fixed table with everyoneEveryone says their own R, A, C, or I out loud to confirm it. 2 AskThe person who wants a change writes the task name and reasone.g. Jordan has more work now, so add a second R for page production. 3 A decidesThe task's A decides whether to change itWhen the A itself changes, the overall project owner decides. e.g. Taylor (director) 4 NotifyUpdate the table and log it in ⑫Also tell the C's and I's for the task that changed. Task changed Before → after Reason Decided by · date Log 1 e.g. Content check A: Taylor, Morgan→ A: Taylor Two A's stalled the check Taylor (director)Date: __/__ Log 2 e.g. Publish & report R: Morgan, Jordan→ R: Jordan Too much was on Morgan Morgan (lead)Date: __/__ Log 3 Write the next task you changed Write the role before and after Write the reason in one line Decided by: ____Date: __/__ Next review datee.g. First 10 minutes of the first Monday's meeting each monthNext: __/__ What triggers a reviewe.g. Someone joined or left, the workload grew, the same task stalled twice Splits not decided yete.g. No A yet for handling questions after launch. Decide at the next review. → 2/4 List out the tasks ↙ 3/4 Narrow to one owner → 4/4 Review and keep i...
100%

Drag to move, scroll to zoom

Task board contents

Not started 16 items

List who's involved
List out the tasks
Narrow to one owner
Review & keep fresh
Set goal & timeline
Place people in map
Confirm the roles
Order the tasks
Add people to table
Fill in each cell
Find gaps in table
Narrow owner to one
Even out overload
Share the table
Log the changes
Set next review

Assigning 0 items

Checking 0 items

In use 0 items

Done 0 items

← Back to templates