Scattered screens to one platform that four user roles trust
Sustainable employability involves many parties: employers, partners, coaches and healthcare professionals, each with their own expertise. Johan asked us to make all of that feel like one experience to the person using it, and to keep it that way as the platform kept growing.
Starting with research and a style direction, we built a Design System, then designed the surveys, the employee dashboard, the marketplace, the onboarding and the public profiles on top of it. Their in-house team built it, and later our developers joined theirs on the web application and the mobile app.
200,000+
Annual users
899
Employers connected
What we did
User Research
Information Architecture
UX/UI Design
Product Design
Website Design
Design System
Component Library
Technical Strategy
Front-end Development
HRTech
Client


01
Introduction
Johan is a Dutch platform for sustainable employability, used by organizations like AON, the municipality of Amsterdam and TNO. Employers run projects, while partners and healthcare professionals offer their services, and employees complete surveys and see their own results. Over 200,000 people use Johan every year.
02
Four roles, one platform
Johan is not one product but four connected ones. An employee wants a short survey and a clear result, an employer wants insight and a budget to spend, a partner wants their services found and sold, and a professional wants a profile that looks credible. We mapped where those journeys overlap and where they have to differ, then built the interface on shared patterns rather than separate solutions. The same navigation logic, the same widgets, the same rules for states and empty screens. An employee arrives through an invite from their employer, so onboarding had to be short enough that a first visit turns into a second one.


03
From screens to a system
The work started concretely: every survey question type, on mobile and desktop. Healthcare professionals use TNO verified surveys to keep track of someone’s wellbeing, so the questions themselves were fixed and the experience had to carry them. Scales with sliders, multiple choice, long answers, sections, numbering. Once those pieces were in place, the same question came up for results: how do you show one measure, several measures, a table, a graph? Instead of designing every dashboard, we designed the widgets behind it and set the rules for how they behave across screen sizes. Partners could then fill a project page with thirty workflows without it falling apart.



04
Customizable, still on brand
Every organization on Johan gets its own project pages. They wanted to recognize themselves in it, so besides their logo as the project avatar we let them add a touch of brand color. Used carefully, because a project page that looks nothing like Johan makes the whole platform feel unreliable. The color shows up in accents and icons, never in the interface structure itself. Partners get a space that feels like theirs, and an employee moving between two projects still knows where they are.
05
Opening the gates
Everything Johan had was behind a login, which made a marketplace with hundreds of partners invisible to the outside world. We designed public profiles for partners, employers and professionals, plus johan.nl as the storefront that ties them together through themes, products and content. The profiles reuse the platform widgets, but with a marketing purpose rather than a dashboard purpose. A partner could suddenly be found on a theme, show their services and link their own blogs to it. The platform became a reason to visit rather than only a tool to log into.


06
A rebuild, not a repaint
After a few years of adding features, the platform needed a new front-end rather than another patch. We made the plan together: their team on the backend, the API and the data entities, us on the client and the components. Scoped down to one widget first, so the setup could be checked before it carried the whole platform. Our developers worked inside their team instead of next to it, which kept the design decisions and the build in the same conversation.



07
Their team took it further
A shared channel, design delivered per feature, guidelines their developers could implement directly. From the start the platform was built by their in-house team, with our Design System as the source. The component rules and the documentation stayed with them, and when the new client came around our developers joined their team rather than replacing it. The collaboration ended with a team that now feels confident and able to grow independently.
07
Results
Johan went from a platform that grew feature by feature to one system four user roles share. Surveys, dashboards, marketplace, onboarding and public profiles follow the same patterns, so a new feature became a configuration question rather than a design project. Their own team runs and extends it, on web and on mobile, for the 200,000 people who use Johan every year.
Related cases
Ready for your next phase?
A 30-minute call is enough to map the fastest path forward.



