Chad Walters, industrial designer and global med device consultant. For more than two decades, Chad has worked at the intersection of user research, brand language, and product development — primarily in med devices, where understanding the context of use is as critical as any mechanical specification. What makes his perspective worth reading: he's spent a career sitting at the table with engineering teams who'd rather just build, and he's learned how to make the case for getting the front end of product development right before the back end begins.
If I just roll in and say, here's what I think we should do. Trust me - that's not a story. That's you trusting me.
In this episode:
Why industrial design is less about aesthetics and more about resolving the tension between user needs, business requirements, and technical feasibility and why that distinction matters before the engineering team is fully ramped
One assumption equals one unit of risk: how Chad traces every component decision - down to a single PCB resistor - back to a user or business need, and what happens when teams skip that step
How to prototype to the question: why $3 in lumber and 30 minutes answers the same question as a day in CAD, and when the expensive prototype is actually the right call
Storytelling as a trust-building tool and why presenting the arc from challenge to failure to solution changes the conversation with clients more than any polished conclusion slide
Why aesthetic choices aren't personal preference: visual brand language is traceable to the business, and "purple and swoopy" means something specific if you know what to look for
Bonus Content:
A Typical Trade Show Both Pitches Their Products. Engineers are Looking for Proof.
S7E16 Chad Walters | Constraints, Iteration, & Industrial Design in Product Development
Chad Walters is an industrial designer and global med device consultant with 20+ years developing products where user needs, business requirements, and technology have to resolve to something a human being can actually use. In this episode, he explains what industrial design actually is and why "making it look nice" is the smallest fraction of the job. He covers what happens in the early ambiguous phase of product development where the most important decisions get made, why one unit of assumption equals one unit of risk and how to trace every component decision back to a user or business need, how to prototype to the question rather than to the solution, and why telling the story of your work builds more client trust than presenting your conclusions. For engineers who have worked alongside designers or anyone in early-stage product development, this episode reframes what effective collaboration between design and engineering looks like before the hard design work begins.
>If YouTube isn’t your thing, check out this episode and all of our past episodes on Apple, Spotify, and all the rest.
📣 PDX 2026 - Built on a Different Psychology
Most trade shows are built around exposure. PDX is built around trust.
There's a reason engineers walk past 90% of booths without stopping and it has nothing to do with your product. Salesperson avoidance is a documented behavioral response. Engineers are trained skeptics. A three-minute pitch from someone with a financial interest in your decision is, in their framework, weak evidence.
PDX changes the format. Exhibitors run short, hands-on training sessions at their booths throughout the day. Engineers arrive in learning mode, not avoidance mode. The psychological contract is completely different and so are the conversations.
From exhibitors who were there in 2025:
"The training session brought us attention and gave us a commitment from the attendees to spend more than a few minutes at the booth." - Trimech
"The small group conversations made for better engagement than simply standing in front of a booth watching people walk by." - Spanner
"Our team connected with the exact people we're building for - manufacturing leads, heads of ops, mechanical engineers." - Quarter20
PDX 2026 - October 20–21 · Mesa Convention Center · Arizona
Booth selection is first come, first served. Many are already reserved.
Contact us using the link below or register directly on our website
Tell the Story of How You Got There - Not Just the Answer
The instinct when presenting work to a client is to skip to the conclusion. You've done the work, you know what should happen next, and presenting the answer feels efficient. Chad Walters argues that instinct is the exact mechanism that erodes trust rather than building it.
If I just roll in and say, here's what I think we should do. We should do this. Trust me - that's not a story. That's you trusting me. Now maybe we've worked together forever and you just trust anything I say, and that's fine, but that's generally not the case.
The alternative isn't a longer presentation. It's a different structure: show the problem you were handed, the tests you ran, the thing that broke, and what you learned from it. Three slides can carry a story if those slides track the arc from challenge to failure to solution.
If you've got a picture of the broken thing, whatever it is and that's how that informed this next prototype. This is how we fix the problem. You're bringing them along. Here's the problem, here's the story, here's how we came up with the solution.
What makes this practical for engineers: the storytelling starts during the work, not at presentation time. When you break something in a mill, you take a picture. When a test fails, you note why. By the time you're presenting, the story already exists - you just need to sequence it.
Once you learn the value of telling a story to bring people along, you'll start thinking about it as you're doing work. You break that in a mill. Oh, better take a picture of that.
The ROI, Chad says, is compounding trust. Not just confidence in a single conclusion, but the kind that eventually gets clients asking "what should we do?" rather than cross-examining every decision.
A Typical Trade Show Both Pitches Their Products. Engineers are Looking for Proof.
The engineer who needed exactly what you're selling walked past your booth - not because the product was wrong, but because nothing in the first two seconds gave him a reason to stop. A specific story that shows how you got to a solution - including what broke before you got there - stops more of the right engineers than any benefits statement, and leaves behind something a demo never can.
If you exhibit at engineering tradeshows, this is worth the read.
Read the full article on The Wave.
When Your Machine Shop Says No
Last year, a customer couldn't find a shop willing to make their part. Difficult material, tight tolerances, small quantity.
We tested our internal supply chain. Made the parts ourselves. Sent them as a surprise.
They worked perfectly. That customer has ordered hundreds more since.
Now available: custom machined parts with Pipeline engineering oversight, pricing that outperforms domestic shops, and the same supply chain we trust for our own work.
Want to learn more? Contact us at the link below: