Every MBA team eventually discovers the same two failure modes: work nobody did because everyone thought someone else owned it, and work two people did twice because neither knew about the other. RACI exists to kill both—and the student version takes ten minutes.
The four letters, translated for student teams
- R — Responsible. Does the work. The person building the model, writing the section, making the slides.
- A — Accountable. Answers for the outcome and breaks ties. Exactly one per deliverable, no exceptions.
- C — Consulted. Gives input before the work is done—the teammate whose analysis feeds yours.
- I — Informed. Told when it's done. Everyone else.
On a five-person team, R and A are often the same person. That's not a violation; that's the point. The letters exist to force one question per deliverable: who owns this?
Build it in ten minutes
At your kickoff meeting, list the deliverables down the left side of a table—not tasks, deliverables. "Financial model," "market sizing," "final deck," "presentation dry run." Five to ten rows for most projects.
Put names across the top. Then fill in letters, following two rules:
- Every row has exactly one A. Two As means a negotiation during crunch week. Zero As means a gap you'll find the night before.
- No row has more than two Rs. Three people "responsible" for one section means merge conflicts, style clashes, and a coordination meeting you didn't budget for.
If a row fights those rules, the row is too big. Split "final deck" into "storyline," "slides," and "appendix" and the letters get easy.
The rows student teams forget
Three deliverables almost never make the list, and cause a disproportionate share of the pain:
- Integration. Someone must own merging five people's sections into one coherent document. This is real work—typically several hours—and if it has no owner it lands on whoever cares most, at 2am.
- The dry run. Who schedules it, who times it, who collects feedback.
- Submission. One named person uploads the file, checks the formatting requirements, and confirms it went through. Teams have lost letter grades to this row not existing.
Integration in particular is one of a handful of standing roles worth naming once for the whole term rather than re-deciding every deliverable; MBA Lab's team charter builder has a dedicated Integrator role for exactly this.
Keep it alive
A RACI that lives in a doc nobody reopens is a kickoff artifact, not a working agreement. Put the owner's name next to each deliverable in whatever tool tracks your work—if your team uses MBA Lab, the assignee field is your R, and the due date makes drift visible early.
Revisit the table once, at the project midpoint. Recruiting season, a brutal midterm, a teammate's case competition—loads change, and a five-minute rebalance beats a resentment that compounds silently to the finish.