TL;DR
TL;DR
TL;DR
I redesigned Lobium from fragmented policy tools into a unified, organization-first enterprise platform—defining a universal navigation and access model that enabled EU Radar’s launch, simplified cross-product workflows, and helped reposition Lobium as a single, scalable enterprise solution.
Lobium offered several established policy intelligence tools used by public affairs teams across Europe. As the company moved toward a unified enterprise platform, customers were required to navigate multiple domains, manage access across disconnected dashboards, and switch between products without a shared organizational context creating friction for both analysts and administrators.
As the sole product designer, I partnered closely with product and engineering to redesign Lobium around an organization-first model.
I led the definition of a unified experience architecture, introduced a universal cross-product navigation, and redesigned onboarding, team management, and role-based access to support real enterprise workflows.
This foundation enabled the successful launch of EU Radar and was later rolled out across Lobium’s existing products, aligning the platform into a cohesive enterprise experience validated by existing customers.
I redesigned Lobium from fragmented policy tools into a unified, organization-first enterprise platform—defining a universal navigation and access model that enabled EU Radar’s launch, simplified cross-product workflows, and helped reposition Lobium as a single, scalable enterprise solution.
Lobium offered several established policy intelligence tools used by public affairs teams across Europe. As the company moved toward a unified enterprise platform, customers were required to navigate multiple domains, manage access across disconnected dashboards, and switch between products without a shared organizational context creating friction for both analysts and administrators.
As the sole product designer, I partnered closely with product and engineering to redesign Lobium around an organization-first model.
I led the definition of a unified experience architecture, introduced a universal cross-product navigation, and redesigned onboarding, team management, and role-based access to support real enterprise workflows.
This foundation enabled the successful launch of EU Radar and was later rolled out across Lobium’s existing products, aligning the platform into a cohesive enterprise experience validated by existing customers.
Problem
Problem
Problem
As Lobium’s product surface grew, user friction became systemic rather than feature-specific.
Policy analysts frequently had to log into separate domains, making it difficult to maintain context when switching between tools. Admins lacked a single place to manage team members and access rights, often relying on workarounds or manual processes. New team members found onboarding confusing, especially when they needed access to multiple tools.
This fragmentation slowed workflows, increased cognitive load, and made Lobium feel like several disconnected products rather than a unified platform, limiting both usability and perceived maturity.
As Lobium’s product surface grew, user friction became systemic rather than feature-specific.
Policy analysts frequently had to log into separate domains, making it difficult to maintain context when switching between tools. Admins lacked a single place to manage team members and access rights, often relying on workarounds or manual processes. New team members found onboarding confusing, especially when they needed access to multiple tools.
This fragmentation slowed workflows, increased cognitive load, and made Lobium feel like several disconnected products rather than a unified platform, limiting both usability and perceived maturity.
Research Strategy
Research Strategy
Research Strategy
Discovery: Understanding the System
The initial phase focused on understanding Lobium’s products as a system, not as isolated interfaces.
I worked closely with the PM to walk through each existing product end-to-end, reviewing prior customer insights and identifying recurring pain points — particularly where users crossed product boundaries or managed teams.
To inform our approach, we also evaluated how mature SaaS platforms such as ClickUp, Asana, and Trello model organizations, teams, and access at scale. The goal to understand which structural patterns remain usable as complexity increases.
Through short internal sprints and cross-team discussions, we aligned on the need for a more intentional organization model that could support current users while enabling future growth.
Defining Insight
A key insight emerged from this work:
The organization — not the product — needed to be the primary unit of experience.
Lobium’s users did not think in terms of individual tools. They thought in terms of:
Which organization they were working for
Which team they belonged to
Which tools they had access to within that context
This insight became the foundation for every subsequent design decision.
Experience Architecture & User Flow
The flow establishes organizational context immediately after login, allowing users to:
Belong to multiple organizations
Switch teams without re-authentication
Access only the products available to their organization
By resolving context early, the system reduces ambiguity across all downstream interactions and creates a clear mental model for users while giving Lobium a scalable foundation for future products.
Discovery: Understanding the System
The initial phase focused on understanding Lobium’s products as a system, not as isolated interfaces.
I worked closely with the PM to walk through each existing product end-to-end, reviewing prior customer insights and identifying recurring pain points — particularly where users crossed product boundaries or managed teams.
To inform our approach, we also evaluated how mature SaaS platforms such as ClickUp, Asana, and Trello model organizations, teams, and access at scale. The goal to understand which structural patterns remain usable as complexity increases.
Through short internal sprints and cross-team discussions, we aligned on the need for a more intentional organization model that could support current users while enabling future growth.
Defining Insight
A key insight emerged from this work:
The organization — not the product — needed to be the primary unit of experience.
Lobium’s users did not think in terms of individual tools. They thought in terms of:
Which organization they were working for
Which team they belonged to
Which tools they had access to within that context
This insight became the foundation for every subsequent design decision.
Experience Architecture & User Flow
The flow establishes organizational context immediately after login, allowing users to:
Belong to multiple organizations
Switch teams without re-authentication
Access only the products available to their organization
By resolving context early, the system reduces ambiguity across all downstream interactions and creates a clear mental model for users while giving Lobium a scalable foundation for future products.
Screens
Screens
Screens
Designing a Role-Aware Onboarding Flow for Multi-Organization Access
Shaped by the foundational user flow we had previously mapped out during the organizational redesign. That flow clarified how users should log in, identify their team context, and access the right products.
Building on those insights, we designed a dynamic entry point that adapts to each user’s state, whether they’re new to Lobium, invited to join an existing organization, or already part of a team. This onboarding logic became the gateway into the unified dashboard and set the tone for seamless navigation across Lobium’s suite of tools.
Top Universal Navigation: Iteration Journey & Final Design
One of the most significant design decisions was introducing a universal top navigation shared across all products, with individual product navigations nested beneath it.
This decision created consistency and reduced cognitive load, but it required reworking legacy layouts (as existing users were used to the current navigation). Some product-specific features had to be relocated or simplified to fit within the new structure.
The tradeoff was deliberate: rather than preserving every legacy pattern, we chose clarity and long-term scalability. This approach reduced onboarding friction, improved cross-product navigation, and positioned Lobium to grow without compounding complexity.
Below is a breakdown of the navigation evolution, annotated to highlight key decisions
Usability Testing (Moderated, Task-Based Evaluation)
Before full rollout, we validated the new navigation and organization model through moderated usability testing with a high-fidelity front-end prototype.
We conducted sessions with 12 participants:
2 users from each of 4 existing customer organizations
2 independent consultants working across multiple teams
Each session focused on realistic, task-based scenarios.
Test Task
Task | Goal |
|---|---|
Create an organization and invite team members | Validate onboarding and admin flows |
Navigate from EU Radar to Stakeholder–Issue Matrix | Test cross-product navigation |
Review access levels of team members | Validate role clarity |
Test Outcomes & Insights
Task | Success Rate | Avg. Completion Time | Observed Issues | Insights |
|---|---|---|---|---|
1. Create an organization & invite team members | 10/12 completed | 1.8 minutes | Confusion around “Add Organization” vs “Create Team” | Led to clearer terminology and microcopy |
2. Navigate from EU Radar → Stakeholder Matrix | 11/12 completed | 12 seconds | None significant | Universal top navigation made switching intuitive |
3. View access levels of team members | 9/12 completed | 1.2 minutes | Users expected permissions to be visible earlier | Led to redesign of the “Team Overview” panel |
EU Radar: Proof of the System
EU Radar was the first product I designed and launched within the newly unified Lobium platform.
The challenge was to build a tool that helped teams monitor EU institutions while inheriting the new onboarding, role‑based access, and universal navigation patterns I had designed. The result was a fully integrated product that validated the new system architecture and set the standard for how all other Lobium tools evolved.
See the clickable prototype below (expand to see clearly)
Designing a Role-Aware Onboarding Flow for Multi-Organization Access
Shaped by the foundational user flow we had previously mapped out during the organizational redesign. That flow clarified how users should log in, identify their team context, and access the right products.
Building on those insights, we designed a dynamic entry point that adapts to each user’s state, whether they’re new to Lobium, invited to join an existing organization, or already part of a team. This onboarding logic became the gateway into the unified dashboard and set the tone for seamless navigation across Lobium’s suite of tools.
Top Universal Navigation: Iteration Journey & Final Design
One of the most significant design decisions was introducing a universal top navigation shared across all products, with individual product navigations nested beneath it.
This decision created consistency and reduced cognitive load, but it required reworking legacy layouts (as existing users were used to the current navigation). Some product-specific features had to be relocated or simplified to fit within the new structure.
The tradeoff was deliberate: rather than preserving every legacy pattern, we chose clarity and long-term scalability. This approach reduced onboarding friction, improved cross-product navigation, and positioned Lobium to grow without compounding complexity.
Below is a breakdown of the navigation evolution, annotated to highlight key decisions
Usability Testing (Moderated, Task-Based Evaluation)
Before full rollout, we validated the new navigation and organization model through moderated usability testing with a high-fidelity front-end prototype.
We conducted sessions with 12 participants:
2 users from each of 4 existing customer organizations
2 independent consultants working across multiple teams
Each session focused on realistic, task-based scenarios.
Test Task
Task | Goal |
|---|---|
Create an organization and invite team members | Validate onboarding and admin flows |
Navigate from EU Radar to Stakeholder–Issue Matrix | Test cross-product navigation |
Review access levels of team members | Validate role clarity |
Test Outcomes & Insights
Task | Success Rate | Avg. Completion Time | Observed Issues | Insights |
|---|---|---|---|---|
1. Create an organization & invite team members | 10/12 completed | 1.8 minutes | Confusion around “Add Organization” vs “Create Team” | Led to clearer terminology and microcopy |
2. Navigate from EU Radar → Stakeholder Matrix | 11/12 completed | 12 seconds | None significant | Universal top navigation made switching intuitive |
3. View access levels of team members | 9/12 completed | 1.2 minutes | Users expected permissions to be visible earlier | Led to redesign of the “Team Overview” panel |
EU Radar: Proof of the System
EU Radar was the first product I designed and launched within the newly unified Lobium platform.
The challenge was to build a tool that helped teams monitor EU institutions while inheriting the new onboarding, role‑based access, and universal navigation patterns I had designed. The result was a fully integrated product that validated the new system architecture and set the standard for how all other Lobium tools evolved.
See the clickable prototype below (expand to see clearly)
Conclusion
Conclusion
Conclusion
Lobium’s messaging evolved from individual tools to a unified enterprise platform, aligning product positioning with the redesigned experience. This shift resulted in the following outcomes:
Existing customers successfully transitioned from the legacy experience to a unified platform
EU Radar shipped within the new system without requiring custom navigation or access logic
The unified experience was rolled out across Lobium’s existing products, aligning the platform as a single enterprise solution
The marketing site was redesigned in collaboration with a Webflow developer to reflect this platform narrative
Following the updated messaging and site structure, demo requests increased, indicating improved clarity and perceived product maturity among prospective customers
Reflection
This project deepened my understanding of designing for complex, multi-role B2B systems. In particular, I learned how to:
Translate organizational structures into scalable UX patterns
Extend an existing design system thoughtfully while introducing new platform components
Collaborate closely with PMs, engineers, and domain experts to align technical and user constraints
Balance legacy product constraints with long-term platform vision
By prioritizing clarity, scalability, and organizational context, this work established a platform foundation capable of supporting both existing enterprise customers and Lobium’s future growth.
If extended further, I would explore deeper analytics around organization-level adoption and continue refining role-based insights as Lobium’s customer base evolves.
