The Internet of Things Needs Design, Not Just Technology


Gartner Research predicts that the typical family home will contain as many as 500 networked devices by 2020. Similarly, Ericsson forecasts 50 billion connected “things” by the same date. Reaching these lofty projections over the next four years, however, will require a fundamental reorientation in the way that technologists and product designers work together to create successful “connected” personal devices and home appliance products. This evolution to “Internet of Things (IoT) 2.0” will be difficult for many companies to achieve — not for lack of technological expertise but because they’ll fail to recognize the value of design in connected product development.

Machine-to-machine (M2M) connectivity — the forerunner of consumer-focused IoT — has been around for decades. Overwhelmingly, those IoT 1.0 applications pushed technology to address B2B market requirements.

Product design considerations in the IoT 1.0 world are not critical to persuading customers to adopt offerings. Enterprise IoT buyers seldom require great design, because most often the buyer is not the product’s end user. Fleet logistics companies, for example, monitor the condition and location of their vehicles. Their developers focus on meeting operational and environmental requirements, caring little about the physical appearance or user experience of a dashboard- or engine-compartment-mounted device that monitors vehicle data.

Read Also:
IoT and Big Data – Who Owns All the Data?

However, as the application of IoT expands to a broader range of commercial opportunities, enterprise B2B applications have become B2B2C. Fleet vehicle operators now directly engage with IoT devices that can measure their physical condition as well as their driving behavior. As B2C companies rush to exploit new IoT applications, pushing technology to potential end users no longer works. Increasingly, the pull of user experience will drive market demand, and product design will be critical to getting consumers to adopt offerings in this new IoT 2.0 world.

The fundamental principle in the IoT 2.0 era is that IoT is not the end product. The IoT is not an iPhone, a networking application, or a wearable device. Customers do not buy IoT. In fact, studies suggest that most consumers are unaware of what IoT is or does. IoT connectivity can enhance a product’s value, but it can never serve as the rationale for the customer purchase.

Read Also:
The Data-Driven Case for Vacation

This misunderstanding of IoT’s role is contributing to a growing list of commercial failures by product manufacturers. Their excuses for missteps include security issues, complexities of managing product life cycles, and lack of interoperability. But most often the root cause is that IoT companies with traditional B2B business models and B2B2C distribution channels have been pushing IoT technology rather than addressing the pull of customer needs and tastes.

One notable example of this type of IoT failure involves the demise of Revolv, a home automation hub designed to communicate with any light switch, garage door opener, home alarm, heating or AC unit, and entertainment system. The product’s manufacturer, Nest, which is now owned by Google, recently informed Revolv customers that their devices would no longer function. So Revolv now serves as a classic example of an IoT product that was long on technology and features and short on addressing the needs of customers.

Read Also:
3 Ways to Use Data for More Successful Digital Ad Campaigns

This kind of “tech push” occurs when both management and engineering discount the value of effective design for representing the emotional and physical connections to the end user. Product function is valued more highly than the expected or actual user experience.

When end users fail to engage with an IoT offering, technology is most often viewed as the problem and solution: “We need better security.” “We need to be interoperable with these other products.

Read Full Story…


Leave a Reply

Your email address will not be published. Required fields are marked *