Show Menu
Cheatography

7 Interaction Design Principles for IoT Product Cheat Sheet (DRAFT) by [deleted]

7 Interaction Design Principles for IoT Product Designers

This is a draft cheat sheet. It is a work in progress and is not finished yet.

Introd­uction

With all the hype about the Internet of Things, it’s easy to forget that we’re still just talking about products: physical things that people can pick up and use. In that sense, designing for the IoT is just a more complex version of product design — something humans have been doing in some form since the Stone Age.

1. Minimize Cognitive Load

When faced with an infinite variety of sensors, displays, and techno­logies, it’s tempting to cram as much “smart­ness” into a product as possible. But every feature comes at a cost. A complex product often means a complex interface, and this adds to the amount of attention it demands from your user. Most of us already deal with a smartp­hone, tablet and laptop, and as smart products prolif­erate, they suck up precious cognitive bandwidth.
Make alerts subtle and few; make interfaces easy to learn and tasks quick to complete. In a world full of smart products, “less is more” isn’t just an aesthetic, it’s a requir­ement.

2. Consider the User

We’re never designing for everybody. Some IoT devices are for the novice with a few specific needs, others are for the power user who wants to endlessly customize. People in a profes­sional enviro­nment have different needs and expect­ations than those at home. Some devices will be specific to a single person, others used by an entire family.
Don’t start designing until you know who you’re designing for. Terms like “clear and intuitive” or “fast and efficient” have real implic­ations for interface design, and they’re often mutually exclusive. Make sure you know your users’ priorities before you start setting your own.

3. Base Your Design on Workflow

Have you ever asked “what’s it for?” and been given a feature list in reply? Designers and product developers tend to think in terms of features, because that’s what they’re ultimately respon­sible for. But users think in terms of workflow: not a collection of features, but a series of tasks and intera­ctions, that proceed in a particular order to achieve a desired outcome.
If you design an interface that doesn’t understand workflow, it’s going to be obviou­s–your final product will demand multiple steps in and out of different modes and states in order to complete the simplest multi-step tasks, and your users will get frustr­ated. And they’ll use someone else’s product
 

4. Anticipate and Respond To Mental Models

When we drive, we think in terms of “lanes”: a mental model that allows a lot of cars to move smoothly through constr­ained spaces. These kinds of shared mental models are crucial to successful technology use, too, whether it’s the scroll­ing­/sl­iding menu model of the early iPod, or the point-­bui­lding model of the Nike Fuelband.
Anticipate which kind of model makes the most sense for your product, and design an interface that supports it. Are your users navigating a branched tree of decisions, or picking from a list? Are they config­uring an assistant and letting it do a job on their behalf? These kinds of abstract ideas are fundam­ental to good intera­ction design, so don’t neglect them, or leave them until too late in the design process.

5. Metaphors To Leverage What Users Already Know

Similar to mental models, metaphors are useful ways of casting inform­ation in terms that users are already familiar with. The best-known example is probably the “desktop” metaphor that governs modern graphical user interfaces (GUIs), from Windows to OSX to Linux. Individual documents are “files”, which are sorted into “folders” or thrown in the “trash” — these were conscious decisions of early intera­ction designers, who realized that the best way to make a new technology accessible is to use the language and structure of an existing one.
In the IoT, this approach plays out in endless ways. Samsung’s induction burner stovetops use a ring of blue LEDs to indicate which burners are on, and how hot they’re running. By projecting spots of blue light around the edges of a pot or pan, they immedi­ately reference the familiar flames of a gas stove, no explan­ation required

6. Use System Intell­igence To Replace User Inputs

Nobody wants to enter all of their personal inform­ation into a web form when completing a transa­ction, so most browsers now offer automatic auto-c­omp­lete. Similar opport­unities exist in IoT.

IoT products have sensors, embedded intell­igence, and access to all online inform­ation. If there’s a simple task that users must frequently address, consider whether an algorithm can take its place.
You’ve got a smart product in front of you — use it to make life a little easier

7. Ask What an “Encha­nted” Version Would Be

One of the most useful approaches to IoT design is also one of the most fanciful sounding. Because so many IoT products are simply “smarter” versions of existing ones, it’s worth asking what it would look like if it had magical proper­ties.
Fantasy is where many of us first learned to think about possib­ilities and utopian scenarios. As IoT designers, we have an incredible array of tools at our disposal. If we’re going to use them to change the world, why not make it a more magical one?