Design and facilitate high-impact client workshops — agenda design, facilitation techniques, virtual and in-person formats, idea generation, decision-making, and synthesis. Includes ASE (Accelerated Solutions Environment) methodology for complex, multi-day co-creation workshops. Use whenever workshops, facilitation, brainstorming sessions, design thinking, strategy sessions, alignment meetings, ASE, or working sessions come up. Use when user asks to "design a workshop", "facilitate a session", "brainstorming agenda", or mentions facilitation, design thinking, strategy offsite, or ASE methodology.
npx claudepluginhub lauraflorentin/skills-marketplace --plugin management-consultingThis skill uses the workspace's default tool permissions.
A well-designed workshop is a strategic lever for consulting. It creates shared understanding, generates insights that isolated interviews miss, builds buy-in through participation, and accelerates decision-making. Poor workshops waste time and damage credibility. This skill covers designing and facilitating workshops that deliver results.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
A well-designed workshop is a strategic lever for consulting. It creates shared understanding, generates insights that isolated interviews miss, builds buy-in through participation, and accelerates decision-making. Poor workshops waste time and damage credibility. This skill covers designing and facilitating workshops that deliver results.
Purpose: Understand current state, identify pain points, establish baseline for recommendations Duration: 4-8 hours, can span multiple days Participants: 8-25 people across functions (operators, middle management, finance, IT) Outputs: Pain point inventory, current-state map, root cause hypotheses Structure: Discovery → analysis → synthesis → validation
Use when:
Purpose: Co-create future-state solution with key stakeholders Duration: 2-5 days, often run consecutively Participants: 6-15 people including process owners, subject matter experts, user representatives Outputs: Process design, system requirements, operating model, implementation approach Structure: Ideation → design → critique → refinement → validation
Use when:
Purpose: Make critical decisions (go/no-go, option selection, sequencing) Duration: 2-8 hours Participants: 6-15 decision-makers, stakeholders, subject matter experts Outputs: Decision document, agreed option, implementation plan, accountability Structure: Context → options review → debate → decision → alignment on next steps
Use when:
Purpose: Develop multi-year strategy or roadmap Duration: 2-3 days Participants: Executive leadership, function heads, strategic advisors Outputs: Strategy articulation, roadmap, initiatives, success metrics Structure: Context → vision → priorities → initiatives → sequencing → metrics
Use when:
Purpose: Review what worked/didn't work, capture insights, plan improvements Duration: 3-6 hours Participants: Core project team, extended stakeholders Outputs: Lessons document, improvement areas, action items Structure: Timeline review → what worked → what didn't → root causes → improvements
Use when:
1. Energy Management Morning = High energy and complexity. Afternoon = Synthesis and decisions.
Sample Day Structure:
2. Balance Input and Output
Workshops fail when they become presentations. Aim for 2:1 ratio of group work to presentation.
3. Breakout Sessions for Large Groups If 20+ people, use breakout sessions on focused topics, then reconvene to share/integrate.
4. Time Boxes Discipline Assign time to every activity. Build in 15% buffer for overruns.
Example:
Day 1: Context & Ideation
Day 2: Design & Critique
Day 3: Validation & Decision
For detailed templates, frameworks, and field-level guidance, read:
references/workshop-facilitation-reference.md — Complete framework details, templates, and examplesRead this file when the task requires: