How to run a Discovery Workshop
A discovery workshop is a structured session that aligns stakeholders on users, problem, scope and success criteria before design and development start, so you build the right thing with fewer mid-build surprises.
How do you run a discovery workshop? You get the right people in one room, work through the business, the users and the technical constraints in a fixed order, and leave with a written scope, priorities and a rough cost and timeline, not a stack of sticky notes nobody opens again. At Code23 we run this on every serious build, whether it’s a marketplace or a wider digital product, because that shared brief needs to exist before anyone writes code.
This isn’t the only workshop worth running. For the fuller breakdown of what we hand over and what it costs, read What Happens in a Product Discovery Workshop?. Once scope is settled and you’re moving into design, Why UX Workshops are Essential to a Project Kick-off covers that next session. This post is the practical one: who needs to be in the room, what order to run things in, and the agenda we actually use.
Contents
- What is a Discovery Workshop?
- Who takes part in a Discovery Workshop?
- What are the key objectives of a Product Discovery Workshop?
- Why are Discovery Workshops so important?
- How do you structure a Discovery Workshop agenda?
- Frequently asked questions
What is a Discovery Workshop?
A Discovery Workshop is the first step in the planning phase of the development process. It is usually the opening meeting between the client and the team who will be working on your project. The client will share their ideas and vision for the business, which will enable the project team to have a shared understanding of the product and the goals of the project.
Whilst running through the Discovery Workshop exercises the project team will have the opportunity to discuss and explore the scope of work and guide the client in the right direction. The Discovery Workshop activities you undertake will also help to identify any critical business challenges you may face during the development phase.
On completion of the Product Discovery process, you should all have a clear understanding of the scope of work and development process, and will be ready to move onto the next phase: product design and UX. That handoff is clearer when you already know the UX deliverables the workshop should feed.
Who takes part in a Discovery Workshop?
The Discovery Session will be led by the facilitator, who is often an Agile Coach or Scrum Master. They will be responsible for translating the information gathered in the workshop into a strategic document and development plan. That being said, the Discovery Workshop should be treated as a collaborative exercise, where topics and ideas can be explored freely.
As well as the primary client stakeholders, the project team members involved from the development agency will typically include:
- The Facilitator (often an Agile Coach or Scrum Master)
- Project Manager
- Technical Lead
- UX Designer
"Code 23 are a first class web design agency. James, Joe and their team are a pleasure to work with and made the process very easy from a client perspective. I was impressed with their ability to work up briefs quickly, their ability to keep to deadlines and the quality of the site that they delivered."
What are the key objectives of a Product Discovery Workshop?
The main aim of the Discovery Workshop exercises is to assess the scope of the project. But there are other important objectives that should be achieved during the Product Discovery process:
- Understanding the motivation behind the project
- Establishing who the target audience is
- Define the value proposition
- Agree the metrics for success
- Outline the core functionalities of the product
- Estimate the project timeline
- Estimate the budget to release the product
Why are Discovery Workshops so important?
There are numerous benefits to running a Discovery Workshop, for both the client and the project team. Some of which we have listed below:
1. Build a relationship with your team
By running a project planning workshop you’ll get to meet some of the project team who will be working on your digital product. They will likely cover a wide range of specialisms, like product strategy, project management, design and development. This knowledge sharing opportunity is invaluable to the successful delivery of your project.
2. Reduce potential risks
During the Discovery Workshop you will not only detail your product vision, but also your business as a whole. This will help identify any pain points or risks that may occur during the development process. Identifying these early enables you to come up with solutions to these risks before they occur.
3. Map out a development roadmap for your project
On completion of the Discovery Workshop you will receive a detailed strategic document that will include all the important details that are needed to kickstart your project. This will of course include a development roadmap and timeline through to the launch of a Minimum Viable Product (MVP) and beyond.
4. Speed up development
By engaging in the Discovery Workshop exercises you will be presented with a list of all of the features and functionality that will be included in your digital product. This minimises the risk of ‘scope creep’ and will speed up the development phase and ultimately the product delivery.
5. Reduce costs
The planning session will characterise which features and functionality will be included, and importantly, at which stage in the development cycle they will be built. Having this development plan agreed before development starts reduces the risk of ‘scope creep’ and unnecessary additional development costs.
How do you structure a Discovery Workshop agenda?
Asking the right questions is key throughout the Discovery Workshop and delivering meaningful outcomes is the primary goal of Discovery Meetings. Here is how we approach a typical Discovery Workshop:
Step 1: Discovery
- How does the business operate? How will this affect the project?
- What is the product vision?
- Who is the target audience?
- Who are the main competitors?
Step 2: Technical Appraisal
- What integrations &/or API’s are required?
- What are the Hosting considerations?
Step 3: Development Roadmap
- What is MVP and what is future development?
- What does success look like and how is it defined?
- What are the potential roadblocks on the project?
- What marketing considerations have you thought about?
Step 4: Project Management Roadmap
- What are the expected timings on the project?
- Are there any events/dates we need to be aware of?
Step 5: Deliverables
- Clear understanding of the full scope of the project
- List of priority features for MVP
- Functional specification (User stories)
- Project management roadmap
- Technical stack and product architecture
- Time and cost estimation
Frequently asked questions
How long should a discovery workshop last?
A useful session is often one focused day, though complex products may need two or more. Shorter workshops work when the brief is already tight; longer ones help when stakeholders disagree on users or scope. Plan follow-up documentation time after the room session ends.
Who needs to attend a discovery workshop?
Bring the decision-makers who own the product vision, plus facilitators who can turn discussion into a plan. From the agency side that usually means a project lead, technical lead and UX designer. Too many observers slow decisions; too few leave gaps you rediscover mid-build.
What do you get at the end of discovery?
You should leave with agreed scope, priority MVP features, user stories or functional notes, a technical direction, and time and cost estimates. Those artefacts feed product design and development without re-litigating basics. For the design-side pack that follows, see the most important UX deliverables.
Is a discovery workshop the same as a UX workshop?
No - discovery settles problem, audience, scope and success criteria; UX workshops go deeper on journeys, structure and interface decisions. They often run back to back, and UX workshops are essential to a project kick-off once discovery has framed the work. Skipping discovery usually means UX time gets spent arguing fundamentals instead.
What’s the difference between a discovery workshop and a discovery session?
In practice, people use the terms interchangeably, and so do we. If there’s a distinction worth keeping, a “session” is often shorter or more informal, one meeting rather than a full day, while a “workshop” implies structured exercises across a longer block of time. What matters more than the label is whether you leave with agreed scope, priorities and next steps, not just a good conversation.
What activities happen in a UX discovery workshop?
Typically: stakeholder interviews to surface assumptions, mapping the target users and their jobs to be done, walking the current process end to end, sketching the core journey, and a prioritisation exercise to sort features into now, later and never. We adapt the mix to the project. A one-day kick-off and a multi-day programme don’t need the same activities.
Can a discovery workshop be run remotely?
Yes. We’ve run discovery workshops in person and over video call, and both work if the structure is right: the right people, a clear agenda and someone facilitating who keeps the room moving instead of drifting into open-ended discussion. Remote works less well when attendees are half-listening between other meetings, so protect the time properly either way.
Next step
Don’t start a build on an understanding you’ve never actually tested in a room. A discovery workshop forces the decisions that are expensive to get wrong later: who it’s for, what’s in, what’s out, and what success looks like.
We’ve been running this process, in one form or another, across 350+ projects since 2005. Book a session and you’ll leave with a written scope, priorities and a clear next step, whether that’s straight into design or a proper Discovery Sprint first.
Design the product
Make the product easier to use before you build it.
We’ll turn the key journeys into a testable prototype, remove friction and give the build team a clear product direction.
