Case study 01S. Siedle & Söhne · Smart Home2023–2024

Complex is fine.
Unclear is not.

At Siedle the whole planning process had to become easier to understand. A prettier interface alone would not have done that.

ChallengeConfiguration took four hours on average, with many manual checks and hardly any guidance through the system.
My roleSenior UX/UI Consultant · Design Lead
Key contributionBrought planning logic, design system, and product picture together.
Outcome & evidence4h → 7m
9.5/10 CSAT
Measured in the case study

Measured means the figure comes from a documented survey inside the project. Observed means the change was visible in everyday work but was not formally captured.

Siedle case study with configurator, hardware, and outcome metrics
Figure 01 — product, system logic, and measured impact

01 — The Context

Four hours of configuration on average.

That is how long installers needed for configuration and manual wiring checks.

The environment: Hardware, app, IP networks, installers, end customers. Everything is connected. That is exactly what makes it interesting (and complicated).

The real task: The specialist knowledge had to get out of people’s heads and off paper checklists. Into a product logic that guides people step by step.

02 — The Outcome

The complexity stayed.
Just not with the users.

4h → 7msetup time according to case study (previously 4 h on average)
9.5/10CSAT according to case study
B2B2Cvolume-ready product ecosystem

The configurator translated specialized knowledge into a guided flow. Before: check manually, look things up, hope. Afterwards the product suggested the next sensible steps.

I'm happy to show configurator flows and components anonymized in a call.

Schematic of the planning flow: before, six steps with manual checks and two rework loops; after, three guided steps
The planning flow, before and after

03 — The Approach

From paper checklists to guided planning.

01

Everything on the table first

The installer journey showed where planning, configuration, and checking fall apart. Suddenly the problem was visible to everyone.

02

Away from matters of taste

Design sprints helped us talk about pain points and consequences. Not about who finds which screen “nicer”.

03

Specialist knowledge into the product

The shift was simple, really: less “configure settings”, more guided step-by-step planning.

04 — Key Learnings

What I took away from it.

Complexity has to go somewhere.

If the product does not carry it, it lands with the users. Usually with a manual, a workaround, or a spreadsheet on the side.

A design system is not “design stuff”.

Documented well, it becomes a shared basis for work. That saves discussions and, in the end, loops.

Are you working on a similarly complex product?

Let’s talk ↗