The Problem
Leonteq runs dozens of internal applications: trading platforms, risk tools, compliance systems, data dashboards. Each one was built by a different team, with its own URL, its own documentation, and its own learning curve.
The only way to navigate this ecosystem was through Confluence pages that nobody kept up to date. New joiners spent their first weeks just finding things. Experienced employees lived on tribal knowledge, with someone on Slack sending the right link and telling you the right person to ask.
There was no overview. No map. No single source of truth for what existed, who owned it, or how to use it.
>_key insight“Think Adobe Creative Cloud, but for a financial institution. Every app has a profile. Every shortcut is one click away. The entire workplace, in one place.”
// design_process
- 01
Discovery
Embedded with new joiners, power users, and engineering leads. Mapped the full application landscape, cataloguing every tool, owner, and use case across the organisation.
- 02
Architecture
Defined the information model: every app gets a profile. Every profile has a clear owner, documentation, quick-launch shortcuts, and embedded micro-frontend access to key features.
- 03
Design
Personalised dashboard, full app catalogue, detailed app profiles, stakeholder directory, and quick-launch shortcuts. 200+ Figma screens across all states and user roles.
- 04
Validate
Three rounds of usability testing: new joiners navigating onboarding, power users testing shortcuts, managers reviewing their app profile pages.
- 05
Ship
Phased release: core launcher and app profiles first, micro-frontend integrations second, personalisation and shortcuts in the final phase.
App Profiles
Every application at Leonteq now has a dedicated profile inside HUB, like a product page on an internal app store. It tells you what the app does, who owns it, who to contact if something breaks, and how to get access.
For new employees, this replaced a graveyard of outdated Confluence pages with a living, always-current source of truth. No more Slack messages asking for the right URL. No more guessing who the right stakeholder is.
Micro Frontends
The technically interesting part of HUB was the micro-frontend integration. For certain high-frequency workflows, we didn't want users to have to fully open an application just to perform a single action.
Instead, individual features from different apps can be surfaced directly inside HUB as embedded micro-frontends. A trader can check a position or trigger a simple order without leaving the HUB context. A compliance officer can run a quick check without switching applications.
This required close collaboration with the engineering teams of each integrated app, defining the contracts, handling authentication, and ensuring visual consistency through the Moneypenny Design System.
Full app catalogue, browsable by category, team, or usage frequency
App profile: owner, stakeholders, quick-launch, and embedded feature access
0%
reduction in time to find and launch any Leonteq tool
0
days onboarding vs. 3 weeks. New joiners productive in their first week.
0+
daily active users across all Leonteq offices globally
0.0/5
average satisfaction score in post-launch employee survey
What This Project Taught Me
Designing an ecosystem layer is a different problem from designing an application. You're not solving one workflow, you're building the substrate everything else runs on. Every information architecture decision has system-wide consequences.
The hardest work wasn't in Figma. It was aligning a dozen independent product teams around a shared model for how their applications would be represented. Each team had legitimate concerns about ownership and accuracy. Getting everyone to trust the system enough to maintain their own profile pages was as much a change management challenge as a design one.
HUB worked because it gave people something useful immediately, and got better the more teams contributed to it. That flywheel is what made it stick.