WHY DESIGN?

Why Design is an interview-led show about the real work behind physical products. It is not especially interested in design as surface polish. The strongest conversations stay close to the people making hard decisions about materials, mechanisms, money, regulation, teams, and users. One episode follows Felicity Boyce through impact-protection materials, factories, China trips, and the less glamorous side of making plastic responsibly. Another turns raspberry picking into a robotics problem where every field condition creates a new edge case. Sid Shaikh’s work at Fieldwork Robotics gives the show a concrete way to talk about learning systems, farm trials, and why lab testing is never the whole test. Rob Halifax’s Windfall Energy story shifts the lens to renters and people in flats, asking what clean-energy hardware becomes when it has to be both useful and visible at home. Dr. Liz McLaughlin’s surgical-device conversation brings in regulation, clinical feedback, and the pressure of improving a technology surgeons have worked around for decades. Dan Salisbury’s move into robotic lab systems gives the show one of its recurring questions: what happens when a designer has to prove their value inside an engineering-heavy startup. Tess Cosad’s fertility-care episode is more emotionally charged, because the product problem is tied to access, stress, medical risk, and being taken seriously while building. Mark Sanders brings an inventor’s view of affordability, simplicity, royalties, and the uneven income of original product work. Will Butler-Adams adds a business-leadership angle, especially around purpose, profit, patient growth, and refusing to chase volume for its own sake. Across these episodes, Why Design keeps pulling practical lessons from career turns that may have looked odd from the outside. It values people who say yes to uncomfortable responsibilities, learn from factories and users, and keep revising when reality contradicts the plan. The pacing is measured rather than hyped. Guests often carry the argument through detailed stories, while the questioning keeps nudging toward the lesson underneath. The show is especially strong when a technical problem becomes a leadership problem. It is also good at making industry-specific work understandable without flattening it. Listeners come away with a sharper sense of why hardware takes so long, why compromise can be dangerous, and why good product decisions are rarely only aesthetic. For builders, designers, engineers, and founders, it offers a grounded look at the gap between a promising idea and a product that earns its place in the world.