Case study · 01

From a 2007 portal to self-service for every business customer

ClientNS Zakelijk
RoleSenior product designer
Year2024–2026
ServicesInteraction design, validation research, usability testing, accessibility
The new Mijn NS Zakelijk start page with task tiles

The context

Every NS-Business Card in the Netherlands was about to move from the OV-chipkaart to the new OV-pas. The portal that had to carry them across went live in 2007, the same year as the first iPhone.

Mijn NS Zakelijk is where organisations, from freelancers to corporates with thousands of employees, order and manage those cards. Their travellers use it to see trips, subscriptions and refunds.

The challenge

Under a 2020 facelift sat an end-of-life Java platform without analytics. We couldn’t see where people got stuck; only customer service could tell us. And they did: 45% of questions about customer details were “How do I change my address?”

Anyone with two roles needed two logins, the top reason customers called. And the OV-pas date was fixed. The scope could move. The deadline couldn’t.

How it unfolded

Drag, swipe or use the arrow keys

Use the left and right arrow keys to move between events.

  • 2007

    The portal goes live

    The original Mijn NS Zakelijk portal
    Same year as the first iPhone
  • 2020

    A fresh coat of paint

    The reskinned portal with a menu of links
    Same end-of-life Java underneath
  • 2021

    Nessie proof of concept

    Mijn NS Zakelijk proof of concept on desktop and mobile
    My first test of the new design system here
  • Discovery

    40+ conversations

    Stakeholder interviews clustered by theme in Miro
    Customer service first, then every company size
  • Scoping

    185 top tasks, one MVP

    Top tasks per role, scored on urgency and importance
    140 made the cut
  • Design

    77 flows for 5 roles

    Employee detail page with card, services and trips
    Map, prototype, test, document. Repeat.
  • Mobile

    Five rounds with Claude

    Five iterations of the mobile start page
    ~170 px saved before the first task
  • Pre-launch

    Audited in production

    Accessibility and UX audit: zero critical findings
    0 critical findings in 44 top tasks
  • Oct 2026

    Live for the OV-pas

    The new personal space for business travellers
    One login. Every business customer.

How I approached it

01

Four things we kept hearing

People trust what they can check, so order status shows wherever it matters. The next step is never obvious, so every flow ends by saying what happens next. Roles confuse more than they help, so each role got its own start page. And for employers it’s all about money, so we built the cost and CO₂ reports they asked for.

02

One login, every role

Many people are both cardholder and contact person; freelancers are often everything at once. Two accounts became one personal login with a role switcher in the sidebar. The price: with two-factor authentication, a department can no longer share an account. We accepted that for security, and said so on the login screen.

Organisation and role switcher in the sidebar
The role switcher
03

Tasks, not menus

Key actions used to hide under “Manage cards and cardholders”, some five clicks deep. Now each role lands on its own start page, led by “Direct regelen”: top tasks as tiles, one click away. Admins start from their people, with every card, order and trip one click further.

The old portal: cards and cardholders search form
Before · the 2007 portal
The new employees overview with filters
After · Mijn NS Zakelijk
04

One widget, 17 statuses

What someone may do with a card depends on order status, contract dates, product and card status, spread over at least five systems. Without one mapping, an archived employee was still offered “Change”. With the SAP and card teams we drew a decision tree behind one core widget. Now there’s one place to fix a rule, and every screen follows.

NS-Business Card overview widget: 17 statuses, 8 products, 1 component
The subscription widget
05

Cutting scope, out loud

The date couldn’t move, so the scope did. Every cut went on a list with its cost written next to it: departments set up by NS on request, no undo after cancelling, two card types side by side until 2027. The one that hurt was search, filters and multiselect. They’re first on the roadmap after go-live.

06

Built for thousands of cards

Large customers are 1% of accounts but hold 63% of all cards. The screens they use every week are designed for volume: approve orders in bulk, see one person in full, and report kilometres and CO₂ saved across the whole organisation.

Orders list with three orders selected for bulk approval
Approve in bulk
Kilometre and CO₂ report per mode of transport
Reports employers asked for

The data was never missing. The mapping was.

Results

Key result1login instead of two accounts
5roles, each with its own start page
77flows designed and documented
0critical findings in the pre-launch audit
B2B portalResearch & validation

What I take with me

  1. 01

    Good is sometimes good enough

    A fixed date forces cuts. Name each one and its cost, and keep the v2 design ready, so a cut is a step, not a dead end.

  2. 02

    In a complex chain, the mapping is the design

    With SAP, identity and card systems behind every screen, the most valuable artefact was often a decision tree, not a screen.

  3. 03

    AI speeds up the searching, not the judgement

    Claude saved the most time on searching, analysing and sorting. Its output is only as good as the context you give it, and the final call stays with the designer.

Next project · Liberty GlobalOne Wi-Fi experience for 20 million users in 8 countries