Chapter intro
Why It Exists
Developing new products and the processes that deliver them is hard, messy, and often frustrating. Many organizations try to solve this with more templates, more milestones, or more "best practices" — and still end up with late changes, stressed teams, and disappointed customers.
This playbook exists to offer a practical, visual way to apply Lean Product & Process Development (LPPD) to real work. It gives you a shared language, a handful of core mental models, and a set of plays you can use to design better products and better development systems — without adding more bureaucracy.
Section 1.1
Who This Playbook Is For
This playbook is written for people who shape product and process development. You don't need to be an LPPD expert to use it — only curiosity, a willingness to experiment, and a concrete development challenge to work on.
Leaders
Who own product families, portfolios, and value streams, and want a more reliable way to create customer value.
Chief Engineers & System Owners
Accountable for end-to-end performance and need to align many functions around a clear direction.
Cross-Functional Team Members
Engineers, designers, product managers, manufacturing, quality, supply chain, service — who want a better way to collaborate.
Change Agents & Coaches
Who support LPPD adoption and need simple visuals and language to bring others along.
Section 1.2
How to Use This Playbook
There are two main ways to use this playbook — pick whichever fits where you are right now.
Read it end to end once
Build a shared mental map and vocabulary with your colleagues before diving into specific plays.
- Start with the Foundations section to understand the principles and core mental models.
- Then skim each later section (Strategy, Discover, Design, Flow, Validate) to see how the foundations show up as concrete plays.
- This gives you and your team a common language going in.
Jump directly to a play that matches your current problem
Already have a live challenge? Go straight to the section that fits and pick one play to try.
- Identify the situation you are in — e.g., "We lack clarity on the customer and problem," "Our concepts keep changing late," "Our development pipeline is stuck."
- Go to the section that best fits and pick one play to try with your team.
- Use the "Foundations" call-outs on each play to see which principles and mental models you are exercising.
A few working agreements
- Treat each play as something to try and adapt, not a rigid method.
- Always connect the play back to a real product or process challenge, not an abstract exercise.
- After using a play, pause briefly as a team: What did we learn? What would we change next time?