4 Industries Being Changed by IoT Whos Getting Hit the Hardest

A sensor the size of a thumbnail can now relay a patient's heart rhythm, a lorry's wheel temperature, or the CO₂ level in an office to a dashboard on the other side of the world. That is the basic promise of the Internet of Things, and across four industries it is already being delivered. But the hardware is the easy part. The harder problem is the experience wrapped around it.

The interface still has to work even when the user is stressed, distracted, or physically constrained.

IoT puts digital products into contexts designers have never had to design for before: a driver who has just hit a barrier, a patient waking at 3am to a worrying alert, a warehouse operative in a cold room with gloved hands. These are not controlled environments. The user is stressed, distracted, or physically constrained, and the interface still has to work. According to IoT Analytics, there will be over 27 billion IoT devices worldwide by 2025. The scale tells you how widely this has spread. What it does not tell you is how many of those devices are surrounded by experiences that actually serve the person using them.

The four industries below are among those most visibly reshaped by connected hardware. Each one brings a different kind of design challenge, and the stakes in each are high enough that getting the experience wrong has real consequences for real people.

Healthcare: When Patient Monitoring Leaves the Clinic

Wearable health devices have moved monitoring out of hospitals and into everyday life. A patient with a cardiac condition no longer needs a ward to track their rhythm. A person managing diabetes can see their glucose trend on a watch. The data is richer than anything a clinic visit could produce, and the potential for early intervention is real. Deloitte estimated that wearables used in preventive care and high-risk management could save over $200 billion in the US by 2050.

But continuous monitoring creates a new problem: alert fatigue. When a device flags every minor deviation, users start ignoring everything, including the alerts that matter. The interface around the sensor has to make judgements about what to surface, when to surface it, and how urgently. Get that wrong and the device becomes noise.

The emotional context problem

Healthcare IoT also surfaces an issue we see across stressed-user contexts. Someone woken at 3am by a device alert is not in the same cognitive state as someone reviewing their health summary over breakfast. The same screen has to work for both moments, and designing for the calmer one while ignoring the urgent one is a mistake that only shows up in real use, not in a usability session. Testing in a lab, where nobody is actually unwell and nobody is actually frightened, produces feedback that is rational and considered. Real use is neither of those things.

The gap in patient-monitoring apps

There is also a coverage problem. Research published in PMC / NCBI found that only 5% of mobile health apps reviewed provided support for patient monitoring of opioid use disorder, highlighting how unevenly IoT-connected care has spread across conditions. The technology exists. The products to support it, with the emotional and contextual intelligence they require, are far behind.

Manufacturing: When the Factory Floor Becomes Unpredictable

Industrial IoT has changed what factory managers can see and when they can see it. Sensors on machinery detect temperature shifts, vibration anomalies, and output irregularities before they become failures. Predictive maintenance, the ability to service a machine before it breaks rather than after, is one of the clearest productivity gains connected sensors have delivered.

The design challenge here is usually not the interface on the factory floor itself. It is the dashboard, the alert system, and the reporting layer that sits above it, and which a maintenance manager or plant director reads on a screen in an office or on a tablet walking the line. That person needs to understand at a glance which signals require action today and which can wait. An interface that presents everything at equal weight forces the reader to do the triage that the product should be doing.

Cognitive load under operational pressure

Our work on the BMW fleet accident reporting app illustrated how badly things go wrong when a stressed user is handed a complex interface. The original app asked accident victims to record damage, fill forms, and upload photos with no guidance on what angles to take or what information was actually needed at the scene versus later. People simply did not complete the forms properly. The interface expected rational, methodical behaviour from someone who had just had a crash.

The redesign separated what the app needed immediately from what could wait. It introduced a visual diagram of the vehicle where users tapped the affected areas rather than describing damage in text, and replaced typed claim forms with voice recordings for witness statements that could be transcribed later. The information collected improved substantially because the format matched what a distressed person can actually do.

When designing IoT alert systems, test with users who are mid-task or time-pressured, not sitting calmly at a desk. The gap between those two states is where most interface failures live.

The same logic applies on a factory floor. An operative in a noisy environment with limited time to respond to a sensor alert needs a different interface than the one designed for a manager reviewing a weekly report. IoT products in manufacturing often serve both audiences and rarely design for either one well.

Transport and Logistics: When Fleets Operate Beyond the Depot

Real-time vehicle tracking, route optimisation, and live delivery status have changed what customers expect from logistics. A parcel that cannot be tracked is now a frustration, not a norm. Behind the customer-facing layer, fleet operators now have visibility over every vehicle they run, and the data volume that comes with that visibility is substantial.

The design problem in logistics IoT is often one of information architecture. How do you show a fleet manager 200 vehicles, their live locations, any active alerts, and the status of that day's deliveries, without producing a screen that is overwhelming? The data is all legitimately useful. The challenge is structuring it so that the right operator sees the right signal at the right moment.

The data is all legitimately useful, but the challenge is surfacing the right signal at the right moment.

Real-time visibility also changes what happens at the last mile, which can account for up to half of total shipping costs, according to Packagex. Route optimisation tools that use live traffic and delivery confirmation data can reduce kilometres driven by up to 15%, according to Software Mind. But the driver using the navigation interface is often under time pressure, unfamiliar with an area, and unable to give the screen sustained attention. Designing for that person is a different problem than designing for the dispatcher watching the same data on a large monitor in a warm office.

Offline resilience matters

On a travel product aimed at younger backpackers visiting off-grid locations, we rethought the entire architecture around connectivity constraints. We worked out what information could be stored offline, what had to remain online, how to queue actions taken without a connection and replay them once reconnected, and how to minimise the data moving between the app and the server. Anything that could be baked into the product was. Logistics fleets operating in rural or underground environments face the same constraint, and very few fleet management products are built with offline resilience as a first principle rather than an afterthought.

Property and Real Estate: When the Building Becomes the Product

Smart building technology has turned physical spaces into data-generating environments. Access control, energy management, air quality, occupancy sensing, and maintenance alerts are now all digitally managed in premium commercial and residential developments. For the people living or working inside them, the interface to all of this is usually an app, and that app is often the primary way they experience the building itself.

We worked on a concierge app for a premium property development, and the research uncovered a problem the client had not originally framed. The brief was to give residents digital access to everything the building offered so they would not need to speak to the concierge. What the focus groups showed was that the core problem was communication, specifically residents not knowing each other and not building any sense of community. Digitising every concierge task would have made that worse, not better.

Automating the mundane to free the human

We pushed back against the original brief and shifted the product strategy. Rather than replacing human interaction with digital transactions, we used the app to automate routine and administrative tasks, which freed the concierge and residents to have the kind of genuine conversations that build a community. We gave each concierge a profile in the app that listed personal interests, explicitly inviting residents to talk to them about those subjects. Residents could also see who their neighbours were and what they were interested in. The technology created the conditions for human connection rather than substituting for it.

When a connected building app is underperforming, run research into what residents actually need from the space before assuming the interface is the problem. The brief and the real problem are often not the same thing.

IoT in property creates a similar temptation across the industry: to instrument everything and surface all of it to the resident. A smart home app that shows air quality, boiler pressure, energy consumption, parcel delivery status, and access logs on a single screen is technically impressive and practically exhausting. The design job is to decide what a resident genuinely needs to see and when, and to leave everything else in the background until it matters.

Why Connected Environments Break Traditional Customer Experience Models

Traditional digital product design assumes a user who is sitting down, has reasonable bandwidth, and has chosen to engage with the product. IoT removes each of those assumptions one by one. The user might be driving, lifting, monitoring a patient, or managing a building fault. The connection might be intermittent. The engagement might have been triggered by an alert rather than a deliberate choice to open an app.

The standard customer journey map does not accommodate this. A journey map describes steps through a product, but IoT products often interrupt users rather than being visited by them. The experience design question shifts from "how do we make each step pleasant?" to "how do we make the interruption appropriate?" That is a fundamentally different problem.

Context inference replaces explicit input

One approach we use is inferring the user's emotional and situational context from what we know about the use case, rather than asking them to tell us. A resident receiving a furniture delivery alert is almost certainly stressed about the logistics of a move. The app does not need to ask how they are feeling. It knows, because it knows what is happening. That inference can shape what the interface surfaces and how it communicates.

The same principle applied to the vehicle accident reporting redesign. Rather than waiting for a stressed driver to navigate to an accident reporting function, the app used accelerometer data to detect a sudden stop after movement and proactively asked whether the user had been in an accident. The interface came to the user, in the right moment, with the right question. That is a different design model than the one most digital products are built on.

Designing for Users in Contexts You Cannot Control

The most persistent design error in IoT products is testing in conditions that do not match real use. A logistics interface that looks clear in a usability session may be unusable on a phone screen in direct sunlight with one hand on a trolley. A health monitoring alert that reads as helpful in testing may feel alarming at 3am. The gap between lab and reality is always present in product design, but IoT widens it considerably because the range of real-use contexts is so large.

The same principle applies to financial moments, where we have found that users behave very differently when real money is at stake compared to a test scenario. On a travel booking product, we initially wrapped the platform's Stripe booking fee into the total price, reasoning that a single clean figure was simpler. What live behaviour showed was that users expected to see a platform fee as a separate line item, because that matches how they understand apps to work. By not showing it, we inadvertently created a fear that a hidden charge would appear later. Breaking the fees out explicitly increased confidence even though users were seeing more information, not less.

Build a short list of the most stressful real-world moments your product will be used in. Design for those moments first, then check the calm-state experience still works.

IoT design has to account for the full range of contexts a device will operate in. That means identifying the worst-case scenario, the most stressed, most distracted, least connected user, and treating that as a design constraint from the start, not an edge case to address in a later release.

• Define what the product must do offline before deciding what it will do online.
• Separate what information is needed immediately from what can wait until the user is calm.
• Use context inference, such as location, device data, or known use case, to reduce what you ask of the user at difficult moments.
• Test in conditions that resemble real use, not controlled lab environments.

Conclusion

IoT is a new set of constraints on an existing category of product. The sensor, the connection, and the data are all means to an end. The end is a person who needed something and got it, without having to think too hard about how. The industries taking the biggest hits from connected technology are the ones where that experience layer has lagged behind the hardware.

Healthcare, manufacturing, logistics, and property are all industries where getting the experience wrong has consequences beyond a bad review. a resident who never opens the building app because it shows them things they do not care about: these are predictable outcomes of design that prioritised capability over context.

The four industries explored here share a common design problem: the user is not where we imagined them to be, in the emotional state we assumed, with the attention we expected. Solving that problem starts before the first screen is drawn, with a clear-eyed account of the contexts the product will actually live in. If you are building or rethinking an IoT product and want to work through what that looks like in practice, let's talk about your connected product.

Frequently Asked Questions