// description
RAPID assigns clear roles to people involved in a decision: Recommend (who proposes the decision), Agree (who has formal sign-off authority or veto power), Perform (who implements the decision once made), Input (who provides information but does not decide), and Decide (who makes the final call). The framework eliminates the ambiguity that causes decisions to stall when everyone assumes someone else is responsible.
// history
Bain & Company developed RAPID as part of their decision effectiveness consulting practice. The framework was published in a 2001 Harvard Business Review article by Paul Rogers and Marcia Blenko titled "Who Has the D? How Clear Decision Roles Enhance Organizational Performance." Bain found that organisations with clear decision roles made faster, better decisions and had higher employee engagement.
// example
A two-person creator business (creator + operations partner) keeps getting stuck on product pricing decisions. Every pricing choice triggers long back-and-forth email threads. They apply RAPID: the creator Recommends a price based on market research and positioning. The operations partner provides Input on cost and margin implications. The creator Decides (sole decision authority on product positioning). The operations partner Performs (updates the listing). No Agree role needed for routine pricing — they reserve that for major strategic decisions only. With roles clarified, pricing decisions that once took three days now take one conversation.
// katharyne's take
Even as a solo creator, RAPID is useful for structuring how you involve collaborators, VAs, or partners in decisions. The most common problem I see in small creator teams is unclear decision ownership — everyone has input, nobody has clear authority, so decisions stall indefinitely. Define who Decides on which categories of decision (product, pricing, partnerships, content, operations) before a decision is on the table. The conversation about roles is much easier when there's nothing at stake yet. By the time you're in a disagreement, it's too late to set up the framework cleanly.
// creative uses
- If you work with a VA or operations assistant on Etsy or KDP, build a one-page RAPID chart for your five most common decision types: listing copy updates, pricing changes, new product launches, ad spend adjustments, and customer service responses. Paste it into your shared Notion or Google Drive. Decision stalls drop immediately when everyone knows who has the D.
- Use RAPID to clarify your relationship with a business coach or mastermind. They are Input; you Decide. This sounds obvious but becomes important when coach recommendations conflict with your values or knowledge of your niche. You own the decision; they inform it.
- Apply RAPID to joint venture or collaboration decisions with other creators — co-bundles, affiliate partnerships, guest teaching. Who Recommends the terms? Who Decides? Who Performs (does the actual setup work)? Getting this clear before the project starts prevents the resentment that builds when workload and authority are both undefined.
// quick actions
- List every decision in your business that currently takes more than 48 hours to resolve. For each one, identify: is the delay because you don't have enough information (Input problem), because someone else needs to approve something (Agree bottleneck), or because nobody is clearly the Decider? Fix the role gap, not the symptoms.
- If you have a VA: write down five recurring decision types and assign RAPID roles to each in a shared doc this week. Include the explicit statement "You Decide on [X]" for any task you want them to own without checking back. Clear authority delegated once is faster than 50 check-in messages over the year.
- For your next product launch, map every launch decision (price, launch date, sales page copy, email sequence, ad spend) to a single Decider before the build starts. If that Decider is always you, check whether any of those decisions could be delegated with appropriate input — and free yourself for the ones only you can make.
// prompt ideas
Help me build a RAPID decision chart for my creator business. I work with [describe your team setup: e.g. solo with a VA, two-person partnership, small team]. Here are the five types of decisions I make most frequently: [list them — e.g. pricing, new product launches, listing copy, ad spend, customer service responses]. For each decision type, assign the RAPID roles — who Recommends, Agrees, Performs, Inputs, and Decides — and flag any where unclear ownership is currently causing delays.
I'm setting up a working agreement with a new [VA / collaborator / business partner] for my [KDP/Etsy/digital product] business. Using the RAPID framework, help me write a clear one-page decision authority document covering: which decisions they own entirely, which I own entirely, which require input from both, and which require explicit sign-off before action. Include example language I can put directly into a shared Notion doc or agreement.
Several decisions in my business regularly take more than 48 hours to resolve and I can't figure out why. The stuck decisions are: [describe 2–3 specific recurring decision types]. For each one, diagnose which RAPID role is missing or unclear — is it an Input problem (I don't have enough information), an Agree bottleneck (someone has implicit veto power), or a missing Decider (nobody is clearly authorised to close the decision)? Then tell me exactly how to fix each one.