It helps you figure out what to build, why it matters, and how to do it right.
In this article, we’ll show you how we run discovery at DECODE – how we plan, what we deliver, who’s involved, and what we’ve learned from real projects.
Let’s dive in!
Table of Contents
Why do we do product discovery?
Here’s the truth: a strong product doesn’t start with design or development. It starts with clarity.
You need to know what matters before you start building. That’s exactly what product discovery is for.
It’s not about slowing you down, it’s about helping you build the right thing the first time.
If you skip it, you’re gambling with your time and money. And most companies, and especially startups, can’t afford to do that.
Discovery is where your idea starts becoming real.
This isn’t about writing lengthy documents no one reads. It’s about asking the right questions. Then finding honest answers:
What do your users actually need?
What’s the best way to build it?
Where’s the value, for users and for you?
The goal here isn’t perfection. It’s to give you enough clarity to move forward with confidence.
You’ll define your direction, test your thinking, and uncover potential issues before they become real problems.
At DECODE, we focus on 4 things:
Understanding your users
Making the product as simple to use as possible
Aligning with your vision
Getting to the next phase quickly
But here’s the thing: no two discovery projects are ever the same.
Some are fast and tactical, while others are deep dives. One project will need a clickable prototype, and another just needs a rough feature list and a plan.
We shape the process around your needs. Not the other way around.
It all starts before the contract is even signed. We listen. We ask questions. We map out where you are and what makes sense next.
This saves time, money, and makes everything that follows a whole lot easier.
We never use a one-size-fits-all approach.
We believe discovery should work for you, not force you to work around it.
How we set up product discovery for success
Next, we’ll discuss how we set up our product discovery projects for success from day one.
Planning before kick-off
Discovery doesn’t start when the contract’s signed. It starts as soon as we talk.
From the first call, we’re already digging in:
What’s the idea?
What problem are you solving?
What’s missing?
Where are the unknowns?
These early conversations matter. A lot.
They shape what discovery looks like and how far we need to go.
We don’t wait to figure things out halfway through. We use this early phase to:
Spot risks before they become problems.
Challenge assumptions, both ours and yours.
Define what should be included in the project.
Decide what we can skip.
The goal is to align early. So when discovery officially starts, we’re already pointed in the right direction.
This is how we avoid surprises later on.
And how we turn a vague idea into a real, structured plan before anyone opens a design tool or writes a line of code.
Setting clear goals
Discovery isn’t just something you “get through.”
It’s the phase that determines whether what you build actually makes sense.
And that’s where clear goals come in.
We keep it simple. Here’s what we aim to do:
Understand what users actually need
Clarify your business priorities
Define what’s technically feasible
Get everyone involved on the same page
We don’t need a complete blueprint from day one. But we do need direction.
Discovery works best when everyone knows what we’re trying to achieve.
And not just what we’re building but why we’re building it, who it’s for, and what success looks like.
That’s what goal-setting is for. It helps us keep everyone on the same page, cut distractions, and focus on the outcomes that matter most.
We define goals that are clear, measurable, and tied to real user or business value. That way, every decision we make during discovery has something to point back to.
When discovery works, you leave with:
A clear understanding of your product
A set of clear priorities
Realistic timelines and budgets
Confidence in what to build next
This sets the tone for everything that follows.
And when you’re on a time crunch or have a limited budget, this type of clarity is essential.
Adapting discovery scope to each project
We don’t treat discovery like a checklist, because no two projects are ever the same.
Some clients show up with just an idea. Others already have wireframes, branding, or investor decks.
That’s why we shape discovery around the product, not the other way around.
We tailor the scope based on where you are and what you need. That might mean:
Skipping user research if you’ve already done it.
Prioritising feature planning over design.
Running extra workshops to align your team.
Focusing on technical feasibility if the concept is already validated.
Building a clickable prototype to support an upcoming funding round.
We figure this out early, usually during presales.
That’s when we dig in, ask tough questions, and get a sense of what will move your product forward.
The point is: we don’t waste time during discovery.
We make sure you get only what’s actually useful for your project. Nothing more, nothing less.
This is how we keep discovery lean, sharp, and directly tied to your goals.
DECODE product discovery team: key roles involved
A strong discovery process needs a strong team.
It works best when people with different strengths tackle the problem together.
At DECODE, that team always includes 3 core roles: product manager, product designer, and solution architect.
Each one looks at the product from a different angle – business, user, and tech.
It’s this balance that helps us ask the right questions early, avoid guesswork, and keep the whole thing moving forward.
We’ll discuss exactly what they do next.
Product manager
The product manager leads on business value and direction. They’re responsible for making sure the product makes sense in the real world, not just on paper.
They work directly with you to unpack the idea:
What’s the goal
Who is this for?
How do we define success?
They help shape your product vision into something concrete.
That includes identifying key user needs, setting priorities, and working with the team to translate your goals into actual features.
They’re also responsible for keeping discovery structured. They run workshops, coordinate feedback, and make sure we make the right decisions.
If something’s unclear or getting off track, they pull it back into focus.
They’re the glue between design, tech, and the client.
Product designer
The product designer owns everything related to the user experience.
Their job is to understand who the users are, what they need, and how they’ll move through the product.
They create user personas, map out user journeys, and build early wireframes that show how your product will work before any code is written.
They also test ideas visually. Is this the simplest path to solving the problem? Can someone new understand what to do?
In many of our projects, our designer also helps you define your visual identity. That could mean defining a basic design system or building a clickable prototype for testing or fundraising.
At every step, they bring it back to the user. If it doesn’t solve the problem clearly, it doesn’t go forward.
Solution architect
The architect makes sure the product can actually be built and scaled.
They take what’s being discussed in discovery and figure out what it means technically.
They explore different implementation options and flag constraints early.
They’ll dig into third-party APIs, assess legacy systems if they exist, and document how everything fits together.
If something is unclear, they’ll reach out to vendors, ask questions, and get answers.
They help define the system architecture: what services it needs, what the backend should look like, how data flows, and how the infrastructure should be set up.
They also provide time and effort estimates, so everyone knows what’s feasible within the client’s budget and timeline.
Most importantly, they make sure the tech plan is solid before design and development begin.
That reduces risk and saves a lot of time down the road.
Our core product discovery deliverables
So what do you actually get from our product discovery process?
It’s real, tangible outputs that help you understand your product and make better decisions moving forward.
And like we mentioned, we don’t deliver everything by default. We tailor each discovery to the project, cut the fluff, and focus on what’s most useful for our client.
But across most projects, these are the core deliverables we give our clients:
DECODE product discovery deliverables: overview
Deliverable
What it is
Why it matters
Project alignment document
A short, high-level document that outlines the scope, goals, and current knowledge from initial workshops.
Ensures everyone’s on the same page from day one to avoid misunderstandings later.
Assumptions and risks
A list of assumptions made (e.g. “mobile-first”, “client will provide copy”) and potential risks with a mitigation plan.
Flags what could go wrong early, before it becomes expensive. Helps the team stay realistic.
A categorized feature list, usually scored by value, effort, and technical dependency.
Helps narrow the scope to an MVP. Keeps things focused and realistic.
Technical solution proposal
Documentation covering system architecture, integration points, estimated effort, team setup, and budget.
Provides a realistic development plan. Crucial for both our internal planning and client decision-making.
Visual identity guidelines
A mini brand book: color palette, typography, logo rules (if none exist).
Gives the product a visual direction. Useful for prototypes, pitch decks, and eventual design handoff.
UI design and clickable prototype
High-fidelity designs linked together into a functional prototype.
Lets clients and investors experience the product. Much more convincing than static slides.
Documentation handover
A complete, organized package of all approved deliverables. Delivered incrementally throughout the process.
Avoids surprises. Ensures everything is signed off. Makes design and dev handover smooth.
We’re here to help you figure out what you need up front.
You get exactly what you need to move forward – confidently and with a real plan.
What real projects taught us about discovery
Discovery isn’t theory. It’s practical. It saves time, saves money, and helps you make better decisions.
We’ve seen it work. Again and again.
One client came in set on building a web app for experienced traders.
But during discovery, it became clear the real opportunity was a mobile app for beginners. That shift changed everything:
Smaller scope
Clearer audience
50% lower budget needed
We defined user personas early and used them throughout. They kept the team focused on real needs, not guesses.
Another client came to us with an early-stage concept.
Discovery showed the risks were too high and the market fit wasn’t strong.
Instead of pushing ahead, they walked away. That decision saved months of effort – and their budget.
Discovery helped them decide notto build. And that’s valuable too
Then there’s the cautionary tale.
One client decided to skip discovery and jumped straight into design and development.
The result? A series of problems that slowed everything down:
Unnecessary delays
Constant reprioritization
Blown timeline and budget
They had to fix problems that could’ve been avoided with a few weeks of discovery.
What these projects taught us: discovery shapes outcomes.
It sharpens your decisions, cuts unnecessary work, and keeps everyone on the same page.
Whether you move forward, change direction, or stop entirely, it helps you do it for the right reasons.
And that alone makes it worth doing.
How DECODE runs product discovery: FAQs
Most discovery projects run between 8 and 12 weeks.
That gives us enough time to cover user research, feature planning, wireframes, technical scoping, and prototyping.
If your focus is more technical, or you already have some materials prepared, it can move faster.
We adapt the timeline based on what you need and where you’re starting from.
Not at all.
Discovery is just as useful when you’re adding major features, planning a redesign, or upgrading an existing product.
It helps you successfully realign, spot risks early, and decide what’s actually worth building.
Whether you’re starting from scratch or building on top of something, discovery keeps future design and development focused.
Once discovery is done, you’ll have everything you need to move forward.
That includes a clear feature set, user flows, technical plan, clickable prototype, and more – depending on the scope.
We can continue into design and development with you, or hand over the documentation if you’re working with your own team.
Either way, we define the direction, test it, and scope it, so you’re ready to build no matter what.
Need discovery for your product?
Do you have a great idea for a new digital product but aren’t sure how to get it over the line? Or do you want a complete change in direction for your existing product?
You’re in the right place.
We’ve helped dozens of companies validate ideas, reduce risk, and build products with real traction.
Our team knows how to adapt the process to your stage, your goals, and your budget.
And we’re ready to help you figure out what to build and what to skip.
If you’re curious about how discovery could work for your product, feel free to reach out. We’ll walk you through it.
Ivan is truly passionate about what he does. In his role as Lead Product Manager, his strength is shaping products that not only meet market needs but also wow their users. And with over a decade of experience at software companies and startups, he knows all the ins and outs of building successful products.
In his spare time, he enjoys staying active, whether it's hitting the gym, playing sports, or hiking. His dream office? A terrace in Komiža on the island of Vis, taking in the warm Adriatic sun.
