[email protected]
0333 050 1245

Discovery workshop questions: a ready-to-use bank for PMs

  1. Home
  2. »
  3. Blog
  4. »
  5. Brand Recognition: How It Impacts Small Businesses

The discovery workshop questions that actually move a project forward split into three categories: opportunity questions (uncover unmet needs), solution questions (test whether your idea fits a real job to be done), and risk questions (stress-test value, usability, feasibility and business viability). Run all three in one session and you leave with validated hypotheses, not opinions.

Diagram illustrating opportunity, solution, and risk questions

Here’s the one-line plan: block 120 minutes, invite a product manager, designer and technical lead, and leave with a prioritised experiment list as your core deliverable.

Use these categories as your map:

Key Takeaways

Discovery workshop questions work best when grouped into opportunity, solution and risk stages, anchored in real past behaviour rather than hypotheticals.

Point Details
Use three question stages Group every question as opportunity, solution or risk to keep evidence structured and comparable.
Anchor in past behaviour Open with “tell me about the last time…” instead of hypothetical framing to get honest answers.
Match agenda length to stakes Use about an hour for small decisions, two hours for a single journey, and a half-day for deeper discovery.
Convert output into owned tasks Every validated assumption needs a named owner and date within 48 hours of the session.
Kukoo Creative runs branding discovery Kukoo facilitates discovery sessions for logo and website projects, delivering a one-page brief and prioritised next steps.

Table of Contents

What is a discovery workshop and when do you need one?

A discovery workshop is a structured session that validates user needs and business viability before you commit engineering time to a build. It’s the checkpoint between “we think this is a problem” and “we’re confident enough to spend a sprint on it.”

You’ll want one when you’re facing a genuine scope or investment decision, not just a routine planning meeting. Typical goals include:

  • Confirming whether a problem is worth solving at all.
  • Narrowing several candidate solutions down to one worth prototyping.
  • Aligning stakeholders who currently hold different assumptions about the same feature.

Length should match complexity. A full discovery workshop for a major decision often runs two to four days, while smaller feature scoping fits comfortably into a half-day or even a 60-minute session.

What deliverables should a discovery workshop produce?

A discovery workshop earns its place on the calendar when it produces something the team can act on the next morning, not a whiteboard photo nobody revisits. Set your expectations before the invites go out.

Aim to leave with:

  • A short list of validated (or invalidated) hypotheses.
  • A prioritised opportunity list, ranked by impact and confidence.
  • An experiment plan naming what gets tested first and by whom.
  • An annotated customer journey showing where the pain actually sits.

Measure success with concrete markers: how many hypotheses got tested, whether the team’s confidence in the top priority shifted, and how quickly the first experiment launched after the session closed. The output only counts if it lands directly in the backlog or project plan within days, tagged with an owner and a date, not filed away as “workshop notes.”

Who should attend and what does the facilitator own?

Keep the core group tight. A product manager, designer and technical lead form the essential trio, with data, customer success or marketing joining only when their input genuinely changes the decision.

Core and optional attendees:

  • Product manager (owns the problem framing).
  • Designer (owns the journey and prototypes).
  • Technical lead (owns feasibility calls in real time).
  • Optional: data analyst, customer success lead, marketing.

Keep the working group small, generally fewer than ten people. Larger groups should be split into breakout pairs for exercises and reconvene for synthesis, so quieter voices don’t disappear.

The facilitator’s job runs through the whole session:

  1. Frame the problem clearly before any discussion starts.
  2. Keep time, and protect the agenda from well-meaning tangents.
  3. Synthesise input impartially, without pushing their own preferred answer.
  4. Run a visible parking lot for good ideas that don’t fit the current scope.

How do you prepare before the workshop?

Preparation decides more of the outcome than anything that happens in the room. Without a clear problem statement and stakeholder map beforehand, sessions drift into confusion and scope creep almost by default.

Work through this pre-work checklist:

  1. Write a one-sentence problem brief, ideally framed as a clear “How might we” challenge.
  2. Pull a data or analytics snapshot showing where the problem shows up.
  3. Draft basic personas or segment notes, even rough ones.
  4. Gather any existing prototypes, mock-ups or competitor examples.

Your invitation and starter pack should tell attendees exactly what they’re walking into:

  • The objective, stated as one sentence.
  • The agenda, timed in blocks.
  • The expected outputs, named specifically.

For tools, a digital whiteboard (Miro or FigJam), a visible countdown timer, and pre-built templates cover most needs. Running remotely, test screen sharing and board permissions the day before. A broken link five minutes into a 60-minute session is five minutes you never get back.

What agenda and timing should you use?

Copy one of these three templates and adjust the labels to your context.

60-minute sprint (small feature decision):

  1. Frame the problem (10 min) — facilitator leads.
  2. Rapid opportunity questions (20 min) — PM leads, whole group.
  3. Quick risk check (20 min) — technical lead flags feasibility blockers.
  4. Decision and next step (10 min) — facilitator captures the call.

120-minute session (single journey or feature set):

  1. Framing and context (15 min).
  2. Opportunity and solution questions (45 min) — designer facilitates.
  3. Assumption mapping and risk scoring (40 min) — rank by risk and testability.
  4. Prioritise and assign owners (20 min).

Half-day, roughly 240 minutes (deeper discovery):

  1. Problem definition and stakeholder alignment (45 min).
  2. Opportunity questions and journey mapping (60 min).
  3. Ideation against top opportunities (45 min).
  4. Solution and risk questions on shortlisted concepts (60 min).
  5. Early experiment planning and ownership (30 min).

The half-day format leaves room for genuine synthesis, which cmeolabs’ guide to discovery workshops places on day two of longer engagements: scoring opportunities with frameworks like RICE or impact-confidence-effort before anyone touches ideation.

Which exercises and tools actually work?

Pick exercises for what you need to learn, not because they’re popular on workshop decks. Empathy mapping surfaces unspoken frustrations. Assumption mapping makes every hidden belief visible, then ranks each one by risk and testability so the team knows what to test first. Crazy 8s forces rapid divergent sketching when the room has gone quiet on ideas. An impact/effort matrix or RICE score turns a long opportunity list into a short, defensible one. Story mapping lays a journey out horizontally so gaps become visually obvious.

Match the exercise to the moment:

  • Stuck defining the problem? Empathy mapping.
  • Too many untested beliefs? Assumption mapping.
  • Need volume of ideas fast? Crazy 8s.
  • Choosing between validated opportunities? RICE or impact/effort.
  • Mapping a full customer flow? Story mapping.

For remote sessions, Miro and FigJam handle most of these natively with ready templates. In person, printed templates, sticky notes and a visible timer do the same job without the tech risk.

Pro Tip: Test your digital board’s template a day early with one colleague. A broken sticky-note grid discovered live wastes ten minutes and half the room’s patience.

What discovery workshop questions should you ask?

Group your questions by stage, and always open with something concrete rather than hypothetical.

Opportunity questions anchor in real past behaviour. Ask “Tell me about the last time you tried to…” rather than “would you ever…”. Follow up with:

  • “What was the hardest part of that?”
  • “What did you do instead, if anything?”
  • “How often does this happen, and what triggers it?”
  • “Who else gets involved when this comes up?”

Solution questions test fit against a real job to be done, not a feature list. Try:

  • “Walk me through how you’d use this in your actual workflow.”
  • “What would need to be true for you to switch from your current approach?”
  • “Show me what you’d expect to happen after clicking this.” (artefact-based, using a prototype)
  • “What’s missing here that you assumed would be included?”

Risk questions map directly onto value, usability, feasibility and business viability:

  • Value: “If this cost £X a month, would you pay for it today?”
  • Usability: “Without me explaining anything, what do you think this does?”
  • Feasibility: “What systems would this need to connect with on your end?”
  • Business viability: “Who else needs to sign off before your team could adopt this?”
  • “What would block this from being approved internally?”

Airfocus’ list of core discovery questions covers similar ground: current pain points, existing workarounds, must-have features, and how the customer defines success. That framing avoids the trap of designing a solution before you’ve confirmed the problem.

Pro Tip: After any opportunity question, ask “what did you do instead?” It’s the single most reliable line for revealing workarounds people forget to mention unprompted.

How do you ask better questions and manage bias?

Phrasing decides whether you get truth or politeness. Avoid hypotheticals (“would you use this?”) and leading language (“don’t you think this would help?”). Anchor every question in a specific past event instead.

Facilitator hands showing active listening

Three facilitation micro-skills carry most of the weight: active listening (let silences run before jumping in), paraphrasing (“so what you’re saying is…”), and short probes rather than long follow-up speeches. Keep a visible parking lot for tangents so the conversation stays on track without shutting people down.

Watch for three biases specifically: leading questions that plant the answer, social desirability (people telling you what sounds good), and team-anchor bias, where the loudest internal voice quietly becomes the “customer’s” voice. Fix each by rephrasing neutrally, asking for specifics, and inviting disagreement out loud.

Pro Tip: If an answer sounds too polished, ask “can you show me the last time that happened?” Real behaviour rarely sounds rehearsed.

What happens after the workshop?

The workshop only matters if its output changes what gets built next week. Convert findings into commitments before the room empties.

Build a post-workshop checklist:

  1. A decision log noting what was decided and why.
  2. A list of validated and invalidated assumptions.
  3. Prioritised experiments, each with an owner and a date.
  4. A short backlog item or experiment brief per priority, handed to delivery.

Templates worth reusing: a simple backlog item (problem, hypothesis, success metric), an experiment brief (what you’re testing, how, by when), and a user-test plan. Schedule a short triage meeting within 48 hours, hand off formally to engineering or design, and set a cadence for experiment sprints so validation doesn’t stall. If you can’t book 8 to 12 user conversations within the following two weeks, the workshop was probably premature.

What mistakes should you avoid?

The same eight mistakes recur across most unproductive sessions: scope too broad, missing stakeholders, no pre-work, weak facilitation, no follow-up plan, assumptions treated as facts, too many exercises crammed in, and feasibility ignored until it’s too late.

Hand underlining problem statement on tablet

Fix each fast: narrow the problem statement to one sentence; confirm attendee list a week ahead; send pre-work with a deadline; brief the facilitator on timekeeping and parking-lot rules; book the triage meeting before the workshop even starts; back every claim with a data snapshot; cap exercises at two or three per session; and pull the technical lead into every risk conversation.

Adapt the question bank’s tone and examples to your industry. A B2B SaaS workshop and a retail branding session need the same three-stage structure but different vocabulary.

Pro Tip: If you notice three or more of these mistakes happening at once, pause the agenda and re-frame the problem statement out loud before continuing.

How does Kukoo Creative run discovery for branding and web projects?

A typical Kukoo Creative discovery session for a branding or website brief follows the same opportunity, solution and risk structure, adapted for identity work: what does the business actually stand for, who’s the audience, and what does the current site or logo fail to communicate. The outcome is rarely a finished design; it’s clarity on direction.

Our recommended immediate deliverable after any branding discovery session:

  • A one-page brand brief summarising tone, audience and key differentiators.
  • The first three prioritised tasks, ranked by impact.
  • A named owner and date for each.

Discovery for a brand or website project succeeds when the client walks away from the first session already knowing which three decisions matter most, before a single logo sketch exists.

Facilitator notes: what I actually do in minute one

In minute one, I state the problem out loud and ask if anyone in the room disagrees with it. Silence usually means agreement, but not always. Once, a “quick feature review” turned into a pricing debate the moment someone admitted the real blocker wasn’t the feature, it was who’d approve the budget. Reframing the question saved the session.

Do: name the parking lot early. Don’t: let the loudest voice answer for the customer.

How can Kukoo Creative help you run your next discovery workshop?

If reading through agendas, question banks and bias checklists has you thinking “I’d rather someone experienced just ran this for us,” that’s exactly the gap Kukoo Creative fills for branding and website discovery. We bring the structure above into your actual project, tailored to a logo refresh, a full identity build, or a new website system.

Kukoocreative

What’s included when you bring us in for a discovery session:

  • Agenda templates adapted to your project scope.
  • Live facilitation, so your team focuses on answering, not running the room.
  • A one-page workshop report summarising decisions and priorities.
  • A next-step plan naming the first three tasks and owners.

Engagements are project-based, quoted upfront once we understand your scope, so there’s no surprise retainer creeping in later. If you’re weighing up a logo design brief or planning a full website rebuild, get in touch and we’ll scope a discovery session around your actual brief, not a generic template.

Where to read more on discovery workshops

For deeper reading beyond this bank of questions, these sources include their own templates and agenda examples:

Next, try mapping your question bank onto an opportunity solution tree to see where gaps in your current backlog actually sit.

Frequently asked questions

What are the best discovery workshop questions to start with?
Start with an opportunity question anchored in past behaviour, such as “tell me about the last time you tried to do this.” It surfaces real friction faster than any hypothetical prompt.

How long should a discovery workshop last?
Match length to stakes: 60 minutes for a small feature decision, 120 minutes for scoping a single journey, and a half-day (around 240 minutes) for deeper discovery involving ideation and early experiment planning.

Who should facilitate a discovery workshop?
Someone impartial to the outcome, ideally not the person pitching the solution, so synthesis stays neutral and the parking lot gets managed fairly.

What’s the difference between a discovery workshop and a brainstorming session?
A discovery workshop tests real assumptions against evidence and produces prioritised experiments; a brainstorming session generates ideas without necessarily validating them against actual user behaviour.

How many people should attend a discovery workshop?
Keep the core group under eight, built around a product manager, designer and technical lead, adding specialist input only when it changes the decision.

Sources