RAPID + Five-Day Escalation
Name one decision-maker and put a clock on every unresolved decision
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 90%
A two-part decision-making system for complex, interconnected organizations. RAPID assigns explicit roles to every decision so there is a single accountable decision-maker, while the five-day alignment rule forces any decision that a manager hasn't resolved to escalate to the next level within five days. Together they act as 'fuses' that keep a many-marketplace ecosystem from stalling.
Origin
Long-standing practices at LinkedIn, described by VP of Product Hari Srinivasan as tools for running an ecosystem with multiple marketplaces and business models. RAPID is a widely-used variant of the RACI/RAPID decision-rights family (popularized by Bain).
Core principles
- 01More ties in the ecosystem require a stronger decision mechanism, not more consensus
- 02Clarity comes from a single named decision-maker, not a committee
- 03Unresolved decisions should escalate on a fixed clock, not linger
- 04Speed of decision protects the whole system from gridlock
How to run it
- 1
Assign RAPID roles to the decision
For each decision, list who Recommends it, who must Agree, who provides Input, and — most importantly — the single person who Decides (the D). Put one name on the decision line.
Pro tip The single name on the decision line is the highest-leverage part; it is what lets you get a decision quickly.
Watch out Spreading the decision across several 'deciders' recreates the gridlock the tool exists to remove.
- 2
Escalate communication channels fast
Use a personal escalation ladder: if a decision has gone three back-and-forths in email, move to a phone call; if the call passes 20 minutes, write to the named decision-maker and let them decide.
Pro tip Aim to reach a decision within roughly an hour by climbing channels quickly.
- 3
Apply the five-day alignment rule
Hold managers accountable that any issue not escalated and solved within five days moves up to the next level of leadership, so nothing sits blocked indefinitely.
Pro tip The rule puts the clock on the manager to get the team unblocked, not on the individual contributor.
In the wild
LinkedIn runs a hiring marketplace, a learning marketplace, an engagement/feed ecosystem, plus marketing and premium businesses; decisions cut across all of them, creating many potential tiebreak points.
→ RAPID and the five-day rule give the org fast, clear tiebreakers so the interconnected ecosystem keeps moving instead of stalling on ambiguous ownership.
Common mistakes
Leaving the decision-maker ambiguous
Without a single named D, cross-marketplace decisions stall because no one knows who can actually make the call.
Letting blocked issues linger without a deadline
Absent a fixed escalation clock, unresolved decisions sit for weeks; the five-day rule forces them upward before they rot.
Is it for you?
Best for
Product and operations leaders running large, matrixed organizations with many interdependent teams and unclear decision ownership
Not ideal for
Small teams or single-thread projects where ownership is already obvious and the process would be overhead
From the transcript
“we have something called Rapid which is a really easy way to know who the decision-maker is”
“if you had three back and forth in an email, you got to pick up the phone. And if you've been on the phone for…”
“the D stands for decisions, but the R is for who's recommending it, the A is for who has to agree, the I is for…”
“you should hold your managers, uh you know, accountable that in 5 days if someone has something that they haven't been able to escalate and…”
From the episode
LinkedIn’s product evolution and the art of building complex systems
Hari Srinivasan (LinkedIn)