IBZ, view case
Design system · Accessibility
A shared foundation for complex public services.
A design system for Belgium’s Immigration Office, with 180+ reusable components supporting clearer, more accessible workflows across 10+ projects.
Expertise /Software UX
Your software works.
Make using it feel easier.
Freelance software UX design for product teams across the Netherlands. I help untangle complex workflows, turn ideas into usable interfaces, and give growing products a more consistent experience.
Less figuring it out. More getting it done.
01 / A good fit
Does this sound familiar?
For teams with capable business software that takes too much effort to use. Perhaps the same task behaves differently across applications, the next step is unclear, or new features are making the product harder to navigate.
02 / The approach
Understand the task before changing the screen.
We start with what someone is trying to achieve and where the current route becomes difficult. Existing feedback, product knowledge, and the interface itself help us identify what needs a closer look. I make assumptions visible so the team can decide what to validate.
A journey or flow gives us a shared view of the problem. It also helps separate issues that need a design change from questions about content, business rules, or how the product works behind the scenes.
03 / The approach
Make the next version something you can discuss.
I turn the direction into screen flows, interface designs, and prototypes. These give the team something specific to examine: what appears at each step, what a person can do, and what happens when something goes wrong.
We agree the appropriate validation and development handover for the project. States, reusable patterns, and the reasoning behind a decision should travel with the screens, so implementation does not depend on guesswork.
04 / The approach
Help the product grow consistently.
When several applications share the same tasks, a design system can make those patterns easier to maintain. Shared navigation, components, and documentation give designers and developers a common reference.
My IBZ work involved a system with 180+ components across 10+ projects. The Telenet Business case shows work on shared navigation and a component library. Those examples describe delivered scope; the right size of system for your product depends on its own needs.
05 / What we can work on
A scope we agree together.
- A clearer map of user journeys and product flows
- Prototypes and interface designs for the agreed scope
- Reusable patterns or design-system work where useful
- Documentation and design handover for the team building it
We agree the deliverables, timing, and cost in a proposal before starting. The project takes shape around what you need.
06 / In practice
A look at the work.
Telenet Business, view case
Software UX · Component library
Separate applications. One connected experience.
Connecting separate applications through shared navigation, a component library, and clear documentation for a more consistent customer experience.
07 / Before we start
Fair questions.
Can you work with our existing product team?
Yes. We agree the contribution you need, how decisions are made, and how design fits your development process. You work directly with me, with clear boundaries around the agreed scope.
Do we need a complete redesign?
Not necessarily. A focused change to one important flow can be a useful starting point. We look at the problem and decide how much needs to change before committing to a broader redesign.
Do we need a design system?
A shared system helps when repeated interface decisions are causing inconsistency or extra work. A small set of documented patterns may be enough at first. It should solve a real coordination problem rather than become another project to maintain.
How are cost and timing decided?
We define the problem, the contribution, and the deliverables together. The proposal sets out scope, collaboration, cost, and timing before the work begins. Research or development beyond that scope is discussed explicitly.