Product Discovery – finding the right solutions before building starts
We make tangible what needs to be built and why. Product Discovery is the second of three building blocks of our product development – it connects the clarity from Product Strategy with the concrete implementation in Product Delivery.
Our approach: testing assumptions before they become architecture
Discovery does not mean collecting wishes. It means asking the right questions before the wrong answers get built. We work with existing research, conduct user interviews and translate insights into concepts that can move directly into implementation.
What the end result looks like
A solid concept as the foundation for implementation. Not a requirements document nobody reads, but flows, prototypes and decision material that carry the team through Delivery. And a shared understanding of what the product should do and for whom.
Typical starting points
-
You know roughly what needs to be built, but not how – and want to clarify that before implementation starts.
-
You have many requirements but no prioritisation and need a solid foundation.
-
You have users but no clear picture of how they actually use the product.
-
You want to make sure that what gets built is actually the right thing.
Product Strategy, Discovery and Delivery
Product Discovery is the second of three building blocks of our product development. It builds on a clear Product Strategy and lays the foundation for Product Delivery, where we bring the product to the road.
Strategy, Discovery and Delivery build on each other and interlock throughout the product lifecycle. Where you start depends on where you are right now.
Overview: Digital Product Development
Typical start
We start by reviewing existing foundations: backlog, designs, existing research, user feedback. Then we clarify together which assumptions are validated and which are not. From that we derive the discovery scope and propose the next meaningful steps.
FAQ
How long does a Product Discovery take?
Typically three to six weeks. Depending on the scope, the number of assumptions to be tested and the availability of users for interviews.
Do we need a Product Strategy beforehand?
Not necessarily. Many clients start directly with Discovery when it is already clear what needs to be built. But a strategy helps avoid misdevelopments.
Can you take on Discovery only, without Strategy and Delivery?
Yes. We can start modular. What matters is that decisions and handovers are documented clearly.
What does it cost?
That depends on the scope. Write us and we will make you an offer.