PromptSharp › Prompt Library › Consulting & Strategy › Workshop designer: an agenda engineered to end in a decision
Workshop designer: an agenda engineered to end in a decision
You own a 3-hour steering workshop next week. Design the agenda, exercises, and pre-read so it ends with a decision instead of a parking lot.
The prompt — copy and run it
You are a facilitation designer engineering a client workshop that must end in a decision. I will describe the decision and the room. Produce: A) AGENDA — a table: block, duration, exercise format (silent brainstorm, dot-vote, 2x2 sort, breakout-and-readback), input required, and the output artifact each block must produce. B) DECISION MECHANISM — state explicitly how the final call gets made: criteria, who decides, what happens on a tie. This goes in the agenda, announced up front. C) PRE-READ OUTLINE — 2 pages maximum: the decision, the options, the data each attendee must arrive knowing. D) FAILURE MODES — the 3 most likely ways THIS group derails (e.g., senior-voice domination, relitigating scope, data disputes) with one concrete facilitation move to counter each. Inputs: [THE DECISION TO BE MADE + OPTIONS ON THE TABLE] · [ATTENDEES: ROLE + LIKELY STANCE] · [DURATION + FORMAT (ROOM/REMOTE)] Rules: Do not invent attendee opinions — stances I have not given you are "unknown: probe in the opening check-in". Verify logistics constraints before finalizing. Keep client-confidential material out of the pre-read outline.
Why this prompt works
Workshops fail in the design, not the room. Naming the decision mechanism up front is the single highest-value move — most groups argue about options endlessly because nobody agreed how the call gets made — and per-block output artifacts kill the sticky-note theater.
Want the daily version?
The PromptSharp Consulting Brief delivers prompts like this every day. Honest status: sample stage — 50 waitlist signups start the free daily, and waitlist members see every issue first.
Frequently asked
When should I use this prompt?
You own a 3-hour steering workshop next week. Design the agenda, exercises, and pre-read so it ends with a decision instead of a parking lot.
Why does this prompt work?
Workshops fail in the design, not the room. Naming the decision mechanism up front is the single highest-value move — most groups argue about options endlessly because nobody agreed how the call gets made — and per-block output artifacts kill the sticky-note theater.
What mistake does this prompt help you avoid?
{'code': 'PF09', 'note': 'Workshops that end in a parking lot — the decision mechanism is named up front and every block must produce an output artifact.'}
Related Consulting & Strategy prompts
Workshop design: an agenda engineered to produce a decision, not a discussion
You have a room of senior stakeholders for three hours. Design an agenda that ends in an actual decision, not a vibes session.…
Weekly client status: progress, risks, and the scope-creep firewall
Friday status is due. Turn the team's raw week into a status the sponsor actually reads — and a scope conversation before it becom…
All Consulting & Strategy free prompts
The PromptSharp Consulting Brief page — five full free prompts plus the ladder status.
PromptSharp Daily — free
The cross-vertical sampler: one sharp, copy-paste prompt each day, rotating across the roster. See what each vertical is like before you commit to one.
Double-opt-in. Unsubscribe anytime. No spam, ever.
Home · Prompt Library · Pricing · Archive · Privacy · Terms · Refunds
Finance · CPG · Marketing · Sales · Consulting & Strategy · Product Management · Dev & Engineering · C-suite · Law · Personal Finance · Career & Job Search · Focus & Productivity · Learning · Health & Fitness · Parenting