Skip to content

Product discoveryworkshop

Before you design or build anything, agree what the product is for, who it serves and what the first release must prove. You leave with a scope, a plan and an estimate.
Plan a workshopSee what's included

Decide before you design

These sessions settle the questions that otherwise come up halfway through the build.

  • Problem & goals

    What problem the product solves, for whom, and what success looks like, agreed by everyone who has a say before any design starts.

  • Users & their jobs

    Who the users are and what they're trying to get done, drawn from your knowledge, any research you have and short interviews where we can run them.

  • Assumptions & risks

    The beliefs the product depends on, ranked by how risky they are, so you test the dangerous ones first.

  • Scope & priorities

    A first-release feature list cut to what proves the idea, with everything else parked on a later list instead of argued about.

  • Flows & a rough prototype

    The main user flows sketched and, where it helps, turned into a clickable prototype you can show to users.

  • Plan & estimate

    A written summary of the decisions, the risks and the next steps, with a timeline and estimate for design and build.

    MVP development

How it runs

Short sessions, clear decisions, and a written plan at the end.

  1. Prepare

    Read what you have, and agree who joins and what the workshop must decide.

  2. Frame

    Agree the problem, the users and what success looks like.

  3. Explore

    Map the journeys and the assumptions behind them.

  4. Decide

    Cut the scope to the first release and rank the risks.

  5. Document

    A written plan, rough flows and an estimate for what comes next.

A good fit if

  • You have an idea but no agreed scope
  • Your feature list keeps growing and nothing ships
  • Your team disagrees on what to build first
  • You need a credible plan for investors
  • You want an estimate you can trust before committing

Ready to build?

Discovery leads straight into design and development with the same team.

MVP development

Questions, answered

What people usually ask before a discovery workshop.

What is a product discovery workshop?

A short, structured set of sessions where your team and ours agree what to build, for whom and why, before design and development start. It turns an idea, or a long feature wish list, into a scoped first release and a plan.

Who should take part?

The people who decide what gets built: usually the founder or product owner, someone who knows the customers well, and someone technical if you have them. Small groups make better decisions.

Can it be done remotely?

Yes. We run discovery online with shared boards and short sessions, which also makes it easier to fit around your team's diaries and time zones.

What do we get at the end?

A written summary of what was decided, the main user flows, a ranked list of risks to test, a first-release scope and an estimate for building it. It's yours to use with us or with any other team.

How much does a discovery workshop cost?

It depends on how much research and prototyping you want included. After a short call you get a proposal with the format, the outputs and the price.

Agree what to buildbefore you build it.

Tell us about the idea and who's involved. We'll suggest a format and send a proposal.
Plan a workshopView all services