Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

The core loop of customer interviews, market research, prototyping (e.g., kitchen samples), and beta testing is universal. The process for developing a cheese powder at Kraft Heinz mirrors software development at DoorDash, proving the principles are medium-agnostic.

Related Insights

The 'Ideal Product Model' is a blueprint with four layers. It starts with the consumer world (Jobs to Be Done, Sensory Attributes) and cascades to R&D (Technical Mechanisms, Measures). This ensures every technical component directly traces back to a user need, allowing teams to strip out features that don't add value.

Launching experiments without prior customer interviews or market analysis is a waste of resources. The most effective experiments are designed to answer specific questions that arise from a solid research foundation, not to substitute for it.

Forget the linear waterfall or even the classic design loop. Dylan Field sees today's best product teams using a non-linear process, 'hopping' between ideation, design, prototyping, and code in any order. The key is the ability to start anywhere and move fluidly between these stages.

Experienced product leaders avoid relying on muscle memory or applying a standard playbook. Each company, product space, and problem is unique. The most effective approach is to first understand the specific context and then select or create the right tools and frameworks for that unique situation.

In AI, low prototyping costs and customer uncertainty make the traditional research-first PM model obsolete. The new approach is to build a prototype quickly, show it to customers to discover possibilities, and then iterate based on their reactions, effectively building the solution before the problem is fully defined.

Voice of the customer research is often insufficient. Adopt iterative innovation by quickly creating and demoing cheap prototypes—even computer simulations or animated concepts—to get constant, early feedback. This validates ideas in real-time.

De-risk new product initiatives by validating them directly with the market using low-fidelity prototypes like sketches. By building a following and an adoption list before development begins, you create undeniable proof of demand that can overcome internal resistance and ensure a successful launch.

Hardware startups must not wait for physical prototypes to get customer feedback. Steve Blank advocates for creating 'digital twins'—advanced, interactive simulations—that customers can use. This allows for rapid iteration and customer discovery, mirroring the agility of software development.

Instead of a traditional big-bang retail launch, Magic Mind first sold direct-to-consumer (D2C). This allowed for 150+ product iterations based on direct customer feedback, ensuring product-market fit *before* scaling into high-stakes retail channels, a strategy borrowed from software development.

The formal MedTech process of distinguishing Verification (testing against technical specs) from Validation (testing against user needs) is a powerful, practical framework for any product development. It creates a disciplined approach to ensure a product is built correctly and is the correct product for the user.

Product Development Frameworks Apply Equally to Physical and Digital Products | RiffOn