Hardware is Just Software in Slow Motion: Why Early Prototypes Beat Perfect Plans | Ebele Okochar and Pete Oliver-Krueger

In this episode, Chad Jackson sits down with Ebele Okochar and Pete Oliver-Krueger, co-founders of Organizational Mindset Mapping (OMM), a coaching and training firm specializing in transformation for manufacturing and hardware companies. Together, they make a compelling case that Agile isn't just for software — and that the biggest breakthroughs in hardware development come from applying its core principles in ways most engineering organizations have never tried.

Ebele offers a framing that cuts right to the heart of the skepticism: "Hardware is just software in slow motion." Pete and Ebele walk through IDD — Industrialization Driven Development — a framework they developed with colleague Jim Dato, building on hardware Agile pioneer Joe Justice's work. IDD gives teams a system-level view from deployment all the way back to initial design, helping them identify what to build now, what to defer, and where the critical risks live.

The episode's most striking segment covers early prototyping. When OMM pushed a resistant client to build before designs were complete, the team uncovered three major problems within a month — a software-hardware integration failure, a materials issue, and customer feedback that eliminated an entire feature the engineering team had invested significant effort building. All discovered in month two, not month twenty-four.

Pete and Ebele also challenge the industry's "digital first" trend, arguing physical and digital prototyping should happen in parallel. They discuss cross-functional teams, backwards process mapping, and how a department full of Agile resisters ultimately came around when they recognized the approach as the collaborative, hands-on work that drew them into engineering originally.

Topics covered:

• IDD and why hardware needs its own Agile framework
• "Hardware is just software in slow motion" — and what that means in practice
• What early prototyping revealed that a traditional timeline would have buried for years
• Physical vs. digital prototyping — why it's not either/or
• How cross-functional teams cut 3-year timelines to 18 months
• The V-model vs. continuous verification
• Why how you introduce change matters more than which change you introduce