How UX Can Help IoT Products, Part 2: User Onboarding, Support, and Security

From Wild West to Mainstream Adoption

In part one of this series, we took a broad look at some of the ways UX strategy can help get your Internet of things (IoT) product headed in the right direction. In this follow-up we’ll be diving deeper into some of the specifics of what makes a great user experience for IoT products, focusing on the critical areas of onboarding, support, and security.

1389701254 Nest Protect 600X335
The Nest Protect uses a visually appealing green to convey messages to the user.

Don’t Haze The Tenderfoot

The importance of great onboarding for IoT

How many articles/websites/books in the UX design and user research space are devoted to user onboarding? At least a million, right? So why discuss it again here? Because with the addition of physical hardware and the potential for multiple control surfaces and interaction points, IoT products simply have more things to setup. Without a good onboarding experience this might mean extra setup steps and greater risk of user frustration or failure.

In the world of IoT getting your users up and running is usually not as simple as firing up an app or launching right into a sign-up process. In addition to more traditional account creation and onboarding, IoT hardware devices need to be configured and managed.

The ideal scenario is an unboxing experience that simply requires a consumer to turn the product on. Amazon’s Echo family of hardware products are close to this level of simplicity. They can ship with user account information already loaded, drastically streamlining installation. Unfortunately, most IoT products can’t support that level of simplicity and pre-shipment account integration yet. Even in the most basic IoT ecosystems it’s likely your user will need to connect a hardware device to a cloud-based account via an app or website and your hardware components will need to be told how to find and connect to the user’s wireless network or to other devices via Bluetooth.

This can be confusing and frustrating stuff, even for tech savvy folk! So building a setup process that less experienced users can follow without stumbling can be a real challenge. UX to the rescue! Here are a few tactics we’ve utilized on IoT projects at Blink.

One Step at a Time: Break it Up

No matter the type of IoT product you are developing it’s key to have a setup process that is broken into guided steps with clear visuals and copy that emphasizes clarity over marketing or system speak. The more complex your product, the harder this challenge may be. The most successful IoT products have onboarding processes that are carefully honed – getting there may require many iterations and user tests.

After you’ve refined your setup flow to the core tasks, separate those processes into discrete steps with digestible information and action steps. Then start to work on a means of providing feedback to the user. Ideally you should include confirmations, presenting modals/sounds/other indications that indicate a step has been completed successfully. You’ll break a user’s trust and excitement for your product pretty fast if they get a few steps into a setup or pairing process but there was an unreported error a few steps back that forces them to restart (see a real life example of this here).

Setup Senses: Sight and Sound

How best to convey setup processes and status? Products that have embedded screens in addition to an app or website have a leg up here – that screen is an ideal place to help provide clarity about status. Use that real estate wisely. Provide clear indications of where the user is at in the process and what action is needed at each step.

For products without an embedded screen, consider using lights or sounds to convey process states. Make sure colors are intuitive (and explained in your app or printed instructions). Even audio cues should be user friendly, whether they are verbal cues or tones. We’ve found in testing that users are easily annoyed if sounds are too loud or grating. For inspiration look at how the Nest Protect uses color and sound alone to guide setup.

If your product is even simpler, without a screen, lights, or sound, that is not ideal, but don’t panic! Can you use confirmations and provide visuals and copy in another element of your system? Thoughtfully designed onboarding graphics in your accompanying app or website can still keep users headed on the right track.

No matter what combination of audio and visual signals, don’t forget about going old school. A printed setup guide included in the box that provides simple and consistent instructions is a worthwhile addition, and it can aid in the initial unboxing experience. Just make sure your printed materials and your on-screen instructions match. We’ve seen misalignments between printed instructions and on-screen guidance in major brand IoT products. This easily avoidable misstep could cause the users frustration.

Inclusive Design Matters in IoT Too

Accessibility is not just a buzzword in design circles these days – it is an important part of developing a mainstream product. You want your product to be as usable as possible to as many people as possible. Will a colorblind user still be able to understand your device’s confirmation colors and setup your product successfully? Can a deaf customer understand that the process went awry if your product uses an audible error tone? Test your onboarding process with as many different audiences as you can.

Things Go Wrong; Be Specific and Helpful

The more complex the product and the larger the number of hardware devices, the greater chance something may go wrong along the way. Always pair your discrete process steps with discrete error messaging.

Provide non-threatening error messaging that helps the user understand what may have gone wrong in human friendly language. Always give users ways to back out and retry the failed process with minimum allowable hassle. And no matter what, work to align imagery and copy to avoid the “All is lost! Start over!” system speak. The all or nothing error-handling processes that might work for dedicated early-adopters will fail miserably with mainstream consumers who just want to get your product setup and move on with their day without needing to pick up the phone or jump into a support forum.

Quit Your Bellyachin’

Make Support and Troubleshooting Visible and Helpful

Beyond setup – the diagnostic and support challenges for IoT products can expand exponentially over a simple app or standalone digital product. The potential for support issues gets higher when working with multiple interfaces, devices, and usage contexts. As such, it’s even more important that IoT products offer support and troubleshooting that doesn’t feel punitive or included as a hastily tossed in afterthought.

Troubleshooting is a big one and in 2017 troubleshooting can (and should!) move beyond simple FAQs. Consider using more interactive, chatbot-like experiences that help the user more easily investigate what might have gone wrong in a conversational way. Self-reporting should be strongly considered as well – can your devices help tell the user that something is wrong? Can your product even help them resolve the issue? Consider applying UX powers to bake in this thinking up front. Your customers will thank you later.

Even with the best troubleshooting, there will be times the user can’t diagnose or solve the problem on their own. In our studies we’ve found that the availability of in-app, easily accessible support is important to IoT consumers. Allow the user to get to support with a single click or tap from Help or Settings. Consider going a step further and making the support process even easier for both your users as well as your support teams by packaging up necessary device/account information directly to a support representative. Automatic is a connected car usage and diagnostic monitor, and when a user needs to get help, the service automatically gathers operating system and product version information into the help ticket submitted by the user. This heads off those painful and costly “Where do I find my firmware number?” or “What product version do I have?” phone calls with customer support reps.

Wildwest Nestcams Web

As welcome as a rattlesnake at a square dance

The UX of IoT Security

Recent high-profile hacks have raised the specter of IoT-related security risks. More and more consumers will be examining IoT devices for information about security up front. These consumers may be increasingly cautious about exposing personal information, especially when it is connected to physical spaces in their homes. Always help users to understand the security of your service without making them dig through product reviews or online forums.

  • What information will they need to provide to use your product?
  • How will that information be used?
  • How does your product or service help keep that information secure?

Simply including text that reads “We use bank-level security” or depicting a lock symbol on a sign-in screen is not enough for most consumers anymore.

Provide reassuring reminders about your security standards during the setup process and during usage to help build trust. Many IoT products need to access home wireless networks, so think about providing transparency around how this information will be handled – what minimum information do you need to keep your product running? Will you have access to see other devices on the network? Be sure to let users know what they can do to prevent unwanted access, but design your systems to offer protection even if they aren’t security pros.

“If you haven’t fallen off a horse…then you haven’t been ridin’ long enough.”

Overwhelmed? Don’t be. Even the most successful IoT or smarthome products went through many updates and iterations and were not without hiccups along the way. Odds are you may not get everything perfect in one go.

While there are many elements that go into creating a successful IoT product just remember, the right user experience driven strategy coupled with great onboarding, thoughtful support, and transparent security will give your product the best chance of success.

If you need help, the UX wranglers here at Blink can assist – we’ve been working in the IoT space for years across strategy, design, and research. We love helping our clients keep users top of mind and design interactions that help avoid those Wild West showdowns with customers.

No matter how you choose to navigate the process for your IoT product, good luck and happy trails!

Similar Articles