One step back

To make the network features easier to understand, I reviewed their names, descriptions and tooltips, but focused above all on how they were organised and how they worked.

In the legacy interface, features appeared in a single list, with no meaningful grouping to help users find their way around. This made it difficult to locate the right option quickly, while unclear names and inconsistent behaviour made individual features harder to understand.

I documented my proposed changes in a spreadsheet, specifying each feature’s name, description, category and intended behaviour. This became the basis for discussions with the Product Owner, developers and stakeholders, helping us reach an agreed solution.

A place for everything

The new taxonomy grouped network features into categories based on their purpose, making individual features easier to find and the differences between them easier to understand.

This structure was adopted in the redesigned interface, allowing users to navigate a wider range of options, including the 18 new features, without adding unnecessary complexity.

A matter of logic

Some features belonged in a particular category but behaved in the opposite way to the others. Full roaming bar, for example, was clearly a roaming feature and needed to stay in that group. However, while the other features enabled a service, switching Full roaming bar on actually blocked it.

To address this inconsistency at its source, I proposed renaming it Roaming capability and reversing its logic during the preliminary review. This meant that switching it on would enable roaming, bringing it into line with the other features in the group.

Reducing uncertainty

In the latest iteration of the confirmation message, we made the information about processing times more accurate. This helps users understand when to expect their updates to be completed, setting clearer expectations about how long the process will take.