CONTEXT · CHOICES · CONSEQUENCES
Learning objective: Create a small operating system that improves other people's work without making every decision depend on you.
Source status: Course-authored teaching based on a reported topic map. Linked references describe the versions taught here. Original workshop diagrams, homework, and organization-specific procedures were not supplied.
Two people believe the other owns a launch decision. RACI assigns task responsibilities: Responsible does the work; Accountable owns the outcome; Consulted contributes before action; Informed receives updates. Prefer a clear accountable owner per deliverable. RAPID, from Bain, distinguishes Recommend, Agree, Perform, Input, and Decide for a decision. These roles do not describe a mandatory sequence, and the Agree role should not turn every participant into a veto holder.
For a launch, name who recommends readiness, who decides go/no-go, what approvals are actually required, who supplies evidence, and who executes. A task matrix alone does not settle a disputed decision right. Ask affected people whether the arrangement is workable.
When a commitment slips, start with evidence and context: Was the result clear? Were time, access, and dependencies realistic? Does the person know how to do this particular task? Training helps a skill gap; it cannot fix missing access. A motivation concern needs a conversation about interests, incentives, confidence, and conditions. Avoid treating skill and willingness as the only possible causes.
Limit: formal charts can add friction to simple work. Use them when ambiguity has a real cost, then revisit them when the work changes.
A project keeps missing its release forecast. Write a one-on-one opening, two diagnostic questions, and a small operating change. Identify the launch decision owner and a review date.
Write your response before comparing it with the example.
0/7000
What is the best purpose for a one-on-one?
Which question is RACI designed to help answer?