Product discovery

At Wzór UX agency, product discovery workshops give you a scope of work that our team or your developers can then deliver. The Fonia and Jawny Lublin projects began with workshops where we set out the product's key features. We then test the chosen features on a clickable prototype, and questions that come up after the workshops are covered in UX consulting sessions.

Challenges

What challenges does product discovery help you solve?

Our approach

Different visions usually surface only with the first screens, when every change already costs money. Before the workshop we talk to the participants one by one, so the differences go onto the agenda as points to settle before anyone starts defending them at the board.

Our approach

In the workshop scope we describe not only the features but also the cases developers usually ask about mid-build: what happens on an error, what an empty screen looks like and what the first version doesn't do. Every vendor then prices the same product.

Our approach

Alongside the team's ideas, we bring your customers' voice to the workshop: their requests, sales data and interviews where they are needed. If discovery concludes the product shouldn't be built yet, that conclusion is a result too, and you get it in writing.

Who it is for

Which companies do we run product discovery for?

Teams with a new product

A new product usually plans more features than the first version can hold, against a deadline that won't wait. In product discovery workshops with the Fonia team we set the priorities and order of features for the cashback app, then designed it in four weeks along with a clickable prototype. We cut the first version down to what lets you test the idea on real users.

Non-profits and media

A non-profit's website has to reconcile its mission with what keeps the organisation going. In workshops with the Jawny Lublin team we described the portal's key features, and of the funding sources we chose together, crowdfunding came out on top, something the team had not considered on that scale before. The same workshops produced the portal's rollout plan and personas.

Manufacturers and service companies

For a manufacturer, an online catalogue is where customers not only choose a product but also download documents. For Swish, the workshops mapped the catalogue's features and the user journey, which produced the specification and scope of work. We shaped every part of the catalogue so customers could download the description, safety data sheet and photos of a product themselves, without writing to the company.

Departments buying a system from a vendor

When an outside vendor builds the system, requirements bounce between business and IT by email and every quote prices a different reading of them. We then run the workshop on the buyer's side, with business and IT in one room, and write the scope in one language for everyone.

Software houses before quoting

A software house quotes a fixed budget and carries the risk of the scope drifting. We run the workshop with its client before the quote, under the software house's brand if needed: we gather the scope, explain what drives the price and prepare the estimate.

First conversation

Free consultation

We ask about your idea and what you already know about the people who will use it. You come away with a recommendation on where product discovery should start and which product questions to settle first. The idea alone is enough, with no brief or feature list.

Patryk Korycki CEO, Business Analyst

Why us?

Why choose our UX agency?

  • Freedom to choose who builds it

    The workshop scope doesn't assume we will be the ones to build the product. We write the documentation for whichever vendor you choose, including your own IT department.

  • Decisions made at one table

    The board, sales and the technical team sit together at the workshop, so issues that kept slipping from week to week in email get settled at the board. Every decision goes into the documentation with its reason and the person who gave it.

  • Less spent on features you don't need

    A feature that drops out at the workshop never reaches design or code, so you don't pay to design and build it. The first version keeps only what tests the idea.

  • A senior team

    The workshops are led by the agency's co-founders, both business analysts, together with our Senior UX/UI Designer, and the same people then design the product. The team has been designing for nine years, today for large organisations, SaaS companies and software houses.

  • Proven client trust

    We have designed for 115 brands, and most of them come back to us with their next project.

  • Higher quality with AI

    We sort the workshop material, meaning notes, board photos and recordings, with the help of AI tools, and the time saved goes into checking that the scope holds together. The documentation reaches you checked for contradictions.

Process

How will we run product discovery, step by step?

  1. Talking with your team

    We agree the workshop goal and who takes part

    At the start we agree which decision the workshops should settle, who needs to be there for it and what material you already have. The workshop script is then written for your problem.

    Key steps

    • Setting the workshop goal
    • Choosing participants from the board, sales and the tech team
    • One-to-one talks with participants before the session
    • Collecting research, analytics and earlier documents

    Deliverables

    • Workshop goal and agenda
    • Participant list
    • List of input materials
  2. Preparation

    We gather the material the team will work on

    We analyse your material and competing solutions and turn them into a script and a working board. You arrive at the workshop with the material already in order, so the time in the room goes on decisions.

    Key steps

    • Analysis of your materials and data
    • Review of competitors and similar solutions
    • User interviews where knowledge is missing
    • A list of assumptions to test at the workshop

    Deliverables

    • Workshop script
    • Working board with input material
    • List of assumptions and questions
  3. Product discovery workshops

    We turn the idea into a first-version scope

    In the workshops we map the user journey, break the idea into features and agree together what goes into the first version and what waits for later. The board gives rise to personas, information architecture and screen flows that the design can stand on.

    Key steps

    • Stakeholder and business goal map
    • User journey mapping
    • Feature mapping and priorities
    • Personas and user stories
    • Information architecture and screen flows

    Deliverables

    • First-version scope
    • Personas
    • User journey map
    • Information architecture and user flow
  4. Handover or design

    The scope goes to your team or to us

    We walk through the workshop documentation at a results meeting and hand it over in files you can keep editing. Design and build of the first version is then led by our team or your developers.

    Key steps

    • Results meeting
    • Answers to questions after the presentation
    • Handover of documentation and working files
    • Next-steps plan

    Deliverables

    • Scope documentation
    • Editable workshop files
    • Next-steps plan
  5. Later versions

    We return to the scope once the first version reaches people

    Features parked at the workshop come back once the first version has gathered data from users. At the next session we order them by what people actually do in the product.

    Key steps

    • Review of data from the first version
    • Interviews with the first users
    • Updating the feature list and priorities
    • Workshop before the next version

    Deliverables

    • Updated scope
    • Priorities for the next version
    • Findings from user interviews

Methods and technologies

Methods we use in product discovery

  • Stakeholder map

    We draw the stakeholder map at the start of the workshops to show who decides, who will use the product and who can stop the project. The room then holds the people without whom the decision wouldn't be made anyway.

  • Personas

    We build personas from data and interviews rather than the team's assumptions: each has a goal, a pain and a moment when it reaches for the product. An argument about a feature is then settled by asking which persona it serves.

  • Customer journey map

    A customer journey map shows the product step by step through the eyes of someone who needs to get something done in it. We add features only against the steps, so you can see which path each of them serves.

  • Feature mapping

    Feature mapping breaks the idea down into single features and assigns them to steps on the journey. The first-version line then sits on the board where everyone can see it at once.

  • Feature priorities and order

    We set feature priorities and their order with you at the workshop, before the first screen exists. Every feature gets its place in the queue, so it is clear what goes into the first version and what waits.

  • Information architecture and user flow

    We lay out the information architecture and user flow during discovery, so the scope takes the shape of screens. A vendor pricing it can see how many views and transitions the first version really has.

Book a product discovery workshop

Interviews, workshops with your team and a first-version scope ready to price.

Client voices

What our clients say

Jonasz Więcławski Chief Executive Officer, Wolumen
“UX Agency Wzór advised us to develop a design system, which in the end made working on our brand much easier. We have ready-made elements to combine, and our image has become even more consistent. The calculator on our site is more convenient for users and looks much better. I recommend working with this collective.”
Marcin Ostrzycki Chief Operating Officer, Selectivv
“We're glad we chose to work with Wzór UX Agency. The time it took to deliver the project, and their commitment, went beyond our expectations. They did solid work for us, which is why we recommend them at every turn.”
Krzysztof Jakubowski President of the Board, Jawny Lublin
“Working on our portal's brand was not the first project UX Agency Wzór delivered for us. We have been working with them for years and we do not intend to change that. Our projects always arrive on time, communication is flawless, and we hold their advice and the quality of their work in very high regard.”
Piotr Majkusiak Owner, Piotr Majkusiak
“I had a vision of my personal brand in my head, but I could not translate any of it into the language of design. Wzór did it perfectly. At every stage they advised me on concrete choices and made me aware of things I had no idea existed. This agency does not throw words around in its proposals. They really do work that way.”
Meet our clients (115)

The team

Who will run your product discovery?

  • Aleksandra Bondar

    Aleksandra Bondar

    Senior UX/UI Designer

    View profile

    How can I help you?

    “I'll prepare the workshop script and, based on what we agree, put together the UX/UI project estimate.”
  • Katarzyna Adamczuk

    Katarzyna Adamczuk

    Prezes, Analityk Biznesowy

    View profile

    How can I help you?

    “I'll draw the scope out of your decision-makers' heads and turn it into a document the whole team keeps coming back to.”
  • Patryk Korycki

    Patryk Korycki

    CEO, Analityk Biznesowy

    View profile

    How can I help you?

    “We'll agree the workshop goal and the participants together, and I'll close the findings with a next-steps plan.”

FAQ

Frequently asked questions about product discovery

What is product discovery?

Product discovery is the stage before design and development in which you establish what problem the product should solve, for whom and what has to be in its first version. With us it consists of interviews, preparation and workshops with your team, and it ends in a scope of work ready to be priced.

How is product discovery different from product strategy?

Product discovery works out how to solve a specific problem and what the first version of the product will contain, while product strategy chooses which problems the company takes on at all. If there is no direction yet, we start with strategy; if it is clear, we start with discovery.

How long does product discovery take?

Product discovery takes at least two weeks with us. We confirm the exact timing once we know the scope.

What do we get after product discovery workshops?

After product discovery workshops you get the first-version scope with features in order of priority, personas, a user journey map and information architecture with screen flows. We go through all of it with you at the results meeting.

Who should take part in product discovery workshops?

Product discovery workshops involve the people who will make the decision about the product, along with representatives of sales, customer service and the technical team. We usually work with a group of five to twelve people and split larger teams into groups.

Can product discovery workshops be held online?

We run product discovery workshops online, on a shared board over a video call, or in person, at our office in Lublin or at your premises. You choose the format when we agree the workshop goal.

Is the product discovery scope enough to price the project?

The product discovery scope is enough to price the first version, because it breaks it down into features, journeys and screens. Questions that come up after the results presentation are discussed at the same meeting.

Do you run product discovery for software houses' clients?

We also run product discovery for software houses' clients, including on a white-label basis under the software house's brand. The scope and estimate go to you, and the client relationship stays on your side.

What if product discovery shows the product isn't worth building?

If product discovery shows the product isn't worth building for now, the documentation ends with that recommendation and the reasoning behind it. You can use the personas and maps you gathered for your next idea.

Patryk Korycki CEO, Business Analyst
Send us a message

Related services

Services related to product discovery

You don't know yet where the product should head.

We'll set the direction and goals, or start with a session with an expert.

You want to hear from users first.

We'll talk to them or check how they cope with your current product.

The scope is ready. Time for the first version.

We'll design it as a clickable prototype or build the MVP straight away.

Next step

Free consultation

We talk about your idea and the people it is meant for. By the end you know where we would start product discovery and what in your product needs settling first. You don't need a finished brief for it.

Patryk Korycki CEO, Business Analyst

Book a free consultation with an expert to discuss your project and get answers to your questions.

- Patryk Korycki, CEO

Schedule a meeting
Book a free consultation