Feature Projects >
Partner Hub >
Hero 1
HERO 1
Building a structure before designing the interface
The Challenge
Partner Hub brought together a growing number of tools used by different partner roles. Before designing individual screens, we needed to understand how everything connected and create a structure that could remain clear as the platform evolved.
Defining the Structure
Working with the Product Owner, Design Lead and another UX designer, I contributed to mapping user flows, organising information and shaping the navigation. Rather than designing isolated screens, we focused on how users would move between tasks and modules and used this as a foundation for the interface.
01 — Understanding users, roles and relationships
Before defining the navigation, we mapped the different users, roles, platform areas and relationships between them. This helped us understand how different responsibilities and access levels would shape the structure of Partner Hub.
02 — Mapping the platform
Early user flows helped us understand how different tasks connected and how users would move through the platform before individual screens were designed.
Key Insights
Navigation wasn't organised around screens, but around modules that supported users' everyday tasks.
03 — From structure to navigation
Early user flows helped us understand how different tasks connected and how users would move through the platform before individual screens were designed.
© 2026 Lidija Janković
Feature Projects >
Partner Hub >
Hero 1
HERO 1
Building a structure before designing the interface
The Challenge
Partner Hub brought together a growing number of tools used by different partner roles. Before designing individual screens, we needed to understand how everything connected and create a structure that could remain clear as the platform evolved.
Defining the Structure
Working with the Product Owner, Design Lead and another UX designer, I contributed to mapping user flows, organising information and shaping the navigation. Rather than designing isolated screens, we focused on how users would move between tasks and modules and used this as a foundation for the interface.
01 — Understanding users, roles and relationships
Before defining the navigation, we mapped the different users, roles, platform areas and relationships between them. This helped us understand how different responsibilities and access levels would shape the structure of Partner Hub.
02 — Mapping the platform
Early user flows helped us understand how different tasks connected and how users would move through the platform before individual screens were designed.
Key Insights
Navigation wasn't organised around screens, but around modules that supported users' everyday tasks.
03 — From structure to navigation
Early user flows helped us understand how different tasks connected and how users would move through the platform before individual screens were designed.
© 2026 Lidija Janković
Feature Projects >
Partner Hub >
Hero 1
HERO 1
Building a structure before designing the interface
The Challenge
Partner Hub brought together a growing number of tools used by different partner roles. Before designing individual screens, we needed to understand how everything connected and create a structure that could remain clear as the platform evolved.
Defining the Structure
Working with the Product Owner, Design Lead and another UX designer, I contributed to mapping user flows, organising information and shaping the navigation. Rather than designing isolated screens, we focused on how users would move between tasks and modules and used this as a foundation for the interface.
01 — Understanding users, roles and relationships
Before defining the navigation, we mapped the different users, roles, platform areas and relationships between them. This helped us understand how different responsibilities and access levels would shape the structure of Partner Hub.
02 — Mapping the platform
Early user flows helped us understand how different tasks connected and how users would move through the platform before individual screens were designed.
Key Insights
Navigation wasn't organised around screens, but around modules that supported users' everyday tasks.
03 — From structure to navigation
Early user flows helped us understand how different tasks connected and how users would move through the platform before individual screens were designed.
© 2026 Lidija Janković