#014: Why Your IoT Project Still Hasn’t Taken Off

https://is1-ssl.mzstatic.com/image/thumb/Podcasts221/v4/01/70/bb/0170bbb0-9264-d141-bf56-c375c8195774/mza_14067636312550255.jpg/600x600bb.jpg

Coredump Sessions

Memfault

18 episodes

5 days ago

Coredump Sessions is a podcast for embedded engineers and product teams building connected devices. Hosted by the team at Memfault, each episode features real-world stories and technical deep dives with experts across the embedded systems space. From Bluetooth pioneers and OTA infrastructure veterans to the engineers who built Pebble, we explore the tools, techniques, and tradeoffs that power reliable, scalable devices. If you're building or debugging hardware, this is your go-to for embedded insights.

Technology

RSS

All content for Coredump Sessions is the property of Memfault and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

Technology

https://d3t3ozftmdmh3i.cloudfront.net/staging/podcast_uploaded_nologo/43339182/43339182-1744206360534-53342e1aed2db.jpg

#014: Why Your IoT Project Still Hasn’t Taken Off — And How to Fix It

Coredump Sessions

57 minutes 4 seconds

3 months ago

#014: Why Your IoT Project Still Hasn’t Taken Off — And How to Fix It

In today’s Coredump Session, the team takes a hard look at why some IoT projects stall before they ever hit scale. From organizational missteps to product-market fit challenges, they explore the hidden forces that derail even technically sound products. You’ll hear candid insights on why being “connected” isn’t enough—and what it really takes to succeed in IoT today.

Key Takeaways

The biggest blockers for IoT teams aren’t always technical—they’re organizational, strategic, and systemic.
Shipping a connected device doesn't guarantee product-market fit, especially if it's missing the right workflows or visibility.
Engineers often build what's technically possible instead of what's valuable for the business.
Collecting data from devices is table stakes—but what matters is how you use that data to drive action.
Many teams lack a clear owner for post-deployment success, leading to blind spots in field performance.
“Observability” should go beyond crash logs and include signals that help prioritize engineering work.
Product-market fit isn’t static—it has to be reevaluated and maintained across the device lifecycle.

Chapters:

00:00 Introduction to IoT Challenges

01:54 Afzal’s Journey in IoT & Early Expectations

04:11 The 500K SIM Card Mirage

08:10 Why IoT Projects Stall: Internal Resistance & Misaligned Incentives

14:25 Rethinking the “IoT” Label: Lessons from Pebble

17:28 When Good Tech Still Fails: The Organizational Blindspot

20:43 Field Reality Check: Why Real-World Feedback is Critical

26:00 Who Owns It? Accountability After Launch

29:07 Designing for Fault Tolerance in Connected Devices

32:52 Fragmentation in IoT: Meeting Diverse Customer Needs

37:27 Niche Focus as a Winning Strategy