Process & Governance Recommendations: UX not as a task – but as a way of working

Why this matters

Prevents UX from only happening in individual projects

Creates clear responsibilities – who does what, when, and why

Reduces friction between design, product, and development teams

Makes UX scalable – even as the team grows

Ensures quality and consistency across products and teams

UX that only lives in the project disappears after the project

The most common trap: UX is done well in a project – by committed people – but nothing lasting follows. No process, no accountability, no repetition.

We define together how UX can be systematically embedded in your product development process – from idea to rollout. With clear roles, meaningful rhythms, and lean governance structures that match your organisation's maturity.

01

Process analysis

What does the current development process look like – and where does it break down?

02

UX integration

At which points in the process should UX actively intervene?

03

Roles & responsibilities

Who does what in design, product, development?

04

Research integration

How do user needs regularly feed into the process?

05

Governance structures

Design reviews, DesignOps, UX KPIs – what fits your context?

Typical statements
before the project

What you get

UX process models (embedded in existing product development processes)
Roles and responsibility matrix (RACI)
Integration of UX research & testing (e.g. in sprint rhythm)
Governance proposals (e.g. design review, DesignOps, UX KPIs)