Skip to content

Plain-language guides to iot development

Date

Monday, November 16, 2026

Posted by

Date

Creating Personas for IoT Products

iot personas

Worried your smart device is being designed for an imaginary average user? Good iot personas fix that: they turn research into a few realistic profiles, covering buyers and operators, that guide design decisions.

Personas are one building block of iot user experience design, and this page covers how to create them for connected products.

Item Value
Consumer personas in Infinum’s research Four (Opposer Ollie, Reluctant Rebecca, Curious Curtis, Ambassador Amanda)
Consumers behind Infinum’s personas 948 European consumers
Persona types in IoT For All’s framework Six
Basis of IoT For All’s grouping Collected field observations, not a scientific grouping

The figures come from Infinum’s consumer research and IoT For All’s persona framework. Both can change or be updated, so check the sources before you rely on them.

What iot personas are and why they matter

In design thinking, a persona is a named user category that stands in for a group of real people. IoT For All’s design thinking guide says that identifying the user categories of an IoT solution can make design decisions easier, because the team keeps its focus on what is important.

A connected product rarely has a single user. The buyer, the person who fixes it and the analyst who reads its data can all be different people, so one generic profile hides real differences.

Personas also shape more than the screen. The same guide notes that, besides user experiences, personas can be used to design systems and solution architectures, and it lists several places they help:

  • Defining the user interface.
  • Choosing the right data store for the data.
  • Prioritizing deliverables by how large each persona’s population is.

Start with qualitative research, not assumptions

Personas built on guesses simply repeat your team’s opinions. IoT For All’s piece on qualitative research argues that skipping qualitative user research typically leads to over-engineering a product and making something nobody wants.

Its example is Griffin’s $100 Connected Toaster, which sends a notification when the toast is done. The author points out that on most toasters the dial already saves past settings and a sound signals completion, so the product solves a problem people do not have.

The article also quotes Wired: quantitative methods let you test your assumptions, while qualitative research lets you find out what you don’t know. That split is why interviews come before persona drafting.

Its process is based on design thinking and runs in three steps:

  1. Talk to people. Hold open-ended interviews without leading questions, and learn about each person’s background, free time and routine.
  2. Map the journey. A journey map shows where the user’s current process hurts, and those pain points are opportunities to design solutions.
  3. Write a problem statement. Focus the solution on one clear problem, then decide whether IoT is the right tool for it.

For a thirty minute interview, the author plans roughly fifteen to twenty minutes of prepared questions and leaves the rest for listening. The deliverable from the interviews is four to five major insights about users. Tell participants that their input will shape a product, and ask before you record them, as the article advises.

Research can also show that IoT is the wrong answer. Not all problems require IoT solutions, and a persona-led brief lets your team say so early.

iot personas Team discussion
Three people gather beside a wall covered with colorful notes.

Four consumer personas from Infinum’s research

Infinum’s marketing and product strategy teams built four consumer personas through cluster analysis of responses from 948 European consumers. They examined demographic variables, lifestyle choices, values, previous usage and ownership patterns, as described in Infinum’s write-up.

Infinum frames the personas as a way to bring statistics and behavioral insights to life. Here is how each one is described:

  • Opposer Ollie is a rural resident with a lower income. If he ever buys, he is most likely to choose systems high on practical usefulness, such as smart lighting or security for his farm.
  • Reluctant Rebecca is a suburban mom who finds smart devices less useful and pleasant, and is apprehensive about privacy risks. A smart baby monitor is the device she might try.
  • Curious Curtis is an urban resident with a higher household income than Rebecca’s group. His openness to innovation and tech-savviness make him an important player in connected living, and he is expected to evolve into an Ambassador.
  • Ambassador Amanda is an advocate and trendsetter for IoT technology use. She is an influencer who promotes the benefits of a connected lifestyle.

Differences in adoption, such as a user with a few unconnected gadgets versus one building a full smart home, are central to multi-device ux design.

Because the sample covers European consumers only, treat these profiles as worked examples rather than ready-made personas for your own market.

Six operator roles behind one connected product

Consumer personas describe buyers, but many products also serve the people who run them. IoT For All identifies six types of personas and illustrates them with a connected coffee machine and a chemicals’ facility. These are the coffee machine examples:

  • The Driver: a bar owner who wants to be notified and to prioritize fixing a malfunctioning machine.
  • The Asset Operator and Supervisor: an owner tracking daily consumption and maintenance, and a manufacturer’s officer reviewing monthly consumption per region and reported hardware failures.
  • The Engineer or Domain Expert: a hardware designer who investigates temperature or pressure fluctuations to find module failures.
  • The Data Operator: a market analyst looking for correlations between hardware failures and customer churn.
  • The Auditor: an external auditor checking GDPR compliance, such as confirmed data deletion for former customers.
  • The Platform Operator: the person who provisions and deprovisions machines and rolls out configuration updates, such as new brewing recipes.

The role names describe needs from an IoT platform perspective and are not tied to specific occupations or functions. The grouping rests on collected field observations and is not a scientific effort, so use it as a starting checklist rather than a rulebook. See the original framework for the industrial examples.

Once the roles are defined, they drive scoping. You can prioritize deliverables by how large each persona’s population is, and you can decide how much out-of-the-box versus custom-built functionality to include by how tech-savvy the audience is.

How do you turn research into personas your team will use?

Combine the two approaches above: interviews for depth, and grouping for structure. A practical sequence looks like this:

  1. Interview a mix of buyers, daily users and back-office staff.
  2. Group people by behavior, values and needs, which is the kind of variable set Infinum used, instead of by job title alone.
  3. Write each persona as a short profile that records traits IoT For All asks about, such as population, tech affinity and need of immediate response.
  4. Rank the personas so the largest or most critical groups shape the first release.
  5. Test each persona against real decisions, then correct it when new research disagrees.

Personas earn their place when they settle concrete choices, such as how much spoken guidance a low-confidence user needs in voice user interface design.

Keep each profile short and replace invented details with observed ones. A persona nobody can trace back to an interview is only decoration.

Frequently asked questions

What are iot personas in plain terms?

Show answer

They are research-based profiles of the different people who buy, use, maintain or analyze a connected product. They give your team a shared picture of who each decision serves, instead of an imagined average user.

How many personas should an IoT product have?

Show answer

There is no fixed count. Infinum’s consumer study ended with four profiles, while IoT For All’s operator framework lists six roles, because the two answer different questions.

Can I rely on survey data instead of interviews?

Show answer

Surveys reveal patterns, as Infinum’s cluster analysis of European consumers did. Still, IoT For All’s author says qualitative research can be as easy as talking to someone and is worth the effort, because interviews surface what a questionnaire never asks.

Can one person fit more than one persona?

Show answer

Yes. According to IoT For All, real people can match several of its types, so treat each persona as a role someone plays at a given moment, not a box for a whole person.