A team can spend an hour improving a proposal and still leave unsure who can approve it. RAPID is a way to make those roles explicit before the discussion becomes another round of consultation.
Bain’s explanation of RAPID separates Recommend, Agree, Perform, Input and Decide. The acronym is a memory aid, not the chronological order in which every decision must proceed.
- Recommend: develop the proposal using the relevant facts and input.
- Agree: provide the formal agreement required within a defined area.
- Perform: carry out the chosen action.
- Input: contribute relevant knowledge or perspectives.
- Decide: make the final decision and commit to a course of action.
Apply it to one real choice
Imagine a team choosing a new appointment-booking tool. One person gathers requirements and recommends an option. Colleagues who handle bookings supply input. A relevant specialist provides any required agreement on a clearly specified issue. The authorised manager decides, and the implementation owner organises the rollout.
This is an illustrative arrangement, not a universal allocation. In a small team, one person may hold more than one role. What matters is that everyone knows which role they are exercising for this decision.
Define the boundary of agreement
“Everyone must agree” can quietly turn a role map into an unlimited veto. Specify whose formal agreement is needed and on what matter. Also establish what happens if an issue cannot be resolved before the decision date.
Write the decision itself in a sentence. “Choose the tool for a three-month pilot within the approved budget” is easier to assign than “sort out booking.” Include the person who will carry out the result early enough to identify practical constraints.
After the decision, record the choice, owner and next action. The role labels have done their job only when the team can move from discussion to an understood commitment. Adding an acronym to a meeting invitation is not the same as changing how the decision gets made.

