Build IoT Products Your Customers Love—and Will Pay For

In the era of digital transformation, the Internet of Things (IoT) is often touted as the next revenue engine. Yet, a recent Cisco study shows that over 70% of IoT initiatives fail. The common thread? A missing, rigorous process for uncovering and solving real customer problems.

This article outlines proven product‑management techniques that let you discover pain points, explore how IoT can address them, and build solutions that are both profitable and sustainable.

Why Design Thinking Matters for IoT

IoT is a tool, not a strategy. Companies mistake the buzzword for a silver bullet, but customers buy solutions, not sensors. Design Thinking provides a structured way to translate customer needs into tangible products, ensuring you’re building what the market actually wants.

The three‑step framework I use in my IoT courses—Discovery, Ideation, and Validation—combines the rigor of Lean with the empathy of UX research. Below, I walk through each stage with concrete tactics and real‑world examples.

Discovery: Identify Genuine Customer Pain

Discovery is about asking the right questions, not inventing problems. In the problem space, you uncover what customers already struggle with and how IoT can help.

My approach involves three complementary research methods:

On‑Site Interviews

By observing users in their natural environment—be it a power plant, a manufacturing line, or a trucking yard—you capture insights that desk research can’t reveal. While coordinating visits can be logistically demanding, the payoff is high. In practice, visiting 10–12 qualified customers often surfaces clear, actionable patterns.

User Interviews (Remote)

When travel isn’t feasible, phone or video interviews expand your reach. Dr. Rob Adams recommends conducting at least 100 remote interviews to validate that a pain point is widespread and not an outlier. Books like Steve Portigal’s Interviewing Users provide structured techniques for uncovering deep insights.

Surveys

Surveys convert qualitative findings into quantitative validation. Once you have a hypothesis from onsite or remote interviews, deploy a survey to test its prevalence across a larger audience. This scale‑up confirms whether the problem is worth pursuing.

During discovery, collaborate across disciplines—UX, engineering, sales, and marketing—to surface ideas early and secure buy‑in.

Ideation: Generate IoT‑Enabled Solutions

With validated problems in hand, move into the solution space. The goal is to brainstorm ideas that align with your company’s core strengths and strategic priorities. For example, if you’re a trucking‑industry provider and discover that fuel costs dominate customer pain, consider how sensor data could reduce consumption.

Structure brainstorming sessions with a cross‑functional team. Guide the conversation with a simple prompt: “If we had sensors in our customer’s trucks, how could we use that data to cut fuel expenses?”

Sample ideas might include:

• Tire‑pressure monitoring to prevent fuel‑wasting deflation.
• Engine‑sensor data to detect and correct inefficient driving behaviors.
• Driver‑performance dashboards coupled with incentive programs for fuel‑efficient routes.

Remember, innovation lies in how you implement these ideas—sensor placement, data analytics, machine‑learning models, and the business model that reduces friction.

Validation: Test Desirability, Viability, and Feasibility

Validate your concept by answering three core questions:

• Desirability – Does it solve a real customer need?
• Viability – Can your business model generate sustainable revenue?
• Feasibility – Are the technical, regulatory, and operational requirements within reach?

Many IoT projects stall here because companies lack a structured validation framework. My IoT Decision Framework helps you evaluate each critical dimension—UX, data strategy, business model, technology stack, security, and compliance—before moving to development.

Anticipating Pushback

Adopting a discovery‑ideation‑validation loop may feel slow to some stakeholders. However, the alternative—jumping straight into engineering—often results in costly failures. By investing a few extra months and budget upfront, you reduce time‑to‑market, lower development costs, and dramatically increase the likelihood of success.

The Bottom Line

Design Thinking offers a disciplined, customer‑centric path to building profitable IoT solutions. Iteration is key: iterate quickly, validate rigorously, and align every decision with customer value. When executed well, this approach can save millions by preventing product missteps and accelerating innovation.

*Photo by Alvaro Reyes on Unsplash