Hundreds of roles edited one by one. Now it takes at most 8 clicks.

KOR had no real users to talk to yet, so I relied on secondary research and built a persona: John, an operations manager. He values speed and accuracy when changing roles. His pain points are limited time, no time to learn new tools, and the risk of changing the wrong thing by accident. The research pointed to two needed features: filtering roles by entity and service, and multi-selection.

I defined the requirements, assumptions and constraints, and listed open questions to validate with users later.

I sketched many options on paper. I dropped a global-edit concept because it would have changed the core logic of the interface and made it harder to learn. I also tested different placements and styles for the filter and select controls.

I tested high-fidelity prototypes of two designs with three users, two remote and one in person. The second performed much better. The first, a multi-level dropdown, was dropped before the third test because of time. Users wanted stronger multi-edit indicators and more visible filter and selection buttons, but they finished tasks quickly and called the interface intuitive.

The final design centres on multi-selection and filtering, familiar patterns that need little learning. I added three multi-edit indicators: a “Multi-edit mode” info highlight, a change of background colour, and stroke highlights on edited fields. Changes have to be saved manually, with no auto-save, so mistakes can’t slip through unnoticed. Some questions and improvements remain open.

The tight deadline pushed me to prototype fast. The real challenge was making multi-edit not just work but feel secure and reliable, and usability testing gave me first-hand insight into how people actually use it.