Ericsson
Enterprise IoT product design, 2023
View live projectOverview
Enterprise IoT is a category rather than a product: connectivity, devices, and the tooling around both, built for people whose job is keeping a large estate of them running. Nobody opens this software for pleasure. They open it because something needs doing.
I worked inside Ericsson’s UX team, thirteen people, rather than delivering to it from the outside. The engagement came through 3fs; the day to day was Ericsson’s.
The work
Flows first, then prototypes, then the interfaces that shipped. Those are less three phases than three resolutions of the same question, and on a product this size the cheapest place to discover that a flow is wrong is still the flow.
All of it alongside product and engineering rather than handed over to them. On enterprise software that matters more than it does anywhere else, because the constraints that decide a screen are usually not design constraints. They are what the platform can already do, what it did last year, and what a customer has built on top of it since. The only way to meet those early is to be in the room when they come up.
Design system
At this scale a design system is infrastructure, not a component library. Many products, many teams, and a long tail of screens already built against it, which means every change is a change to something that is in use.
I contributed to the Ericsson Design System across both halves of that: the new work, and the maintenance that keeps a system honest once people depend on it. The second half is the less interesting one to talk about and the one that decides whether the system is still true a year later.