This article is part of a five-part series on product discovery best practices.
This best practices article is part five of a five-part series on product discovery. In the previous article, you used customer research and feedback to identify the strongest opportunities, prioritize ideas, and connect customer evidence to your roadmap.
But product discovery does not stop once you identify the right opportunity. You still need to test whether your proposed solution works for customers before you move into delivery. Prototypes and proofs of concept help you explore possible approaches, gather feedback on realistic experiences, and refine the solution before engineering begins building.
In this article, you will learn how to turn a defined feature into a testable solution, create interactive prototypes, build a proof of concept, gather feedback in context, and prepare a validated solution for delivery.
Click any of the following links to skip ahead:
This article shows how to turn customer insight into testable solutions and decide what is ready for delivery. Use Aha! Roadmaps to define features and create prototypes. Use Aha! Builder to turn those prototypes into proof-of-concept experiences and collect feedback in context.
Step 1: Bring potential solutions to life
Start with a well-defined feature, then turn the problem into a few possible solution paths. This gives the team a clearer way to evaluate trade-offs and decide what to test first.
Review the supporting evidence: Pull together the research, feedback, and feature details in one place. Use Elle (the AI assistant) to clarify the outcome and document the assumptions you still need to test. This gives you a clearer starting point before solution work begins.
Explore alternative approaches: Sketch alternative workflows and concepts on whiteboards so you can compare directions side by side. Visualizing more than one approach makes trade-offs easier to discuss and helps you choose a path worth turning into a prototype.
Bring in the right perspectives: Bring product, design, engineering, sales, and support into the conversation early enough to shape the direction. Each group sees the problem from a different angle. Together, these perspectives help you pressure-test the concept before moving it forward.
Record the decision: Capture which concept the team wants to pursue, why it stands out, and which questions are still open. That record gives everyone a shared reference point when the work moves into prototyping.
Step 2: Create interactive prototypes
Once the team has chosen a direction, turn the concept into something people can click through and react to. A lightweight prototype shows you more than a discussion can. You can see where the flow makes sense, where it feels awkward, and what needs to change before you spend more time building it.
Create an interactive prototype: Use Elle to generate a prototype in Aha! Roadmaps. Once the team can click through the idea, weak spots become easier to see.
Start with the simplest version: Build only what you need to answer the question in front of you. That keeps the work focused and helps you learn what you need without getting pulled into details that do not matter yet.
Review it together: Share the prototype with product, UX, design, and engineering while it is still easy to change. Those conversations usually reveal awkward steps, missing context, or a simpler way forward.
Refine as you learn: Update the prototype as feedback comes in, then use the next version to answer the next question. Each revision should make everything clearer and move it closer to a proof of concept.
Step 3: Build a proof of concept
Once the prototype is ready for customer testing, move it into Aha! Builder to build a proof of concept. This takes your prototype further by letting you create a database-backed experience that feels more complete. Customers can enter information, move through real steps, and respond to something that behaves much more like the product you plan to deliver.
Focus on one important question: Keep the proof of concept centered on the part of the experience that carries the most risk or uncertainty. A tight scope makes it easier to tell whether the concept is solving the customer problem.
Make it feel real enough to validate: Use Elle to turn the prototype into something closer to the real product. Match your branding, shape the workflow around a real use case, and add the data, states, and interactions customers need to move through the experience in a natural way.
Prepare for customer feedback: Be clear about what you want to learn before customers use it. Write down the assumptions you are testing, the questions you need answered, and the kind of feedback that would show the concept is ready to move forward.
Step 4: Gather feedback in context
Once customers can interact with the proof of concept, collect feedback while the experience is still fresh. This helps you understand what feels clear, where people get stuck, and whether the concept solves the problem it was designed to address. The goal is to gather input you can use right away to improve the experience.
Collect feedback in context: Add the feedback widget to your Aha! Builder proof of concept so customers can share reactions while they are using it. Feedback tied to the experience is often easier to understand because it reflects what people noticed in the moment.
Follow up when you need more detail: Use a study or customer interviews in Aha! Discovery when you need more context than written feedback can provide. A smaller set of conversations can help you understand why people responded the way they did.
Capture what you learn: Record patterns, open questions, and useful reactions in highlights, clips, or a note. Saving the details in one place makes it easier to review the feedback and decide what to change.
Revise and test again: Update the proof of concept based on what you learned, then share it again if important questions are still open. A second round often helps you confirm that the changes improved the experience instead of introducing new issues.
Step 5: Prepare the solution for delivery
Once customers have responded to the proof of concept, you can decide whether the solution is ready to move into delivery. Validation will not answer every question, but it should give you enough clarity to judge whether the experience works, what still needs refinement, and what design and engineering need next.
Review validation results: Look at customer feedback, interview findings, and proof of concept results together. Use that evidence to decide whether the solution solves the right problem, where customers still struggled, and what still needs to change.
Confirm what is ready to build: Review the open questions, remaining risks, and unresolved assumptions before handing the work to engineering. This helps you separate what is clear enough to move forward from what still needs another round of refinement.
Document what the team validated: Record the key findings, validated assumptions, and important trade-offs in the Aha! Roadmaps feature, requirements, or notes — wherever you keep implementation context. This shows your team what was tested, what everyone learned, and how the solution should work.
Prepare design and engineering to build: Use the prototype, proof of concept, and supporting research to show how the experience should work in practice. This gives the team a clearer picture of the flow, the key interactions, and the decisions already made before implementation begins.
Product discovery works when you stay close to customers, learn as you go, and let evidence shape your decisions. Across this series, you have seen how research, feedback, opportunity analysis, and validation work in tandem. Together, these practices create a repeatable discovery system that helps product managers make better decisions and stay closely connected to customer needs.