01 — The Context
Up to four hours of configuration. The interface was not the actual problem.
Installers were spending up to four hours on configuration and manual wiring checks. Simply building new screens would not have solved much.
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 user.
The configurator translated specialized knowledge into a guided flow. Before: check manually, look things up, hope. Afterwards the product suggested the next sensible steps.
Here too: public artifacts are limited by confidentiality. Anonymized flows and component examples can be discussed in a direct conversation.
03 — The Approach
Simply building new screens would not have solved anything.
Everything on the table first
The installer journey showed where planning, configuration, and checking fall apart. Suddenly the problem was visible to everyone.
Away from matters of taste
Design sprints helped us talk about pain points and consequences. Not about who finds which screen “nicer”.
Specialist knowledge into the product
The shift was simple, really: less “configure settings”, more guided step-by-step planning.
“Complexity does not disappear. It has to go somewhere. Good UX puts it into the system and not onto the user.”What stayed from this project
04 — Key Learnings
What I took away from it.
If the product does not carry it, it lands with the users. Usually with a manual, a workaround, or a spreadsheet on the side.
Documented well, it becomes a shared basis for work. That saves discussions and, in the end, loops.