Ten copyable workshop agenda examples with concrete timing blocks and facilitator notes β strategy, kickoff, retrospective, design thinking, OKR, and more.
A strategy offsite and a 90-minute retrospective share a skeleton β open, diverge, converge, close β but almost nothing else: not the timing, not the methods, not where the energy dips or where the decision gets made. This page is an agenda library. For each of ten common workshop types you get a ready-to-run agenda with concrete timing blocks you can copy into your planning document, plus facilitator notes on energy, buffers, and decision points.
If you want the underlying structure instead β one reusable template you can adapt to any session β start with the workshop agenda template. That article explains the skeleton. This one hands you the filled-in version for the session you are actually running.
How to read these agendas
- Times are relative. 0:00 is your start time, so every agenda works at 9:00 or 14:00.
- Group size assumption is 6β12. Above that, split into sub-groups of 4β6 and add 10 minutes per share-back.
- Buffer is already built in. The blocks look generous on purpose β resist the urge to compress them. If you need to shorten an agenda, cut a block, not the slack (see workshop duration planning).
- Every agenda ends with owners. A workshop that closes without named owners and a follow-up date produced sticky notes, not outcomes.
Strategy workshop agenda (full day)
Goal: leave with 3β5 prioritized strategic moves, each with an owner. Works for leadership teams of 5β10. More on the format on the strategy workshop page.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:20 | Check-in & framing | Name the decision the day must produce, and who breaks a tie |
| 0:20β1:05 | Current state | Data walk-through, then a SWOT analysis against it | | 1:05β1:15 | Break | | | 1:15β2:15 | Diverge | Strategic options via brainwriting β silent first, discussion second | | 2:15β3:00 | Cluster | Affinity map the options into 6β8 candidate moves | | 3:00β3:45 | Lunch | | | 3:45β4:30 | Stress-test | Premortem on the strongest candidates | | 4:30β5:15 | Converge | Dot voting, then the named tie-breaker decides | | 5:15β5:30 | Break | | | 5:30β6:15 | Commit | Owner, first step, and review date per move | | 6:15β6:30 | Close | Commitment round: each person states what they now own |
Facilitator notes
- Schedule the premortem after lunch deliberately. The post-lunch dip breeds skepticism, and skepticism is exactly what a premortem runs on.
- Announce the decision rule at 0:20, before anyone is attached to an option β never after the vote.
- The current-state block always runs over. The 45 minutes are already padded; if it still overflows, cut slides, not discussion.
For a version with pre-work and stakeholder preparation, see the full-day strategy workshop agenda.
Kickoff workshop agenda (half day)
Goal: a new project team that knows why the project exists, what each person brings, and how it will work together. See the kickoff workshop page for method options.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:15 | Check-in | One expectation per person (check-in questions) |
| 0:15β0:45 | Context | Sponsor explains the why, then takes questions |
| 0:45β1:30 | Surface concerns | Hopes and fears, clustered on the wall |
| 1:30β1:45 | Break | |
| 1:45β2:30 | Team setup | Team canvas: roles, skills, goals |
| 2:30β3:00 | Ways of working | Working agreements β decided, not just collected |
| 3:00β3:30 | First steps | Plan the first two weeks, assign owners, close |
Facilitator notes
- The sponsor speaks early and then stops facilitating by presence. If they stay, brief them to ask questions rather than answer them.
- Working agreements are a decision point: read each aloud and get explicit consent, or they evaporate within a week.
- The energy dip lands around minute 90 β that is why the break sits exactly there.
A deeper walkthrough: the perfect kickoff workshop agenda.
Retrospective agenda (90 minutes)
Goal: one to three concrete changes for the next iteration, each with an owner. Format background on the retrospective page.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:10 | Open | One-word check-in, restate the prime directive |
| 0:10β0:35 | Collect | Sailboat retrospective: wind, anchors, rocks |
| 0:35β0:55 | Discuss | Cluster, then dig into the two biggest themes |
| 0:55β1:10 | Converge | Dot voting on what to change |
| 1:10β1:25 | Actions | Actions for retrospectives: 1β3 items, owners, deadlines |
| 1:25β1:30 | Close | Quick temperature check on the retro itself |
Facilitator notes
- Cap actions at three. A retro that produces five actions produces zero.
- Rotate the collection format every few sprints β start-stop-continue or mad-sad-glad β before answers become rehearsed.
- The buffer hides inside the discussion block: if collection runs long, discuss one theme instead of two.
Design thinking workshop agenda (full day)
Goal: two or three tested concept directions for a defined design challenge. See the design thinking workshop page.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:20 | Frame | Check-in, then the design challenge in one sentence |
| 0:20β1:20 | Empathize | Gallery walk through research findings and user quotes |
| 1:20β1:30 | Break | |
| 1:30β2:15 | Define | Reframe insights as How Might We questions |
| 2:15β3:00 | Lunch | |
| 3:00β3:45 | Ideate | Crazy 8s: eight sketches in eight minutes, then share |
| 3:45β4:30 | Select | Sort ideas on a How-Now-Wow matrix, pick 2β3 concepts |
| 4:30β5:30 | Prototype | Paper prototypes or storyboards per concept |
| 5:30β6:00 | Test & close | Feedback rounds; decide what gets prototyped properly next week |
Facilitator notes
- No research, no workshop. The empathize block only works with real user input on the wall β postpone rather than improvise personas.
- Timebox the sketching ruthlessly; the discomfort is the method.
- The 4:30 selection needs criteria named before sorting starts, or the loudest sketch wins.
OKR planning workshop agenda (half day)
Goal: this cycle's objectives and key results, committed and owned. Method options on the OKR workshop page.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:15 | Open | Check-in, review last cycle's scores without relitigating them |
| 0:15β1:00 | Draft objectives | 1-2-4-All on "what must be true in 90 days" |
| 1:00β1:15 | Break | |
| 1:15β2:00 | Key results | Draft KRs per objective (OKR planning session) |
| 2:00β2:40 | Stress-test | Each KR: measurable? influenceable? Sort on an impact-effort matrix |
| 2:40β3:15 | Commit | Final wording, owners, check-in cadence |
Facilitator notes
- Hold the line at three objectives. The workshop's main output is what the team agrees not to pursue.
- KRs drift into task lists under time pressure β the stress-test block exists to catch that, so protect it when running late.
- Decision point: who cuts the fourth objective? Agree at 0:15, apply at 2:40.
Team offsite agenda (one-day core)
Goal: the two conversations the team keeps postponing, resolved, plus renewed working relationships. See the leadership offsite page for the leadership variant.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:30 | Arrive | Rollercoaster check-in: the last six months in highs and lows |
| 0:30β1:30 | Look back | Timeline retrospective of the period since the last offsite |
| 1:30β1:45 | Break | |
| 1:45β3:00 | Big topic 1 | The postponed conversation, in World CafΓ© rounds |
| 3:00β4:00 | Lunch | Long on purpose β the corridor talk is part of the agenda |
| 4:00β5:00 | Big topic 2 | Options and a decision, not another discussion |
| 5:00β5:30 | Walk | Outside, in pairs, no task |
| 5:30β6:15 | Commit | What changes back at work, with owners |
| 6:15β6:30 | Close | Appreciations exercise |
Facilitator notes
- Offsites die of overstuffing. One day carries two real topics β a third topic costs you both.
- Social time is not filler; the long lunch and the walk do work the plenary cannot.
- If topic 1 produces the decision topic 2 needed, swap the afternoon rather than running the plan.
Why most offsite agendas plan logistics instead of facilitation: the team offsite agenda nobody writes.
Brainstorming workshop agenda (2 hours)
Goal: a ranked shortlist of ideas against one sharp question. More formats on the innovation workshop page.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:10 | Frame | One How Might We question, visible all session |
| 0:10β0:35 | Silent diverge | Brainwriting rounds β ideas on paper before anyone speaks |
| 0:35β1:00 | Build | Round robin: each person extends someone else's idea |
| 1:00β1:10 | Break | |
| 1:10β1:35 | Sort | How-Now-Wow matrix: implementable now vs. genuinely new |
| 1:35β1:50 | Converge | Dot voting on the "Wow" column |
| 1:50β2:00 | Close | Top 3β5 ideas get an owner for a feasibility check |
Facilitator notes
- Starting silent is the single highest-leverage choice: it protects introverts' ideas from the anchor effect of the first spoken suggestion.
- Energy peaks early β put the hardest thinking before the break and the sorting after.
- An ideation session without a follow-up owner is entertainment. The last ten minutes are the point.
Problem-solving workshop agenda (half day)
Goal: root cause understood, solution chosen, owner assigned. Format background on the problem-solving workshop page.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:15 | Frame | The problem owner reads the problem statement as written |
| 0:15β1:00 | Root causes | The 5 Whys in groups of 3β4, compared in plenary |
| 1:00β1:15 | Break | |
| 1:15β2:00 | Sense-making | What, So What, Now What on the cause map |
| 2:00β2:45 | Solutions | Lightning Decision Jam: generate, vote, pick |
| 2:45β3:15 | Commit | Owner, first experiment, and a date to check the fix worked |
Facilitator notes
- Keep cause-analysis and solutioning in separate blocks. Groups that jump to fixes at minute 20 solve symptoms.
- The problem owner participates but does not facilitate β they are the person least able to see the frame.
- Decision point: the chosen fix is an experiment with a check date, not a verdict.
Sprint planning agenda (2 hours)
Goal: a sprint goal the team believes in and a scoped backlog that fits capacity. For the surrounding team practices, see the way of working page.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:10 | Goal first | Draft the sprint goal before touching any ticket |
| 0:10β0:40 | Clarify | Top items from backlog refinement: open questions only |
| 0:40β1:20 | Estimate | Planning Poker on the candidate items |
| 1:20β1:45 | Scope | Commit items against real capacity β holidays and support load included |
| 1:45β2:00 | Confidence | Fist-of-five on the goal; below three fingers, remove something now |
Facilitator notes
- Goal before items, always. Teams that start from the ticket list produce a pile, not a sprint.
- An estimation debate longer than five minutes is a signal to split the story, not to keep debating.
- The confidence vote is the buffer: it is cheaper to cut scope in minute 110 than in week two.
Vision workshop agenda (half day)
Goal: one vision narrative the group would defend, plus the first milestones toward it.
| Time | Block | What happens |
|---|---|---|
| 0:00β0:15 | Open | Check-in: "a postcard from us, three years out" |
| 0:15β1:00 | Diverge | Letter from the future, written solo, read aloud |
| 1:00β1:15 | Break | |
| 1:15β2:00 | Make it concrete | Cover story: the magazine feature about your success |
| 2:00β2:45 | Work backwards | Backcasting: milestones from the vision to next quarter |
| 2:45β3:15 | Converge | Agree the narrative's substance, name owners for milestone one |
Facilitator notes
- Groups burn hours arguing vision wording. Converge on substance β what is true in three years β and assign the polishing to one writer afterwards.
- Backcasting is what separates a vision workshop from a poetry reading: no milestones, no workshop.
- If the vision kicks off a transformation program, plan the follow-up with the change management workshop page in view.
Adapt the agenda, keep the spine
All ten agendas follow the same spine β open, diverge, converge, close β with the weight shifted to match the job: retros converge fast, ideation sessions diverge long, offsites protect social time. When you adapt one, move blocks rather than shaving minutes off all of them, and re-check three things: where the energy will dip, where the buffer lives, and who makes the call at the decision point. Running remote? Halve the block lengths and double the interaction β the virtual workshop planning guide covers the adjustments.
Before you send any of these out, run it through the workshop planning checklist, and for the full planning process from objective to follow-up, see the Workshop Planning Guide.
If you'd rather not assemble the blocks by hand, Workshop Weaver generates a method-backed agenda draft from a plain description of your goal, group, and time budget. The judgment calls above β energy curve, buffers, decision points β stay yours; the tool just gets you a defensible first draft in minutes instead of an afternoon.
π‘ Tip: Try Workshop Weaver free for 7 days. No credit card required.
Start freeRelated Articles
Workshop Planning Template: A Fill-In One-Pager
Copy this workshop planning template: goal, participants, agenda blocks, materials, and follow-up on one page β with facilitation notes on every field.
Workshop Planning Tools Compared: What Each Is Best At
An honest comparison of SessionLab, Miro, Mural, Butter, and Workshop Weaver across the full facilitation workflow: planning, running, and follow-up.
How to Structure a Workshop: The Four Blocks That Work
Learn how to structure a workshop with four building blocks β opening, divergence, convergence, commitment β plus energy-curve timing rules, a half-day vs. full-day decision table, and three example structures.