Separate applications. One connected experience.

Business customers need to move between tasks without losing their bearings. My contribution to Telenet Business connected separate applications through shared navigation, a component library, and documentation.

At a glance

Context
A portal for business customers
My contribution
Software UX, shared navigation, and component-library work
Delivered scope
A common interface foundation and documentation across applications
Telenet Business SIM setup and management screens presented with shared navigation.
SIM setup and management illustrate different customer tasks within a shared portal structure.

Help separate applications feel connected.

A customer portal can bring several applications together while still leaving people to make sense of each one separately. From the customer’s point of view, the work continues across those boundaries: setting something up, managing it, and finding the next relevant task.

For Telenet Business, my contribution focused on the connections between those applications. Shared navigation, a component library, and documentation formed the foundation for a more consistent customer experience.

The thinking behind the work.

Give customers a shared point of reference.

Navigation is part of how a portal explains itself. A shared structure gives people a common point of reference as they move between applications. My work contributed to that connection, helping the separate parts sit within a recognisable whole while retaining their individual tasks.

Support consistency through a component library.

The component-library work complemented the navigation. Reusable interface elements provide a shared vocabulary for screens with different purposes. The SIM setup and management examples show the context: the tasks differ, but both belong to the same business-customer experience.

Make the shared approach easier to carry forward.

Documentation was part of the contribution alongside the library and navigation. Shared design work needs an explanation that others can use, as well as the interface elements themselves. Keeping those pieces together supports a common understanding of the portal across its separate applications.

A common foundation for the customer portal.

The work connected separate applications through three concrete pieces: shared navigation, a component library, and clear documentation. My contribution concerned that common foundation. The example shows how I approach software UX beyond individual screens: look at the connections that help different tasks belong to one experience.

Explore my software UX expertise

Have something in mind?
Let’s talk.

Tell me what’s on your mind.
We’ll figure out the next step together.

Ready to say hi?