Get your free personalized podcast brief

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

An upcoming PDMA workshop connects two powerful frameworks. It uses customer outcome contradictions identified through Jobs-to-be-Done (e.g., "faster but cheaper") as the direct input for TRIZ (Theory of Inventive Problem Solving), translating the problem space directly into a structured solution space.

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.

Innovation flourishes when teams learn to hold opposing values in tension (e.g., risk vs. safety) rather than trying to resolve them into a single choice. Framing complex issues as paradoxes to manage unlocks creativity, whereas an 'either/or' approach stifles it.

Instead of rushing to solve a perceived problem, spend time questioning the problem itself—a process Dr. Seelig calls "framestorming." For example, the problem isn't designing a better suitcase; it's getting your belongings to a destination. This redefinition opens up radically different and more innovative solutions.

Walmart reframed planning around desired outcomes, not feature lists. This gave engineering teams the flexibility to innovate on solutions, increasing engagement and productivity, despite initial resistance from leadership accustomed to feature-based roadmaps.

Conventional innovation starts with a well-defined problem. Afeyan argues this is limiting. A more powerful approach is to search for new value pools by exploring problems and potential solutions in parallel, allowing for unexpected discoveries that problem-first thinking would miss.

Users often develop multi-product workarounds for issues they don't even recognize as solvable problems. Identifying these subconscious behaviors reveals significant innovation opportunities that users themselves cannot articulate.

When handed a specific solution to build, don't just execute. Reverse-engineer the intended customer behavior and outcome. This creates an opportunity to define better success metrics, pressure-test the underlying problem, and potentially propose more effective solutions in the future.

Before an innovation workshop, focus interviews on employees and customers who interact with the product daily, not just executives. Their ground-level insights are essential for defining the strategic 'white spaces' that will guide the workshop and ensure it addresses real problems.

Research across major companies shows that 71% of the time, a solution for a known customer need already exists internally. The primary barrier to innovation isn't a lack of solutions, but the inability for siloed departments to discover and connect existing capabilities with identified customer needs.

The work that makes an innovation workshop successful happens before it starts. Before the session, assign a clear owner for the outputs and create a rubric for evaluating ideas. This structure ensures that promising concepts are systematically advanced for investment, rather than dying on a whiteboard photo.