Technology & Innovation

Service thinking

September 15, 2014

Global

September 15, 2014

Global

Designing for the Internet of things? First, think of the service

Designing for the Internet of things? First, think of the service

Why starting with the service you aim to provide may be the best way to design IoT-connected objects

This year’s International Consumer Electronics Show (CES) was heaving with exhibitors chasing the current top trend in consumer electronics: the Internet of Things (IoT). From a suitcase to a dairy cow, from a light bulb to a train track, almost any object can be now connected to the Internet via embedded computing components. 

Some of these look like technical fancies that are unlikely to see the light of day, but others capture the imagination: a world in which can "talk" to us and one another feels genuinely new and exciting, a bona fide technological forward leap like the Internet was before it. 

This new world requires new design principles and skills. The objects that make up the Internet of things are unlike conventional products, of course, but nor are they akin to information systems with digital interfaces, such as websites or mobile apps. The design principles and practices developed for each of those are unlikely to produce the best possible connected 'things'. 

So how should businesses approach design for the Internet of things? One approach, advocated by experts, is to consider the object in question as the physical interface for some service that the business provides. It is this service, whatever it happens to be, that the customer ultimately pays for, so the thinking goes. The 'thing' should therefore be designed to best the delivery of that service. 

Services and systems

According to Mike Kuniavsky, user experience architect and author of Smart Things, designers should start by conceiving the service they wish to provide through the Internet of things, and only then think about the hardware that will deliver it. "Designing the thing first is kind of backwards," Mr Kuniavsky says. "How can I use this thing?"

He suggests thinking about a connected object as an "avatar" for a service. An example is the London Oyster travel card, which allows passengers to pay for journeys by touching an RFID-enabled card onto a receiver. 

The Oyster card is, in Kuniavsky's parlance, the avatar for the service of paying for a journey. Today, it is possible to use that service without the Oyster card itself, by using either the near-field communication functions of a smartphone, or a contactless payment card. However, the Oyster card made the service easy to use, using a form factor with which most customers were already familiar. 

"Designing the thing first is kind of backwards"

Another example is Nike+, the sportswear company’s online excercise tracking service. The service was originally launched to work with Apple's iPod devices, but now accommodates a range of devices, including wristbands and smart watches. 

Building a compelling and useful service has never been easy. In the context of the IoT it requires the combination of a variety of different systems and technologies. Getting this right is one of the hardest challenges for an IoT designer, says Claire Rowland, author of the forthcoming book, Designing Connected Products: UX for the Consumer Internet of Things.  

"You have to think much more about designing systems than designing user interfaces," she says. "But when you’ve got a system of different devices, with different capabilities, it’s much more complicated to do that. You can make a lovely app, but if the whole thing’s not working together as a system then it won’t feel like its functioning as a service."

For manufacturers such as Apple, the way to get around this complexity has been to develop 'closed' systems that only communicate with devices and objects from the same family. The logic is that functionality and communication are thus easier to achieve. 

What is possible in IoT design will evolve along with the supporting technologies. According to Ven Sen, head of advisory services for social, mobile and sensors at global IT firm Cognizant, it is important to make sure the limitations of today do not constrain our imagination.

"Our concerns today are ‘how can I connect to a device’ but we will then move into how is the object itself designed,” he says. “The physical nature of objects will change with technology."

"Architecture is a good example. Five years ago you had a certain set of requirements when you physically built a house and WiFi was not one of them."

All the more reason, then, for businesses to consider first the service they intend to provide to their customers, and to view the Internet of things as simply one more medium through which to deliver that service.  

Do you agree that 'service thinking' is the key to IoT design? What services are ripe for an IoT front-end? To share your thoughts, please visit the Future Realities LinkedIn group, sponsored by Dassault Systèmes

Enjoy in-depth insights and expert analysis - subscribe to our Perspectives newsletter, delivered every week