Why Most Ideation Workshops Fail to Produce Decisions
Most workshops do not fail because people lack ideas. They fail because the session was built to generate noise, not to produce a decision.
Teams leave energized, walls are covered in notes, and nothing of real value happens the week after. That is not a people problem. It is a process problem.
Decision-Driven Workshop Cheat Sheet
Core Problem
Most workshops fail not from lack of ideas but from:
- Brainstorming without convergence – ideas captured, none truly chosen.
- No shared definition of success – different, unspoken criteria; politics wins.
- Lost context – no traceable link from ideas → decision → next steps.
What Good Looks Like
A decision-driven workshop always:
- Frames the problem precisely
Use one clear sentence with persona, friction, and desired outcome.
- Forces divergence then convergence
Generate many options quickly, then go deep on only 2–3.
- Makes evaluation objective and visible
Agree 2–4 measurable success metrics and score ideas against them.
90-Minute Agenda (Copy/Paste)
0–5 min: Context & Problem
- Read the one-sentence problem aloud.
- Confirm persona and desired outcome.
5–15 min: Constraints & Assumptions
- Capture hard constraints (budget, date, tech, regulatory).
- List big unknowns and assumptions.
15–30 min: Rapid Divergence
- Timed rounds of idea generation.
- Each idea = headline + one-line rationale.
30–60 min: Pick Top 3 & Go Deep
- Score ideas against agreed metrics.
- Select top 3. For each, define:
- Owner
- One experiment
- Two success measures
- One failure signal
60–75 min: Decide & Assign
- Deciders choose one experiment to run first.
- Record reasoning and link it to the problem statement and constraints.
75–90 min: Document & Schedule Review
- Save all artifacts (problem, metrics, scores, decision, experiments).
- Add them to your project tracker.
- Schedule a review date and assign who reports results.
Anti-Bias Tests
- Hide authorship during first scoring
- Evaluate ideas without names attached.
- Score before gut voting
- Score against metrics first.
- Only then use dot-voting as confirmation, not replacement.
Templates
Problem Statement
For [persona] who struggles with [friction] we will solve [core problem] so they can [desired outcome].
Go deeper
How to Run a Discovery Workshop
Summary
Most ideation workshops fail not because of weak ideas, but because they’re structurally incapable of producing a decision. They’re optimised for generating and sharing ideas, not for converging on a clear, owned next step.
Convergence vs. Consensus
- Consensus = everyone agrees; the group picks what feels safest in the room (e.g. dot voting, show of hands).
- Convergence = the team narrows from many options to a strong shortlist using explicit criteria, and a single decision-owner makes the call.
- Consensus optimises for comfort; convergence optimises for quality and clarity.
Three Preconditions Before Ideation
To reliably leave a workshop with a decision, three things must be locked before ideas are generated:
- A precise problem statement
- Not a broad topic like “How might we improve onboarding”.
- A specific sentence with: persona + friction + desired outcome.
- Example: “For new users who abandon setup within two minutes, we will solve unclear next steps so they can complete their first session without support.”
- This focuses all ideas on the same target instead of scattering them across multiple problems.
- Visible evaluation criteria
- Written down and agreed before anyone suggests ideas.
- Examples:
- Retention > virality for this decision.
- Must be feasible within the next quarter.
- Criteria defined after ideation are usually backfilled to justify a preferred option.
- A named decision-owner
- One person, not “the group”.
- Their job: look at the shortlist, apply broader context, and make the call.
- The group’s job: generate and evaluate options to give that person high-quality inputs.
Why Standard Formats Fall Short
- Popular formats (90-minute workshops, double diamond, lightning decision jams) provide structure but do not guarantee a decision.
- Without:
- a shared problem statement,
- pre-set criteria, and
- clear ownership,
you can run a textbook session and still walk away with only a pile of notes and no decision.
What a Real Decision Output Looks Like
You know a workshop produced a decision if you can state, in one sentence:
What was chosen, why it was chosen over alternatives, and who owns the next step.
If you can’t do that, you produced ideas, not a decision.
How Bandos Enforces This
- Sessions start with a problem statement.
- They end with a ranked shortlist, not a messy board.
- Voting is anonymous, so criteria-not seniority-drive the outcome.
- The output is a scored list with a named next step, not a photo of sticky notes.
Go deeper: How to Run a Discovery Workshop
Decision-Driven Workshop Summary
Most workshops fail not because teams lack ideas, but because they’re structurally incapable of producing a clear decision and owned next step. The issue is process, not people.
Core Problem
Workshops often fail due to:
- Endless divergence without convergence: Ideas are generated and captured, but never truly chosen.
- No shared definition of success: Criteria are vague or unspoken, so politics and seniority dominate.
- Lost context: There’s no clear link from ideas → decision → next steps, so momentum dies after the session.
What Good Looks Like
A decision-driven workshop always:
1. Frames the Job Precisely
Use a single, explicit JTBD (Jobs To Be Done) statement:
As a [persona], I want to [goal], so I can [outcome].
This can also be framed as a problem statement or user need statement, as long as it is specific and shared.
2. Forces Divergence Then Convergence
- First: generate many options quickly.
- Then: narrow to a strong shortlist and go deep on only 2–3 options.
3. Makes Evaluation Objective and Visible
- Agree on 2–4 measurable success metrics before ideation.
- Score ideas against these metrics in the open.
90-Minute Decision-Driven Agenda
0–5 min: Context & JTBD Statement
- Read the JTBD statement aloud.
- Confirm persona, goal, and desired outcome.
5–15 min: Constraints & Assumptions
- Capture hard constraints (budget, dates, tech, regulatory).
- List big unknowns and explicit assumptions.
15–30 min: Rapid Divergence
- Timed rounds of idea generation.
- Each idea = a short headline + one-line rationale.
30–60 min: Pick Top 3 & Go Deep
- Score all ideas against the agreed metrics.
- Select the top 3.
- For each of the 3, define:
- Owner
- One experiment
- Two success measures
- One failure signal
60–75 min: Decide & Assign
- The decision-owner chooses one experiment to run first.
- Record the reasoning and explicitly link it back to:
- The JTBD statement
- The constraints and assumptions
75–90 min: Document & Schedule Review
- Save all artifacts:
- JTBD statement
- Constraints & assumptions
- Metrics and scores
- Shortlist and final decision
- Experiments, owners, and success/failure signals
- Add them to your project tracker.
- Schedule a review date and assign who reports results.
Anti-Bias Tests
- Hide authorship during first scoring: Evaluate ideas without names attached.
- Score before gut voting: Score against metrics first; only then use dot-voting as confirmation, not as the primary decision tool.
JTBD Statement Template
As a [persona], I want to [goal], so I can [outcome].
Alternative framings (problem statement, user need statement) are acceptable as long as they are specific enough that everyone is aiming at the same target.
Example:
As a new user who abandons setup within two minutes, I want to understand my next steps, so I can complete my first session without support.
Convergence vs. Consensus
- Consensus
- Everyone agrees.
- The group picks what feels safest (dot voting, show of hands).
- Optimises for comfort.
- Convergence
- Many options → strong shortlist using explicit criteria.
- A single decision-owner makes the final call.
- Optimises for quality and clarity.
Three Preconditions Before Ideation
To reliably leave with a decision, lock these before generating ideas:
- Precise JTBD Statement
- Persona, goal, and outcome in one sentence.
- Not a broad topic like “improve onboarding” but a specific job or friction.
- Visible Evaluation Criteria
- Written and agreed upfront.
- Examples:
- Retention > virality for this decision.
- Must be feasible within the next quarter.
- Criteria defined after ideation are usually backfilled to justify a preferred option.
- Named Decision-Owner
- One person, not “the group”.
- Their job: apply broader context and make the call.
- The group’s job: generate and evaluate options to give them high-quality inputs.
Why Standard Formats Fall Short
Common formats (90-minute workshops, double diamond, lightning decision jams) provide structure but do not guarantee a decision.
Without:
- A shared JTBD statement
- Pre-set evaluation criteria
- Clear decision ownership
…you can run a textbook session and still walk away with only a pile of notes and no real decision.
What a Real Decision Output Looks Like
You know a workshop produced a decision if you can state, in one sentence:
What was chosen, why it was chosen over alternatives, and who owns the next step.
If you can’t do that, you produced ideas, not a decision.
How Bandos Enforces Decision-Driven Workshops
- Sessions start with a JTBD statement.
- They end with a ranked shortlist, not a messy board.
- Voting is anonymous, so criteria - not seniority - drive the outcome.
- The output is a scored list with a named next step, not a photo of sticky notes.
Further Reading
- How to Run a Discovery Workshop
- How to Run a Discovery Workshop (Bandos deep dive)