Session Brief: RAPID

Goal

Artifact: RAPID Role Map

Working Question

Which decision does the Decider make based on recommendation, Agreer approval and Performer feasibility?

Context

Question clear; stakeholder map; constraints; previous decisions; known conflicts between roles.

Setup

• Format: Method session
• Duration: 45-90 min workshop, plus async lead time of 1-2 weeks
• Mode: Workshop or async
• Participants: Recommender (develops recommendation, often driver function); Agreer (must agree, often compliance/legal/finance); Performer (implements decision, must confirm feasibility); Input (provides data or expertise, no veto); Decider (one person, final decision).
• Owner: Recommender (develops recommendation, often driver function)
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward RAPID Role Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

RAPID doc template with roles Recommend, Agree, Perform, Input, Decide; shared document area; pre-comment threads; decision deadline in calendar.

Preparation

Create RAPID doc, assign roles with names. Pre-read with recommendation at least 5 business days before meeting so Agreer and Performer have time to review.

Agenda

1. Phase 1: Clarify question and roles (30 min beforehand) Owner: Facilitator Action: Bound the question. Recommender, Agreer, Performer, Input, Decider with names. Clarify where Agreer veto right lies. Hint: Common error: Agreer role is assigned inflationarily, everyone gets veto. Agreer is only whoever must agree because of mandate (legal, compliance, finance budget). Output: RAPID Role Map

2. Phase 2: Recommender develops recommendation (1-2 weeks) Owner: Facilitator Action: Interview input people, analyze options, formulate one recommendation with rationale. Involve Agreer and Performer early. Hint: Recommender must bring Agreer and Performer into development, not only into meeting. Otherwise meeting collapses through late concerns. Output: Recommendation

3. Phase 3: Pre-read and comments (5 business days) Owner: Facilitator Action: Doc released. Agreer checks approvability. Performer checks feasibility. Inputs add data/expertise. Decider reads. Hint: Agreer does not stay silent. Anyone who does not agree comments in writing before meeting, otherwise it counts as agreement. Output: Decision Log

4. Phase 4: Decision meeting (45-90 min) Owner: Facilitator Action: Recommender presents recommendation. Agreer confirm or name obstacles. Performer confirms feasibility. Decider asks clarification questions and decides. Hint: If Agreer cannot agree: decision blocked, Recommender revises or escalates. Decider cannot overrule Agreer. Output: RAPID Role Map

5. Phase 5: Documentation and implementation (1-2 business days) Owner: Owner Action: Decision in doc, Performer takes over with implementation plan, owner and date. Informed are communicated. Hint: If Performer provides no plan after decision, Phase 3 failed. Feasibility was mandatory check. Output: Recommendation

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: RAPID Role Map

Closeout

• Update result artifact: RAPID Role Map
• Define location, version, and review recipients.
• Define owner, next step, and review date.

RAPID Role Map: RAPID

Working Question

Which decision does the Decider make based on recommendation, Agreer approval and Performer feasibility?

Context

Question clear; stakeholder map; constraints; previous decisions; known conflicts between roles.

Participants

• Owner: Recommender (develops recommendation, often driver function)
• Participants: Recommender (develops recommendation, often driver function); Agreer (must agree, often compliance/legal/finance); Performer (implements decision, must confirm feasibility); Input (provides data or expertise, no veto); Decider (one person, final decision).

Input

RAPID doc template with roles Recommend, Agree, Perform, Input, Decide; shared document area; pre-comment threads; decision deadline in calendar.

Template

RAPID Working Template

Goal

Clarify who recommends, agrees, performs, inputs, and decides.

Context

What decision needs to be made, and why now?

Input

• Decision question:
• Stakeholders:
• Constraints:
• Facts and assumptions:

Working area

• Recommend:
• Agree:
• Perform:
• Input:
• Decide:

Output artifacts

• RAPID role map:
• Recommendation:
• Decision log:

Open questions

• ...

Decision / next step

Owner, date, and success signal.

Completion Check

• RAPID Role Map is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision