Skip to content

Plain-language guides to iot development

Date

Monday, November 16, 2026

Posted by

Date

Service Design for Connected Products: Principles and Steps

iot service design

Your connected product works in the lab, yet customers still get stuck once it’s in their homes. IoT service design fixes that by planning devices, people and support as one system, not separate parts.

This guide sits inside our wider coverage of iot user experience design, and it zooms in on the service that surrounds the device.

Item Value
Antecedents of successful IoT service and system design six antecedents
Manufacturers compared in the case study two manufacturers (aerospace and trucking)
Case study published April 30, 2018
Length of the practitioner design-principles list 7 principles
Practitioner list published 14 Mar 2017

The figures come from the Sayar and Er case study and the Futurice design principles post. They can change, so check the sources before you rely on them.

What IoT service design actually covers

A connected product is more than a gadget with an app. Futurice describes IoT solutions as made of several elements, which is why one design discipline rarely covers them all (source).

  • Physical devices such as sensors, actuators and interactive devices.
  • The network that connects those devices.
  • The data gathered and analysed to create a meaningful experience.
  • The physical context in which the user meets the solution.

Service design is the work of making those elements, plus the people and processes behind them, behave like one offer. The manufacturing study by Sayar and Er concludes that successful IoT implementations need well-executed service and system design, not only a solid product (source).

A concrete example from that study: Caterpillar integrates sensors into its vehicles so operators and service personnel get information about potential problems and the actions that solve them. The product alone does not deliver that value; the service around it does (source).

Six antecedents from two manufacturers

Sayar and Er compared two leading manufacturers, one in aerospace and one in trucking, and published their findings on April 30, 2018. They identified six antecedents of successful IoT service and system design (source).

  1. A well-articulated system design strategy, communicated across the business. Ask whether every team could explain it in a sentence.
  2. Redefined frontline roles and responsibilities. The people who install, repair or support the product now carry part of the experience.
  3. Service-aware staff, through training and recruiting. Technical skill alone is not the target.
  4. Guidance for customers on system use. Connected products need onboarding, not just a manual.
  5. Customer focus aligned across the business, so sales, engineering and support pull in the same direction.
  6. Methods for systems thinking and creativity, used deliberately rather than by chance.

The study covers two cases in manufacturing, so treat it as a strong checklist rather than a universal law. Smaller consumer products may weigh the items differently.

Seven principles that shape connected-product services

Futurice’s list of 7 principles is aimed at practitioners and dated 14 Mar 2017 (source). Read it as a prompt for team discussion, and check each point against your own users.

  • Focus on value. Research where a problem is truly worth solving.
  • Take a holistic view. Design across devices, services and touchpoints.
  • Put safety first. Trust is a main design driver.
  • Consider the context. Homes, workplaces and public areas differ.
  • Build a strong brand. Brand goodwill helps when something fails.
  • Prototype early and often. Hardware is hard to change later.
  • Use data responsibly. Collect what makes the solution useful.

Two of these matter most for service design. On the holistic view, Futurice says it is not enough to design one touchpoint well; you must look across the whole system, the role of each device and service, and the conceptual model of how the user understands it. On trust, it warns that trust is built slowly and lost easily, so each interaction should build it (source).

iot service design Design planning
People lean over a table with large sheets of paper and colorful sticky notes.

Context adds a physical edge. Futurice points out that commands given through digital interfaces can have real-world effects that cannot necessarily be undone, so your service needs clear recovery paths.

How does a service blueprint help?

A service blueprint lays out what the customer sees, what happens out of sight and which processes support it. A 2024 study adapted the method for networks of companies and proposed an enhanced framework with three key components (source).

  • The cyber frontstage lane, for digital interactions.
  • The physical backstage lane, for physical operations.
  • The support stage lane, for supporting processes.

That split fits connected products well, because the app, the device and the repair team all sit in different lanes. The authors tested the framework in the Portuguese stone sector and reported that it identified network dysfunctions and was easy for industry professionals to use (source).

Note the setting: the study concerns coopetition networks, where companies collaborate and compete. If you build a single-company product, borrow the lane idea and drop what you do not need.

Steps to run an IoT service design project

The sources do not prescribe one fixed method, so this sequence is an editorial synthesis of their points. Adjust it to your team and product.

  1. Research the real user value and the barriers to adopting the technology, before you fix the feature set.
  2. Map the whole system, including each device, service provider and touchpoint, on a blueprint with digital, physical and support lanes.
  3. Follow a customer through setup, daily use, failure and repair, and our guide to an iot customer journey map shows one way to record it.
  4. List the error situations across hardware, software, network and user actions, then design what the user is told and how they recover.
  5. Prototype the hardware and the service together, including the support conversation, before you commit to production.
  6. Prepare frontline staff and customer guidance so the people around the product can explain and repair it.
  7. Check that people with different abilities can set up and use the product, and our overview of iot accessibility is a good place to start.

Revisit the blueprint after launch. Real support tickets will show where the lanes do not connect the way you drew them.

Frequently asked questions

Is a well-designed product enough for a connected offer?

Show answer

No. The manufacturing researchers found that results depend on service and system design as well as the product, so staff, guidance and processes need design attention too (source).

Why prototype so early?

Show answer

Futurice notes that a connected object is hard to replace once it is installed, and its software can be hard to update for security and privacy reasons. Early prototyping of both hardware and the whole solution reduces costly rework (source).

How much data should a connected product collect?

Show answer

Only what the solution needs. The same practitioner list advises against hoarding data and suggests picking the data points that make the product functional and useful (source).

Can I use a service blueprint for a physical product?

Show answer

Yes, as a starting point. The lane structure of digital front stage, physical back stage and support processes was tested in a stone-sector network, so adapt it to your own product rather than copying it (source).