Ericsson Private 5G
Project Overview
Ericsson Private 5G is a wireless networking
solution that enables organizations to deploy
private cellular networks on-site.
The network is managed through a cloud-based
Network Management Portal where administrators can configure, monitor,
and operate network components.
My Role
I was part of a 6-person UX team designing the Network Management Portal
for Ericsson Private 5G.
Within the team, we each owned individual product features from concept to implementation.
I worked on multiple configuration workflows and interfaces that help users to install, configure, and manage network components through the portal.
This involved close collaboration with frontend and backend developers, radio engineers, and documentation teams to ensure the designs aligned with how the system actually works.
System Overview
The system supports a multi-stage process for deploying and operating a private 5G network.
It is structured into four main stages:
-
Site Selection
-
First-time configuration
-
First-time activation
-
Runtime operation
Understanding the Users
The system supports users across Ericsson, partner, and enterprise organizations, each with different roles, responsibilities, and levels of access.
Elsa is a software installer with a crucial role in setting up the system.
One of her roles is site activation, including configuring the baseband during installation.
Elsa’s journey in the installation process is structured into five phases.
In this case study, I focused specifically on Phase 5 (site activation), where baseband configuration is one part of the process.
Design Process in Practice
We followed a user-centered design approach, but in practice we adapted it to fit the realities of the project, where design decisions were shaped by system complexity and close collaboration with cross-functional teams.
User-Centered Design
Process in Practice
Key Design Challenges
No real users access
The product hadn't been released yet, so we had no access to real end users.This made it difficult to validate the design and test the system in real scenarios.
To move forward, to validate our designs, we relied on close collaboration with internal experts involved in the project, including radio engineers, backend developers, and project stakeholders. After designing a feature, we presented it in review sessions with these teams to verify whether the flow and logic were correct. Once aligned, the design was then handed over for implementation.
Complex and dependent configuration
The configuration process involved multiple steps and dependent inputs, making it hard for users to keep track and avoid mistakes.
To address this, I structured the process as a step-by-step flow to make it easier to follow.
Each step clearly shows what needs to be filled in, with related inputs grouped together and clear error messages to guide the user through the process.
The following screens are examples of the configuration flow and step-level interactions.
Final Design
The following screens show the end-to-end baseband configuration flow, structured across six steps.
The goal was to make a complex setup process easier to follow. Since many inputs depend
on each other, breaking it into steps helped users understand what to do and when.
We also designed the flow in a way that prevents users from making invalid configurations.
By the time they reach the final step, everything is already set up correctly.
Design Delivery & Quality
To ensure the designs were ready for implementation, I followed a structured approach that combined design quality, team alignment, and clear handoff.
-
Worked closely with developers and stakeholders through regular discussions.
-
Reviewed and refined designs regularly within the UX team.
-
Presented and validated design solutions to development and cross-functional teams.
-
Updated role mapping when features impacted permissions.
-
Documented features in Confluence to ensure clarity and alignment across teams.
-
Maintained and updated the UI library for consistency.
-
Delivered complete wireframes and interaction flows to the development team.