Information Architecture · 2025
Giving a siloed platform a navigation that scales.
Designing a scalable information architecture for SoPost’s next-generation platform.
Role
Senior Product Designer
Worked with
Product, Engineering
Validated with
Internal teams and Customer Success
Status
Signed off, not built
Setting the Scene
In 2025, SoPost rebuilt Campaign Manager from the ground up, and it became clear pretty quickly that the navigation needed a complete rethink, not a patch. The old structure had grown organically, and features like reporting, stock management and fulfilment had each ended up in their own silo.
The result was inconsistent hierarchies, confusing terminology, and duplicated entry points across the organisation and campaign levels.
I led the redesign of the navigation framework, working with Product and Engineering to define how people should move through a multi-layered, data-heavy SaaS platform in a way that felt scalable, intuitive and future-proof.
Understanding the Problem
The legacy navigation had become fragmented and unintuitive.
- Inconsistent information architecture: reporting, fulfilment and product setup each used a different structure
- Poor discoverability: people struggled to find key actions such as viewing orders or managing integrations
- A flat hierarchy: every page sat at the same level, which overloaded people and broke their expected mental models
The challenge was to rebuild a sense of orientation and flow: where you are, what you are doing, and what comes next.
Redefining Hierarchy and Flow
I mapped the full product architecture and grouped actions by user intent, not by department. That revealed a natural three-tier hierarchy:
- Organisation level: global controls such as Integrations and Settings
- Campaign level: the core unit of work for brands
- Reporting level: insights and performance data tied to campaigns
From that, I defined a dual-layer navigation model:
- A persistent sidebar for global navigation and orientation
- A contextual horizontal bar for the task in hand, which changes with the level you are working at
What appears in that bar depends on where you are. Setting a campaign up gives you Campaign settings, Branding, Products and Journeys. Move into reporting for the same campaign and it becomes Orders, Stock, Distribution, Feedback and the rest. That’s progressive disclosure applied to navigation: you see what’s relevant to what you’re doing, not everything the platform can do. It let people move between strategic and operational contexts without losing their place.
Collaboration and Validation
Working with our Product Director and the Engineering leads, I tested early prototypes across internal teams and with Customer Success. The feedback confirmed:
- Faster navigation and clearer task grouping
- A stronger separation between brand-level and campaign-level work
- Better comprehension of where new modules, including ROI reporting, stock and fulfilment, and Integrations, would sit
The new information architecture also left room for future modules without structural change, a key sign that it would scale.
Outcome
The agreed framework defines:
- A unified, scalable framework underpinning every Campaign Manager module
- A clear separation between organisation, campaign and reporting levels
- Lower cognitive load and clearer wayfinding
- A foundation for future permissions and role-based access
The redesign is about how people reach things, not how those things look.
The framework was signed off. It had not been built by the time I left.
Reflection
I grouped things by what somebody was trying to do rather than by which team owned them, and most of the structure came out of that one decision. In testing, people could tell where they were without being told.
It was designed to underpin the whole of Campaign Manager, connecting Reporting, stock and fulfilment and Integrations through one structure. What I find satisfying about this kind of work is that, built, the next hundred features would have somewhere sensible to live.
“From day one, Jade impressed me with her attention to detail and the quality of her designs, which made frontend building almost a copy-and-paste exercise.”
Let’s improve something together.
Open to part-time roles and fractional contracts, two to three days a week.