Your connected product can fail long before anyone opens the app. An iot customer journey map follows every step from purchase to retirement, so you can spot the gaps early. Start with the stages, then add questions to each one.
This guide is part of a wider look at iot user experience design, where journey mapping is one of several tools.
| Item | Value |
|---|---|
| Stages in the example IoT journey | Nine stages |
| Foundational IoT design tools named in the guide | Three tools |
| Where most customers eventually spend their time | App feature and usage stage |
| Layers in a service blueprint | Five horizontal layers |
| Date the IoT journey guide was last updated | December 2, 2024 |
These figures come from IoT For All’s journey guide and the GeekyAnts CX knowledge base. They can change, so check the source before you rely on them.
Why an IoT journey reaches beyond the screen
Many designers spend their time on the app, yet a connected product is also installed, handled and maintained in the physical world. The experience therefore starts well before the first login and continues well after the last tap, as IoT For All explains.
Your customer will not diagnose problems for you. If the product lags, they do not care whether a chip or a weak Wi-Fi signal is to blame, and they will simply conclude that the product doesn’t work.
A journey map keeps the whole team looking at one path instead of separate parts. It is one of the three foundational tools the same guide recommends, and it helps you surface gaps, risks and issues early rather than hearing about them on launch day.
The nine stages of an IoT customer journey
The example map in the IoT For All guide covers the full product life, from the first advert to the day a customer replaces the device. Most of its stages sit outside the app, which is exactly why a screen-only view misses them.

- Initial purchase and advertising
- Unboxing
- Installation
- Connecting
- Onboarding and initial setup
- App feature and usage
- Troubleshooting
- Maintenance
- Decommissioning or upgrading
The guide notes that the usage stage is where most customers eventually spend their time. That makes it tempting to polish only that stage, but the earlier steps decide whether anyone arrives there. Source.
What goes wrong at each stage
Early stages are physical, and small lapses there can end the relationship before the product ever works. The same guide offers these examples:
- Unboxing: unclear instructions about removing protective plastic lead to confusion at best and incorrect installation at worst.
- Installation: when the process sets no expectations, users are disappointed that they cannot install immediately.
- Connecting: a QR code in an “impossible-to-reach” spot on the device hurts the experience.
- Onboarding: a complex flow plus a weak Wi-Fi or cell signal can leave the user unable to finish setup.
The guide warns that a customer who cannot find the right QR code or follow the installation instructions may never experience the full feature set. Setup problems also leave the rest of the app unusable, because it cannot receive data from the devices. Both points are in the IoT For All guide.
Later stages are about staying power. For troubleshooting, the guide advises giving users directions, or better yet recommendations, so they do not walk away overwhelmed.
Maintenance matters just as much: if batteries need replacing every month and the device is hard to take apart, you will not keep customers for long. At the upgrade stage, letting people port their settings over via the app removes a real worry.
How to build the map with your team
The map works best as a shared working document rather than a design deliverable. Here is one simple way to run it:
- Lay the stages out as columns, including the hardware ones the app never shows.
- Under each stage, write the critical questions a designer should ask the team, which is how the IoT For All guide pairs its map.
- Mark every point where the experience depends on a physical object, a signal or a battery.
- Review the draft with product, hardware, software and data science together.
- Test the weak points with real tasks that span hardware and software.
Step four pays off beyond the map itself, because the guide says the process breaks down silos and builds the tight camaraderie that helps teams make delightful products. For step five, the same source says user testing must include scenarios and tasks that span both hardware and software features, and our overview of iot user research methods shows ways to run them.
A journey map shows only the customer’s view. If you also need the people, systems and handoffs behind each step, the approach in our iot service design guide is the natural next move.
Extending the map past the first purchase
Strategy for Industry’s analysis of consumer electronics argues that many journey maps stop too early. It says they often fail to map the post-ownership transition, which leads directly to churn rather than retention if mishandled, according to its customer journey analysis.
The same page says poor unboxing and setup experiences, such as confusing instructions or technical glitches, lead to high return rates, negative reviews and customer churn. It also suggests adding end-of-life touchpoints in the app or a web portal, covering trade-in, certified recycling or safe data wiping.
For a connected product, that means your map should end at a handover rather than a dead stop. Give the old device a clear exit and the new one a smooth start.
Frequently asked questions
What is an IoT customer journey map?
Show answer
It is a visual timeline of everything a customer meets with your product, from the first advert to retirement. What sets it apart is that physical steps such as packaging, mounting and battery changes sit alongside the app screens.
How is it different from an app user flow?
Show answer
A user flow tracks taps and screens inside the interface. A journey map widens the lens so the box, the install, the signal in the room and the support moment all count as part of the experience.
Who should help create the map?
Show answer
Bring in anyone who shapes the product, not only designers. The IoT For All guide names product, hardware, software and data science as the groups to involve, because gaps often fall between them (source).
Is a journey map the same as a service blueprint?
Show answer
No. According to the GeekyAnts CX chapter, a journey map shows the customer’s perspective only, while a blueprint connects customer actions to the infrastructure behind them. That is where hidden handoff and automation problems show up.
