Kick-off & Goal Definition: What should the audit actually find out?

Why this matters

An audit without a clear focus is analysis without direction

Prevents looking in the wrong places

Saves time and resources through targeted review areas

Creates alignment in the team on goals and expectations

Foundation for selecting the appropriate UX methods

Good analysis means knowing what you're looking for beforehand

Every product is different: different user groups, different processes, different weak points. A UX audit that examines everything often delivers less than one that purposefully answers the right questions.

We therefore always start with a structured kick-off in which we define the product context, relevant user groups, and most critical task areas together.

01

Product & context briefing

What is the product, who uses it, what should it achieve?

02

Define user groups

Who is in focus for the audit?

03

Determine review areas

Which templates, flows, or areas will be analysed?

04

Develop goal catalogue

What should the audit specifically answer?

05

Select methods

Which method mix fits the goal and the context?

Typical statements
before the project

What you get

Shared goal catalogue for the audit
Definition of templates or product areas to be reviewed
User group profile & key usage scenarios