Facilitators —Sprint

Act as a senior sprint facilitator. For this challenge: [insert]. Decide whether a 4 or 5-day sprint is the right format. Cover: is this big-stakes enough? Is it well-bounded? Is the team available? Is there a real decision to make at the end? Could this be solved with research alone? Recommend Sprint, Don't Sprint, or Adapt — with reasoning.

Act as a sprint facilitator following the Knapp method. Take this fuzzy challenge: [insert] and sharpen it. Cover: the long-term goal (in 6 months, what does success look like?), the sprint question (what's the most important question we need to answer this week?), the deciders, the user we'll test with. Present as a pre-sprint brief.

Act as a sprint facilitator. For [insert sprint challenge], identify the right Decider(s). Cover: who has the authority to make the final call on Day 3, who needs to be in the room, who can deputise if needed, what to do if there's no clear decider, the conversation to have with the sponsor about authority. Present as a decider plan.

Act as a sprint facilitator. Recruit the 5–7 person sprint team for [insert challenge]. Cover the roles needed: Decider, Finance/Strategy, Marketing, Customer expert, Tech/Logistics, Design, Trouble-makers. For each: why we need them, the time commitment, the buy-in conversation. Present as a recruitment plan.

Act as a sprint facilitator. Run a 60-minute pre-sprint briefing with the team a week before a sprint on [insert challenge]. Cover: why we sprint, the challenge, the long-term goal, the sprint question, the schedule, the rules (devices off, one conversation at a time), homework, what to expect each day. Present as a briefing agenda.

Act as a sprint facilitator. For [insert sprint], identify the lightning talk experts to invite on Day 1: someone with deep customer insight, someone with technical context, someone with strategic context. For each: what 5-minute talk we want, the questions they should answer, the framing brief. Present as expert briefs.

Act as a sprint facilitator. We need 5 users for Friday's testing. Plan recruitment: target user criteria for [insert challenge], the screener, recruitment channel, incentive, scheduling, backups, the brief for the recruiter. Start this Monday-of-sprint at the latest. Present as a recruitment plan.

Act as a sprint facilitator. Build the materials checklist for a 5-day in-person sprint with [insert number] people. Cover: room setup, walls, sticky notes, markers, dot stickers, timer, snacks, screens, prototyping software, recording setup for testing. Specify quantities. Present as a packing list.

Act as a sprint facilitator. Plan the physical room setup for a 5-day sprint. Cover: where the maps go (long wall), where solutions go (long wall), the prototype zone, where the user testing happens, where lightning talks land, the snacks, the breakout spots, the no-laptop zone vs the build zone. Present as a room plan.

Act as a remote sprint facilitator. Adapt the standard 5-day sprint for fully remote with the team in [insert timezones or spread]. Cover: condensed days vs spread, the tools (Miro, Zoom, Figma, Loom), the energy management, what falls apart and how to compensate, the things that work better remote. Present as a remote adaptation plan.

Act as a sprint facilitator. Run the opening of Day 1 for a sprint on [insert challenge]. Cover: welcome, why we sprint, the week's shape, the rules (devices off, one conversation, time-boxed), introductions, the long-term goal exercise, the sprint questions exercise. Present as a minute-by-minute Day 1 morning script.

Act as a sprint facilitator. Run the long-term goal exercise for [insert project]. The team writes their answer to 'why are we doing this project? Where do we want to be in 6 months, a year, 5 years?' Cover: the framing, the silent solo time, the share-out, how to land on a single goal everyone agrees with. Present as a step-by-step run.

Act as a sprint facilitator. Run the Sprint Questions exercise for [insert challenge] — turning fears into questions. Cover: the framing ('What questions do we want to answer this sprint?'), the silent writing, the format ('Can we... ?'), the compilation, how the questions guide Friday's test. Present as a step-by-step run.

Act as a sprint facilitator. Run the customer journey map exercise on Day 1 for [insert product or service]. Cover: identifying actors, the start, the end, the high-level steps in between, the iterations, when to add nuance, when to draw the line. Present as a step-by-step run with the rules ('keep it simple, 5–15 steps').

Act as a sprint facilitator. Run the lightning talks. For each expert (customer, tech, strategy): the framing, the 5-minute talk, the 10 minutes of questions, the 'How Might We' notes the team writes throughout. Present as a step-by-step run.

Act as a sprint facilitator. Run the How Might We affinity grouping and dot-vote at end of Day 1. Cover: the wall layout, the silent affinity grouping, the labelling, the 2 dots per person vote (decider gets extra), the placement on the map. Present as a step-by-step run.

Act as a sprint facilitator. End Day 1 by picking the target — the moment on the map and the customer the sprint will focus on. Cover: how the Decider chooses, how to handle disagreement, how to make the choice visible, how to close the day. Present as a closing script.

Act as a sprint facilitator. Run Lightning Demos on Day 2 morning. Cover: the framing, the homework (everyone arrives with 3 demos), the 3-minute presentations, the big idea capture, what to do with non-obvious analogues. Present as a step-by-step run.

Act as a sprint facilitator. Run the 4-step Sketch exercise: 1) Notes (20 min — collect ideas), 2) Ideas (20 min — doodle and refine), 3) Crazy 8s (8 min — 8 variants of best idea in 8 minutes), 4) Solution sketch (90 min — 3-panel storyboard, anonymous, given a name). Present as a step-by-step run with the framing for each phase.

Act as a sprint facilitator. Some team members are uncomfortable sketching ('I can't draw'). Coach them: the framing (this isn't about art), the encouragement, the comparison ('boxes and arrows are fine'), the gentle pressure to push through. Present as a coaching script for the moments before and during the solution sketch.

Act as a sprint facilitator. Close Day 2 with the anonymous solution sketches taped on the wall, ready for tomorrow. Cover: the rules (keep them anonymous, don't discuss tonight), the homework (think about it overnight, don't show anyone), the closing reflection. Present as a closing script.

Act as a sprint facilitator. Run the Art Museum on Day 3 morning. Cover: the silent walk-around with the sketches, the 'heat map' dot-stick (every team member sticks dots on what stands out), the 3-minute speed crit per sketch, the straw poll (1 dot per person on favourite). Present as a step-by-step run.

Act as a sprint facilitator. Run the Supervote on Day 3. Cover: the framing (the Decider has the supervote), the discussion of risks/concerns, the placement of the supervote(s), what happens when the Decider picks something the team didn't favour, how to commit to it without resentment. Present as a step-by-step run.

Act as a sprint facilitator. The team has 2 strong, different solutions ([insert them]) and the Decider can't pick. Run a Rumble — prototype both and test both on Friday. Cover: the conditions where a rumble is right, the framing, the implications for the prototype day, the user testing structure (3 users on each? alternating? both prototypes per user?). Present as a rumble decision and run.

Act as a sprint facilitator. Run the Storyboard exercise on Day 3 afternoon. The team builds a 10–15 frame storyboard of the prototype journey for [insert chosen solution]. Cover: the opening scene, the user's journey through the prototype, the points of interaction, the resolution. Decisions made at the storyboard save hours on Day 4. Present as a step-by-step run.

Act as a sprint facilitator. For [insert sprint solution], pick the right prototype approach: clickable digital prototype, paper prototype, physical prop, role-play, brochure/marketing-page test, Wizard of Oz. Justify based on what we need to learn on Friday. Present as a recommendation with the build plan for Day 4.

Act as a sprint facilitator. Assign Day 4 prototype-build roles for this team: [insert team members and skills]. The standard set: Maker(s) — builds the screens. Stitcher — assembles them. Writer — copy. Asset collector — finds images, logos, real content. Interviewer — preps Friday script. For each role: what they do, what they hand off when, the time-boxes. Present as a Day 4 plan.

Act as a sprint facilitator. Help the team keep the prototype realistic-enough for Friday without over-investing. Cover: the 'just real enough' principle, the typical traps (over-polishing, building the back end, fixing edge cases the test won't expose), the moments to call time on a section. Present as a Day 4 reality-check play.

Act as a sprint facilitator. End Day 4 with a trial run of the prototype. Cover: someone fresh role-plays a user, walks through the prototype, the team observes, fixes the obvious breaks before Friday. Present as a step-by-step trial run.

Act as a sprint interviewer. Run the 5-Act Interview Friday morning: 1) Friendly welcome, 2) Context questions, 3) Introduction to the prototype, 4) Tasks and nudges (think aloud), 5) Debrief. Present as a step-by-step interview script for a 60-minute test on [insert prototype].

Act as a sprint facilitator. Set up the observation room on Day 5. Cover: the live stream from the interview room, the team's observation behaviour (silent, taking notes per user), the note-taking template (one row per user, columns for the 3 things you'd ask Sprint Questions), the rule about not interrupting the interviewer.

Act as a sprint facilitator. After 5 user tests on Friday, run synthesis. Cover: putting all observation notes on the wall, finding patterns (3 users = a pattern, 2 = partial, 1 = outlier), mapping patterns back to the Sprint Questions, identifying what we learned. Present as a step-by-step synthesis run.

Act as a sprint facilitator. End the sprint with a clear decision: Build (pursue this direction), Iterate (small fixes, test again), Pivot (different solution to same problem), Park (problem isn't ready). Cover: the framing of the four options, the discussion, the Decider's call, how to capture the decision so the team doesn't lose momentum. Present as a closing script.

Act as a sprint facilitator. Write the post-sprint report for [insert sprint — paste your notes]. Cover: the challenge, the long-term goal, the sprint question, the team, the target, the chosen solution, the prototype, what we tested, what we learned (per Sprint Question), the decision, the next steps. Make it readable in 5 minutes. Present as a 1-page report.

Act as a sprint facilitator. Present the results of [insert sprint and outcome] to leadership in 20 minutes. Cover: the question we answered, the answer (with evidence), the recommendation, the asks. Avoid showing every artefact. Lead with the decision they need to make. Present as a 5-slide outline.

Act as a sprint facilitator. Brief the team that's picking up the work after [insert sprint — paste key learnings]. Cover: what's certain (validated), what's open, what to test next, the artefacts they should reference, the people they should talk to, what NOT to redo. Present as a handover doc.

Act as a sprint facilitator. Capture what the team learned about working together this week — beyond the project outcome. Cover: what worked, what surprised them, what they'd carry into normal work, what they wouldn't. Run a 30-minute team retro. Present as a retro structure.

Act as a sprint facilitator. Adapt the standard 5-day sprint into 4 days (the modern Knapp recommendation). Cover: what gets compressed, what gets cut, what gets pushed earlier, the new daily flow. Present as a 4-day adapted run sheet.

Act as a sprint facilitator. Run a 2-day lightning sprint when you don't have 4–5 days. Cover: what's preserved (the question, the test), what's stripped (lightning talks, deep mapping, polished prototype), the cost of compression, when this works vs falls apart. Present as a 2-day adapted plan.

Act as a sprint facilitator. Run a Foundation Sprint (a Knapp variant for very early-stage problems). Cover: how the goal is more 'find the right problem' than 'test a solution', the activities that change, the output (a sharper challenge, not a prototype), when this is the right call. Present as a Foundation Sprint structure.

Act as a sprint facilitator. Run a sprint embedded in [insert programme context]. Cover: how to bound the sprint scope without it expanding, how the team protects 5 days, how the sprint output handshakes with programme deliverables, how to avoid the sprint becoming 'just another planning session'. Present as a sprint-in-context plan.