Zaak & Taak

Every process, one board.

Designing a configurable kanban way of working for ViewPoint, so housing corporations can shape their own processes and guide employees through cases step by step.

Year

2025–2026

Role

UX designer (sole designer)

Team size

Me, product owner, 2 testers, 6 developers

Duration

Not specified

Company

Itris BV, ViewPoint

Tools

Figma, FigJam, Miro, Jira, Microsoft 365, Claude (coded prototypes)

Zaak & Taak board layout with filter panel







In pilot with housing corporations.

Context

A new way of working, inside a product people use all day.

ViewPoint is the ERP Itris builds for Dutch housing corporations. Employees use it every day to manage tenants, properties, cases and payments.

Zaak & Taak brings process-driven work into ViewPoint. Admins build kanban boards for their own processes, with filters deciding which cases show up. They assign those boards to the people who do the work. End users then move through cases step by step, and can filter further to focus on what matters to them.

My brief: as the only designer on the team, design Zaak & Taak for both sides: the admins who set up processes and the employees who work in them.

Before -> finding work instead of doing it

Long lists that showed everything, except progress.

Cases were handled through long lists and search screens. They showed what existed, but not where a case stood or what had to happen next. The process lived in people’s heads, not in the tool.

The interface didn’t help either. It looked and felt like it came from 2006:

  • No hierarchy. Every action was a bright blue button with the same weight, so nothing pointed to the next step.

  • Poor accessibility. White text on light blue buttons had too little contrast to read comfortably.

  • Repetition everywhere. Every row had its own “Uitvoeren” link, and the same actions came back as buttons in the detail area.

  • A cramped layout. Case details slid up from the bottom of the screen, squeezing the list and pushing information out of view.

Old ViewPoint activity list with many blue buttons and a detail panel sliding up from the bottom

The challenge -> one design, many processes

No two corporations work the same way.

ViewPoint is a very flexible product. Every customer environment is set up differently, and every process inside it has its own steps. So I couldn’t design one fixed flow. The design had to be flexible and scalable enough to work for processes I would never see.

After -> one board per process

Admins shape the process, users follow it.

For admins. Admins manage every board from one overview. It shows each board’s status, the processes feeding it, the roles and the assigned users at a glance, with quick actions like duplicate or set inactive. Corporations can set boards up themselves, or Itris consultants can do it for them, which also gives Itris a service to offer.

Mijn procesborden overview with status, processes, roles and assigned users per board

Each board is set up in three tabs: processen (which case types and workflows feed the board), bordindeling (the columns and groups) and behandelaars (who works on it).

Process board setup showing the case types and workflows added to the board

A filter system that scales. Every column, group and step can carry its own filters. The filter builder supports nested and/or groups, a pattern people know from tools like Notion, so even complex rules stay readable. That is what makes one design work for any process.

Board layout with columns and groups, and the nested filter builder panel

For end users. Users see their boards as tabs, so switching between processes takes one click. Cases move through the columns step by step, and selecting a card opens its details in a side panel, without leaving the board.

End-user kanban board with the filter panel on the left and case details on the right

Filters that stay personal. On top of the admin’s filters, users can filter by assignee, creation date, case type, priority and more. Combinations they use often can be saved as their own filters, so their daily view is always one click away. None of this changes the process for anyone else.

Group by what matters. Users can group the board, for example by assignee. That turns it into swimlanes, so it’s easy to see who is working on what.

Kanban board grouped by assignee into swimlanes

Room to work. Case details now open in a side panel instead of sliding up from the bottom. Users can drag it wider or narrower, so they decide how much space goes to the board and how much to the case.

Resizing the case detail panel by dragging its edge

A new look for ViewPoint

Where the new visual direction started.

Zaak & Taak was also where ViewPoint’s new visual style began, including the purple that now sets the tone for new features. Itris had no design system yet, so I set one up and worked with the developers on a new component library to match. The same foundation was later used for the AI assistant.

Bridge -> how we got there

Customers first, then prototypes, then a foundation to build on.

  1. Listen to customers. Multiple client interviews and sessions to understand how corporations actually handle cases.

  2. Borrow from tools people know. Filter patterns based on best practice from tools like Notion.

  3. Prototype in code. Screens in Figma, plus working prototypes built with Claude Code to test ideas and make them concrete for developers.

  4. Build the foundation together. A new design system and component library, set up with the developers.

  5. Test continuously. Tight loops with the two testers and checks with users.

The result

Zaak & Taak is in pilot with housing corporations, with a broader rollout to follow. It gives ViewPoint a new, process-driven way of working, and a visual and component foundation that new features now build on.

Reflection

  • Design the system, not the flow. With this much configurability, I wasn’t designing a process. I was designing the tool admins use to build processes. That changes every decision, from the wording to the defaults.

  • A solid core first. With so many possible processes, it was tempting to support everything. Scoping to a strong core and phasing the rest kept the product shippable and gave the pilot something focused to test.

2025–2026

2025–2026