Use this when you need to facilitate a meeting that isn't a standard ceremony (retro, IPM, demo) and want a structured plan with timed agenda, facilitator cues, discussion prompts, and decision-capture templates.
Process
Step 1: Gather meeting context
Ask the facilitator:
- What is the purpose of this meeting? (What decision, alignment, or output do you need by the end?)
- Who will attend? (Roles and count — e.g., "3 engineers, 1 PM, 1 designer, 1 client stakeholder.")
- How long is the session? (30 min, 60 min, 90 min, half-day?)
- Is there pre-work or context attendees should review beforehand?
- Are there any known tensions, blockers, or sensitive topics to navigate?
Step 2: Design the session structure
Based on the inputs, design a session plan using these building blocks:
| Block type | Duration | When to use |
|---|---|---|
| Opening frame | 2-3 min | Always — state Point A (where we are) and Point B (where we need to get) |
| Context share | 5-10 min | When attendees need shared understanding before discussion |
| Silent generation | 3-5 min | Before any brainstorming — prevents anchoring on the first idea |
| Small group work | 10-20 min | Groups of 3 for ideation, problem framing, or design exploration |
| Full group discussion | 10-20 min | Synthesis, debate, and decision-making |
| Dot-voting / prioritization | 5 min | When you need to surface real priorities without social pressure |
| Decision capture | 3-5 min | After each decision point — state it, confirm agreement, record it |
| Parking lot review | 3-5 min | Near the end — review parked items, assign follow-ups |
| Closing round | 3-5 min | Always — each person shares one takeaway |
Step 2b: Prepare the space and opening energy
Before scripting the session, consider three additional dimensions:
Space design: How the room is arranged shapes what's possible.
- Circle = equal power (good for retros, check-ins, consensus)
- Breakout clusters (3-5 people) = lower social pressure, faster generation
- Gallery walk = pin work around the room, let people move and annotate (movement activates different thinking)
- Materials on the table (Post-its, markers, paper) = "you will contribute." Nothing on the table = "you will listen."
- For remote: gallery view = circle. Shared Miro/FigJam = materials on the table. Chat open = permission to react.
Warm-up selection: If the session is 60+ minutes or the group needs to shift energy, include a 2-5 minute warm-up before the first content block. Match to the session need:
- Need focus? → One-Word Check-In (2 min, any size): each person shares one word describing how they arrive
- Need energy? → Shake It Out (2 min, any size): shake each limb 8x, then 4x, 2x, 1x -- fast, loud, resets the room
- Need connection? → Commonalities (5 min, pairs): find 3 non-obvious things in common with a partner
- Need creativity? → Word Association Chain (3 min, circle): rapid-fire word association, no filtering
Related skills: See
/workshop-warm-upfor the full warm-up library with facilitation scripts.
Energy management: Build at least one energy checkpoint into sessions over 60 minutes. Watch for: phone checking (disengage or reformat), one person dominating (create structure for other voices), energy drop after lunch (standing activity or medium change). If the room's energy doesn't match what the next activity needs, pause and adjust before proceeding.
Step 3: Generate the facilitation script
Produce the script in this format:
# (Meeting title)
**Date:** (date)
**Duration:** (total time)
**Goal:** By the end of this session, we will have (specific outcome).
**Attendees:** (list)
---
## Agenda
### 1. Opening (X min)
**Facilitator says:** "(Opening frame — Point A to Point B)"
### 2. (Activity name) (X min)
**Purpose:** (What this block achieves)
**Facilitator says:** "(Prompt or instruction to the group)"
**Facilitator watches for:** (Dynamics to manage — e.g., "one person dominating," "tangents")
### 3. (Activity name) (X min)
...
### N. Closing round (3 min)
**Facilitator says:** "Let's go around — one thing you're taking away from this session."
---
## Decisions made
- (Capture during session)
## Action items
| Action | Owner | Due |
|--------|-------|-----|
| | | |
## Parking lot
- (Items tabled for later)
Step 4: Review and adjust
Present the script and ask:
- Does the flow make sense for this group?
- Is the time allocation realistic? (Common mistake: too much context, not enough discussion.)
- Are there any dynamics I should plan for? (Vocal skeptic, quiet stakeholder, remote participants?)
- Do you want a co-facilitator role defined?
Adjust based on feedback.
Distributed cognition checklist
Before finalizing any facilitation script, verify you are leveraging distributed cognition effectively:
- Modular information: Are participants externalizing ideas onto movable artifacts (sticky notes, index cards, digital stickies) rather than just talking?
- Visual modeling: Are you using sketching, mindmaps, storyboards, or diagrams to make relationships visible?
- Shared artifacts: Will the session produce something the team can point to and think with together after the meeting?
- Prototype where possible: For solution-oriented sessions, can participants build or sketch something tangible to evaluate, rather than debating abstractions?
If a session is purely verbal discussion with no externalized artifacts, add at least one distributed cognition technique. Thinking with your brain and objects in the world is not a better way to think -- it's the natural way.
Output location
Present the facilitation script as formatted text in the conversation for the facilitator to copy into their notes or shared doc.
Example Output
Input
- Meeting purpose: Decide whether to build a native mobile app or invest in a progressive web app (PWA) for Cartwell's upcoming B2C launch — need a clear go/no-go direction with rationale documented
- Attendees: 2 senior engineers, 1 mobile engineer, 1 product manager (Renata Osei), 1 UX designer, 1 VP of Marketing (external to the product team) — 6 people total
- Session length: 90 minutes
- Pre-work: Attendees have read a 2-page technical brief comparing native vs. PWA on performance, cost, and timeline; VP of Marketing has shared Q3 customer acquisition targets
- Known tensions: The mobile engineer strongly prefers native (has been vocal about this); VP of Marketing doesn't understand the technical tradeoffs and may push for whichever option "sounds faster"; engineers and marketing have not been in the same room on this topic before
Output (abbreviated)
Cartwell Mobile Platform Decision Session
Date: TBD Duration: 90 minutes Goal: By the end of this session, we will have selected either native app or PWA as Cartwell's B2C launch platform, documented the deciding criteria, and assigned next steps. Attendees: Renata Osei (PM, facilitator), 2 senior engineers, 1 mobile engineer, 1 UX designer, 1 VP of Marketing
Pre-Session Setup
Space design: Arrange tables in a breakout cluster of 6 (one round or U-shape). Place Post-its, markers, and printed evaluation criteria cards at each seat — the signal is "you will contribute, not just listen." If any attendees are remote, open Miro board with sticky note zones pre-labeled; gallery view on; chat open.
Materials to prepare:
- 2-column comparison poster (Native vs. PWA) hung or projected — visible the whole session
- Pre-printed "criteria card" per person (Performance / Time to Launch / Cost / Reach / Maintainability)
- Dot stickers for voting (5 per person)
- Decision capture sheet (shared doc or physical flip chart at front)
Agenda
1. Opening Frame (3 min)
Facilitator says: "Thanks for being here. Here's where we are: we have a B2C launch window in Q3 and two credible platform paths — native and PWA. Both have real merits and real costs. We've all read the brief, and we're bringing different lenses to this room. By the time we leave, we need one direction — not consensus that both options are fine. Our job today is to use the disagreement productively to get to the right decision, not the comfortable one."
2. Warm-Up: One-Word Check-In (2 min)
Purpose: Shift everyone from their previous context; surface room energy before a high-stakes technical debate.
Facilitator says: "Before we dig in — one word for how you're arriving right now. I'll start: focused."
Facilitator watches for: The mobile engineer or VP using their word to editorialize ("frustrated," "skeptical") — acknowledge it lightly: "Good to name that — let's put that energy to work."
3. Shared Context Alignment (8 min)
Purpose: Ensure the VP of Marketing and engineers are working from the same factual baseline before opinions surface.
Facilitator says: "We all read the brief, but let's make sure we're operating from the same facts. Each of you has a criteria card. I'm going to ask each person to name the one criterion they think matters most for Cartwell's Q3 launch — just the criterion, not the answer yet. We'll go around once."
Facilitator watches for: Anyone jumping to a conclusion ("and that's why we need native") — redirect: "Hold the verdict for now — we're building the map before we navigate."
Artifact produced: Facilitator marks each named criterion on the flip chart. Duplicates get a tally mark. This becomes the shared evaluation framework.
4. Silent Generation: Individual Position Cards (5 min)
Purpose: Prevent the mobile engineer's known preference from anchoring the room before quieter voices have thought independently.
Facilitator says: "On a Post-it, write your current lean — Native, PWA, or Undecided — and your single strongest reason. Don't share yet. This is just for you."
Facilitator watches for: Anyone looking around before writing. If it happens: "Eyes on your own card — this isn't a vote yet, it's thinking time."
5. Small Group Work: Stress-Test Both Options (20 min)
Purpose: Surface the real objections and risks for each option before the full group debate, in a lower-pressure format.
Setup: Split into two groups of 3 (aim for mixed roles in each group).
- Group A — Argue for PWA and identify its biggest risks
- Group B — Argue for Native and identify its biggest risks
Each group gets a half-sheet with two prompts:
- The strongest case for this option given Cartwell's Q3 constraints is…
- The scenario where this option fails us is…
Groups capture responses on Post-its and stick them to their half of the comparison poster.
Facilitator watches for: The mobile engineer dominating Group B. If it happens, ask the other group members directly: "What risks does this option carry that we haven't named yet?"
6. Gallery Walk + Dot Vote (10 min)
Purpose: Let everyone process both sides before the full group discussion; surface real priorities without social pressure.
Facilitator says: "Take 5 minutes to read both sides of the poster. Then use your 5 dot stickers to mark the risks or criteria you think are most decisive — not what you prefer, but what you think will make or break this decision. You can stack dots."
Facilitator watches for: VP of Marketing skipping the technical risks column — gently redirect: "The engineering risks are worth your eyes too — they affect your Q3 timeline directly."
7. Full Group Discussion: Decide (25 min)
Purpose: Synthesize the voting data into a decision with explicit rationale.
Facilitator says: "Here's what the dots are telling us — [read top 3 clustered risks aloud]. Let's discuss: given these as the deciding factors, which platform do we commit to? I want to hear from everyone before we call it."
Structured go-round (5 min): Each person states their position and one reason — no rebuttals yet.
Open debate (15 min): Facilitator manages airtime. If the mobile engineer or VP dominate, use: "I want to make sure we've heard from [name] before we go further."
Decision call (5 min): Facilitator reads back the apparent direction: "What I'm hearing is a lean toward [X] because [top 2 reasons]. Does anyone have a blocking objection — not a preference, but something that would make this option fail?" If no blocks: declare the decision and write it on the flip chart immediately.
Facilitator watches for: Consent vs. enthusiasm — you need the former, not the latter. Name it: "You don't have to love this decision to commit to it. Blocking objections only."
8. Decision Capture (5 min)
Facilitator says: "Let me read back what we decided and why — correct me if anything's wrong."
Capture aloud and in shared doc:
Decision: Cartwell will pursue [Native App / PWA] for B2C launch. Deciding criteria: [e.g., Time to launch against Q3 target; Push notification capability for re-engagement] Risks accepted: [e.g., Higher upfront dev cost; Longer QA cycle] What would change this decision: [e.g., If engineering capacity drops below 2 mobile engineers]
9. Parking Lot Review (5 min)
Facilitator says: "A few things came up that we didn't have time to resolve — let's assign them now so they don't disappear."
Likely parked items:
- Android-first vs. iOS-first sequencing (if native chosen)
- Offline functionality requirements (if PWA chosen)
- Budget approval process for whichever path
10. Closing Round (3 min)
Facilitator says: "Last thing — one word or one sentence: what are you taking