agentleFS
mahirautela2020-designmahirautela2020-design/claude-skills-ux/collab-workshops-facilitation/SKILL.md

collab-workshops-facilitation

Skill1 starsChanged 8 months agoMITView on GitHub

Designs and facilitates effective workshops. Use when the user needs help planning and running discovery, ideation, prioritization, and alignment sessions, and using collaborative tools (FigJam, Miro) and methods like Crazy 8s, mapping, and prioritization, tied to clear outcomes and next steps.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 13 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when you want to bring a cross‑functional group together to define problems, generate ideas, prioritize work, or build …

    line 21
  2. Distinctive:

    Start by making the workshop purposeful and scoped.[web:173][web:174][web:175][web:179][web:183]

    line 29
  3. Distinctive:

    Create a time‑boxed agenda that balances divergence and convergence.[web:171][web:175][web:179][web:183]

    line 68
  4. Distinctive:

    Keep the focus on user stories and evidence, not solutions.

    line 113
  5. Very specific:

    Keep the energy high and ensure quieter voices have space to contribute.

    line 139
  6. Distinctive:

    When there are too many ideas or opportunities, facilitate prioritization.[web:177][web:179][web:183][web:185]

    line 145
  7. Distinctive:

    Place ideas based on user/business impact and implementation effort.[web:177][web:183][web:185]

    line 150
  8. Very specific:

    Ensure final outputs include a short list of prioritized items, not just raw votes, and align them with product/UX strategy and opportunity …

    line 159
  9. Distinctive:

    Use built‑in facilitation tools:

    line 169
  10. Distinctive:

    Call on different people to share.

    line 177
  11. Distinctive:

    Use chat or reactions for those less comfortable speaking.

    line 178
  12. Distinctive:

    Use timers and stick to time boxes.

    line 242
  13. Distinctive:

    Use individual exercises (Crazy 8s, silent dot voting) to balance input.[web:171][web:176][web:180][web:184]

    line 246
  14. Distinctive:

    Follow up quickly with a written summary and next steps.

    line 254
  15. Distinctive:

    Use this skill with:

    line 260

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Workshop Design & Facilitation

Purpose

This skill helps plan and run UX and product workshops that actually produce decisions and shared understanding, rather than unfocused meetings.[web:173][web:174][web:171][web:175][web:179][web:183] It covers designing discovery, ideation, prioritization, and alignment sessions, and using collaborative tools (FigJam, Miro) and methods (Crazy 8s, mapping, prioritization frameworks) effectively, connected to opportunity framing, strategy, and research follow‑ups from related skills.[web:176][web:180][web:184][web:177][web:185][web:178][web:182]

Use this skill when you want to bring a cross‑functional group together to define problems, generate ideas, prioritize work, or build alignment on direction.


Instructions

Step 1: Define purpose, outcomes, and participants

Start by making the workshop purposeful and scoped.[web:173][web:174][web:175][web:179][web:183]

Ask:

  • "What decision or outcome should this workshop produce (not just activities)?"
  • "Which part of the process is this: discovery, ideation, prioritization, alignment, or critique?"
  • "Who needs to be in the room to make decisions and provide key perspectives?"

Define:

  • A short purpose statement (e.g., “Align on top 3 onboarding problems to tackle next quarter”).
  • 1–3 concrete outputs (e.g., prioritized opportunity list, mapped journey, 10–20 sketched ideas).
  • A participant list representing design, PM, engineering, and relevant business stakeholders.[web:173][web:175][web:183]

Where relevant, tie the purpose to outcomes or opportunity spaces defined in product-discovery-opportunity, product-ux-strategy-alignment, or ux-mindset-problem-framing.


Step 2: Choose workshop type and core activities

Select the type of workshop and supporting activities based on your goal.[web:173][web:175][web:171][web:183]

Examples:

  • Discovery / empathy:
    • Activities: stakeholder interviews, journey mapping, “What we know / think we know / don’t know” boards.
  • Ideation / design:
    • Activities: Crazy 8s, “How Might We” clustering, sketching and sharing, concept posters.[web:176][web:180][web:184][web:171]
  • Prioritization:
    • Activities: impact/effort matrix, MoSCoW, dot voting, RICE card sorting.[web:177][web:179][web:183][web:185]
  • Alignment / critique:
    • Activities: design walkthroughs, structured critique (e.g., “I like / I wish / What if”), decision mapping.[web:173][web:183]

Pick 2–4 activities that fit your time box (e.g., 1.5–3 hours) and purpose, and that you can clearly connect to next steps (e.g., experiments, roadmap items, research).


Step 3: Design the agenda and flow

Create a time‑boxed agenda that balances divergence and convergence.[web:171][web:175][web:179][web:183]

Typical structure:

  1. Opening (10–15 min):
    • Welcome, purpose, outcomes, agenda, roles.
    • Ground rules (e.g., one conversation at a time, critique ideas not people).
  2. Warm‑up (5–10 min):
    • Quick exercise to get people talking and comfortable with the tool.
  3. Core activities (60–120 min):
    • Discovery/mapping, then ideation, then prioritization, depending on goal.
  4. Decisions & next steps (15–30 min):
    • Summarize key outputs, decisions, owners, and follow‑up actions.

Assign rough time to each segment and plan buffer for discussion. Ensure the agenda explicitly ladders up to strategic outcomes or opportunity questions where possible.


Step 4: Set up collaborative boards and materials

Prepare the workspace in FigJam, Miro, or similar.[web:178][web:182][web:171][web:179]

Include:

  • Clear sections for each agenda step, with labels and brief instructions.
  • Pre‑made templates:
    • Journey maps or service blueprints.
    • Crazy 8s frames.
    • Impact/effort grids or other prioritization matrices.
    • Stickies and dot voting markers.
  • Example cards for the first few items to model what “good” looks like.

Share access and any pre‑reads in advance so participants can log in and orient themselves.


Step 5: Facilitate discovery and mapping activities

For discovery, empathy, or alignment workshops:[web:173][web:175][web:171][web:179][web:183]

  • Use activities like:
    • “What we know / think we know / don’t know” about users and problems.
    • Journey mapping or service mapping for key flows.
    • Affinity clustering of existing insights or pain points.
  • As facilitator:
    • Keep the focus on user stories and evidence, not solutions.
    • Capture pain points, questions, and assumptions visually.
    • Summarize themes periodically to keep everyone aligned.

Aim to leave with a clearer shared picture of the problem space and user context, ready to feed into product-discovery-opportunity and ux-mindset-problem-framing.


Step 6: Facilitate ideation: Crazy 8s and beyond

For ideation workshops, use methods that encourage broad idea generation.[web:176][web:180][web:184]

Typical flow:

  • Present a clear problem statement or “How Might We” question.
  • Run Crazy 8s:
    • Each participant sketches 8 ideas in 8 minutes for the same problem.[web:176][web:180][web:184]
    • Emphasize quantity and diversity over polish.
  • Have participants briefly share their favourite 1–2 ideas.
  • Cluster ideas into themes and label them.

You can follow up with:

  • Dot voting to identify concepts worth exploring.
  • Small groups refining selected ideas into more detailed concepts or flows.[web:171][web:175][web:183]

Keep the energy high and ensure quieter voices have space to contribute. Capture the strongest ideas so they can move into prototyping and validation (ux-prototyping-validation).


Step 7: Run prioritization and decision activities

When there are too many ideas or opportunities, facilitate prioritization.[web:177][web:179][web:183][web:185]

Methods:

  • Impact/Effort matrix:
    • Place ideas based on user/business impact and implementation effort.[web:177][web:183][web:185]
    • “Quick wins” (high impact/low effort) often become near‑term focus.
  • MoSCoW (Must, Should, Could, Won’t):
    • Categorize ideas or features to clarify scope for a release or timeframe.[web:177][web:181][web:185]
  • Dot voting:
    • Give participants a limited number of votes to highlight what they believe matters most.[web:171][web:179][web:183]
  • RICE or similar frameworks (if your team uses them):
    • Rough scoring by reach, impact, confidence, and effort.[web:177][web:181][web:185]

Ensure final outputs include a short list of prioritized items, not just raw votes, and align them with product/UX strategy and opportunity sizing where possible (product-discovery-opportunity, product-ux-strategy-alignment).


Step 8: Facilitate remote collaboration effectively

For remote or hybrid workshops, pay extra attention to participation and pacing.[web:178][web:182][web:171][web:183]

Tips:

  • Use built‑in facilitation tools:
    • Timers for activities.
    • Voting tools for prioritization.
    • Cursors or avatars to see who is working where.[web:182][web:178]
  • Mix individual and group work:
    • Solo sketching or note writing to avoid groupthink.
    • Group discussion and clustering after individual work.[web:171][web:175]
  • Encourage participation:
    • Call on different people to share.
    • Use chat or reactions for those less comfortable speaking.

Plan short breaks for longer workshops to avoid fatigue.


Step 9: Close with decisions, owners, and follow‑up

End the workshop by making outcomes and next steps explicit.[web:173][web:179][web:183]

Summarize:

  • What you produced:
    • Mapped journeys, themes, ideas, prioritized lists.
  • What was decided:
    • Which problems or ideas move forward, and in what form.
  • Who owns what:
    • Named owners for follow‑up actions (e.g., refine concepts, validate with users, prepare roadmap items or experiments).
  • When:
    • Timelines for next steps and check‑ins.

After the session:

  • Share a short recap:
    • Screenshots or links to boards.
    • Key decisions and action items.
    • Any open questions that need additional work.

This turns workshop energy into concrete progress rather than a one‑off event and connects outputs into research, experimentation, and roadmapping streams.


Examples

Example 1: Discovery and alignment workshop

  • Purpose:
    • Align on top user problems in onboarding.
  • Activities:
    • “What we know / think we know / don’t know”.
    • Journey mapping for first‑time users.
    • Thematic clustering of pain points.[web:173][web:171][web:175]
  • Outcome:
    • Shared journey map, top 3 problem themes, list of assumptions to validate next via ux-user-research and product-discovery-opportunity.

Example 2: Ideation and prioritization workshop

  • Purpose:
    • Generate and prioritize ideas to improve dashboard usability.
  • Activities:
    • Problem recap and “How Might We” questions.
    • Crazy 8s sketching in FigJam.
    • Dot voting and Impact/Effort matrix.[web:176][web:180][web:184][web:177][web:183]
  • Outcome:
    • 40+ idea sketches, 5 promising concepts, 3 chosen for prototyping and user testing (ux-prototyping-validation), with a short list mapped to product outcomes.

Troubleshooting

Workshops drift off-topic or run out of time

  • Reiterate purpose and outcomes at the start of each segment.
  • Gently park off-topic items in a “parking lot” for later.
  • Use timers and stick to time boxes; be willing to cut or compress activities.[web:173][web:174][web:175][web:171][web:183]

A few voices dominate

  • Use individual exercises (Crazy 8s, silent dot voting) to balance input.[web:171][web:176][web:180][web:184]
  • Invite quieter participants to share explicitly.
  • Set norms about equal participation up front.

Outcomes feel vague or not actionable

  • Reserve time at the end for explicit decision making and action planning.
  • Translate outputs into a small set of prioritized items with owners and links to strategy or opportunity spaces.
  • Follow up quickly with a written summary and next steps.

Notes for use with other skills

  • Use this skill with:
    • ux-mindset-problem-framing and product-discovery-opportunity to frame workshop problems and opportunities and capture outputs into opportunity spaces.
    • product-ux-strategy-alignment to ensure workshops are anchored in strategic outcomes and metrics.
    • ux-user-research and ux-prototyping-validation to plan follow‑up validation from workshop outputs.
    • Stakeholder communication skills (collab-stakeholder-communication) to present workshop outcomes and keep alignment over time.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.