Product Discovery: Specs Yesterday? Not So Fast.

Product discovery is the evidence-informed process of reducing uncertainty by identifying problems worth solving and validating solutions before extensive development, ensuring that what gets built is both desired by users and technically feasible. This crucial phase in the product development process prevents wasted resources by confirming that real users want a proposed solution and that it can be designed to be valuable, usable, and viable. Effective product discovery integrates continuous learning and user research to avoid the pitfalls of premature specification, fostering a collaborative environment where engineers are essential partners, not just executors.

What is Product Discovery and Why It Matters

Product discovery is a continuous, evidence-informed process designed to reduce uncertainty by identifying problems worth solving and validating potential solutions before committing to extensive development. It directly addresses two fundamental questions: whether real users desire a proposed solution and if it can be designed to be valuable, usable, feasible, and viable. This process is distinct from product delivery, which focuses on producing value, as discovery prioritizes uncovering what creates that value.

Its importance lies in preventing wasted resources and ensuring that development efforts are directed toward solutions that genuinely address user needs and market opportunities. For instance, Swarmia's product discovery process for developer experience surveys confirmed a critical mass of existing customer feedback and market demand, validating the "what" and "when" before significant engineering investment. By involving engineers and designers early, product discovery fosters stakeholder buy-in and leverages their technical expertise to translate "pie-in-the-sky ideas" into feasible realities, avoiding costly reworks later in the product development process. This approach helps product teams avoid going down a path that leads to a dead end, ultimately speeding up product delivery by ensuring clarity and context from the outset.

The Pitfalls of "Specs Yesterday" Thinking

Many teams misunderstand product discovery, treating it as a discrete "phase" rather than a continuous process, often conflating it with "just-in-time spec writing." This anti-pattern is driven by a management instinct to keep engineers busy and show progress, leading to significant inefficiencies. When discovery is viewed as a pre-development phase, it often results in detailed designs and specifications being handed off to a separate delivery team. This creates a "waterfall-like" scenario where critical information and context are lost, leading to extensive back-and-forth communication and potential misinterpretations.

For instance, a spec might state "customers want to get to the other side," but without the context gleaned from user research, engineers might build a bridge over a small stream when the actual need was for a tunnel through a mountain. This premature solution design, without adequate user research and feasibility checks, often leads to building the wrong thing or an overly complex solution. Engineers, who possess deep knowledge of technological possibilities, are often only brought in during the delivery phase. This means their valuable insights into technical feasibility and potential solutions are overlooked during critical discovery stages, reducing their contribution to "about half their value." The most expensive way to learn what users want is often by writing production code, highlighting the need for early, iterative prototyping and continuous discovery involving the entire product team.

Engineers: Essential Partners in Product Discovery

Engineers are indispensable to effective product discovery, offering a unique and critical perspective that goes beyond mere implementation. Their deep technological knowledge allows them to generate some of the best solutions, understanding precisely "what’s possible with technology." For example, when exploring a user need like "searching for a specific movie title," a designer might focus on the user experience, while an engineer might identify a technical solution to improve recommendation algorithms, such as detecting different user types to prevent "all recommendations are for kids’ movies." This dual perspective from a product trio (Product Manager, Designer, Engineer) attending user interviews can lead to more robust product improvements.

Involving engineers early in the product development process, rather than just during product delivery, prevents costly "discovery boondoggles." They translate "pie-in-the-sky ideas" into feasible realities, actively participating in the ideation process and helping to create prototypes. These prototypes, ranging from whiteboard sketches to interactive mockups, are crucial for testing whether a proposed solution is valuable, usable, feasible, and viable without writing production code. This iterative approach, often seen in dual-track agile, ensures that risks are tackled proactively. By empowering engineers with context and involving them from the outset, product teams eliminate handoffs, reduce back-and-forth clarifications, and significantly speed up the overall product delivery process.

Integrating Discovery and Delivery for Speed

Continuous product discovery, when integrated seamlessly with delivery, is crucial for accelerating the product development process. A common pitfall is separating discovery and delivery into distinct phases or teams, which often leads to "waterfall-like" handoffs where critical information and context are lost. This necessitates extensive back-and-forth communication and clarification, significantly slowing down product delivery. For instance, a detailed specification document handed off to a delivery team without shared context often results in engineers having to stop work to clarify requirements.

By contrast, involving the entire product trio—Product Manager, Designer, and Engineer—in continuous discovery eliminates these wasteful handoffs. When those delivering the work, especially engineers, are empowered with full context from the outset, they can make informed decisions autonomously. This approach significantly reduces the time spent clarifying details during the delivery phase and minimizes miscommunication, preventing the team from building the wrong solution. Adopting a "dual track agile" approach ensures that discovery work, focused on fast learning and validation through prototypes, runs concurrently with delivery work. This allows risks to be tackled proactively during discovery, leading to a much faster and more efficient delivery of validated solutions.

Practical Techniques for Effective Product Discovery

Effective product discovery relies on actionable methods that validate solutions and secure stakeholder buy-in. Continuous user research is paramount, involving ongoing customer interviews to uncover problems and validate potential solutions. This ensures the product team is always informed by real user needs, moving beyond mere confirmation-seeking interviews.

Prototyping plays a critical role in testing hypotheses without committing to full-scale development. Prototypes can range from low-fidelity whiteboard sketches to interactive mockups, allowing teams to quickly assess whether a proposed solution is valuable, usable, feasible, and viable. For example, an interactive prototype demonstrating multiple portals for tailored communication can gather feedback from both customers and internal stakeholders. This iterative approach, where building to learn is prioritized, significantly reduces the cost of validating ideas.

Integrating discovery with delivery is best achieved through a dual-track agile approach. This framework allows discovery work, focused on rapid learning and validation, to run concurrently with delivery work. It ensures that risks are addressed proactively during discovery, leading to faster and more efficient product delivery. By involving the product trio—Product Manager, Designer, and Engineer—in continuous discovery, teams eliminate costly handoffs and empower engineers with the context needed to make informed decisions, ultimately accelerating the product development process.

Frequently Asked Questions

Conclusion

By integrating product discovery and delivery, and empowering your product trio with continuous learning, you can bridge the gap between engineering's need for clarity and the iterative nature of product development. This approach not only speeds up development but also ensures that your team is consistently building the right solutions for your users.

Sources & References

• Product Discovery: Why Most Teams Get It Wrong - Ainna
• 13 ways to free up time for Product Discovery | by Markus Müller
• Why Engineers Should Participate in Discovery
• Product Discovery Should Speed Up Delivery, NOT Slow it Down
• Requirements Elicitation in Modern Product Discovery – Requirements Engineering Magazine
• Software to Search and Discover Product Data - Engineering.com
• How we do product discovery at Swarmia | Swarmia
• [PDF] The Product Discovery Playbook 2.0 - Productboard
• How iterative Product Discovery helps you solve the right problem
• Product discovery and deciding what gets built - Scott Gartenberg