Industries

Where your product operates changes how it is engineered

A sensor on a kitchen wall, a unit on a running machine and a flight controller meet different limits: who installs them, how they connect, how long they stay, and who may act on them. Start with the place your product will live in.

Find your environment

Why the place matters

The product is half the system. The place is the other half

Each place changes which engineering question has to be settled first.

  1. Who sets it up?

    At home, someone who is not an engineer, on a network that changes without notice. On a running machine, an installer who is not always the engineer who designed the unit, on equipment that was there first.

  2. What does the link look like?

    An aircraft’s radio or Wi-Fi path drops in signal shadow. In a care setting a connection drops differently, and the product has to save, queue and recover.

  3. Who may act?

    In an energy product, observing, configuring and approving are different permissions. Around existing field equipment, observing a system does not give control of the process.

The places

Find the place your product will live

Each page starts from different questions. Filled squares mark the ones that page treats as defining; open squares are not part of how that page frames the problem.

Where people are in the room

The product lives with people who did not build it and may not be technical.

  1. Smart Home & Consumer IoT

    Who sets this up, and on whose network?

    • People
    • Link
    • Fit
    • Time
    • Change
  2. Healthcare

    Who is it for, and where does engineering stop?

    • People
    • Link
    • Change
    • Authority

Where something is already running

The product joins machines, assets and systems that were there first.

  1. Energy

    What was measured, when, and who may act on it?

    • Fit
    • Time
    • Authority
  2. Manufacturing

    Where does the signal come from, and where does the unit live?

    • People
    • Fit
  3. Oil & Gas

    Where does the existing field system end and your software begin?

    • Link
    • Fit
    • Change
    • Authority
A drone surveying a small field and farm buildings, with crop maps and charts on panels beside it

Where the product is out on its own

The product ends up beyond the reach of the people who built it.

  1. Agriculture

    Who installs it, and what happens when nobody looks at it for long stretches?

    • People
    • Time
    • Change
  2. Drones & UAV

    What can the aircraft carry, power and still link?

    • Link
    • Fit
    • Change
  3. Automotive & Mobility

    What does the unit do when the vehicle is out of coverage?

    • Link
    • Change

What stays the same

The place changes the brief. The seams stay the engineering

  1. The seams

    Device, connection, cloud and app still have to behave as one product.

  2. The update path

    How a product is changed once it is installed is designed before it ships.

  3. The order of questions

    Only the question that comes first changes with the place.

Between two places

If your product sits between two places, start where it spends its life

Then read the neighbouring page for what the product hands over.

Where to go next

You know where it operates. Next: what it has to become, and who engineers it

What does the product have to become?

How much of the engineering do you hand over?

Not sure yet? Product Discovery & Technical Strategy is where that decision gets made.

Talk through where your product will operate

Bring the product and the place it will be installed.