The right method at the right time

When should you conduct an expert review?

The best time is before important decisions become expensive to change, but after enough of the service exists to assess real user journeys.

7 min read

Before a redesign

Before designing the new service, understand the old one. An expert review can show which problems stem from structure, language, functionality or missing feedback, and which parts already work well and should be preserved.

Without this foundation, the redesign may focus on what is easiest to see rather than what matters most to the user.

When a prototype begins to take shape

A clickable prototype can be reviewed before development begins. At this stage, changing sequence, terminology, navigation and interaction patterns is still relatively inexpensive. The review can also identify assumptions that should be taken into usability testing.

The prototype need not be visually finished, but it must contain enough detail for the important choices and actions to be understood.

Before launch

Immediately before launch, there is less room for change, but the consequences of simple mistakes are greater. A focused review can identify blockers, unclear confirmations, mobile display problems and journeys that fail to connect from beginning to end.

Findings should be prioritised firmly at this stage: What must be resolved before launch? What belongs in the first round of improvements? What can wait?

When the data shows that something is wrong

Analytics can show where users drop out, but not always why. Customer service may see recurring questions without knowing which design decision causes them. An expert review can examine the relevant steps and formulate concrete hypotheses and improvements.

When the team has become too close to the service

The people building a service know its terminology, exceptions and shortcuts. That knowledge makes them efficient while also making it harder to see what a new user is missing.

This is especially visible in services that have grown through many small changes. Each change may have made sense on its own, while the whole service has acquired inconsistent language, competing navigation patterns or unclear priorities.

When the improvement backlog has become too long

If the backlog contains more possible improvements than the team can deliver, you do not need more ideas. You need an independent assessment of which problems have the greatest consequences and which measures could resolve several problems at once.

The report does not replace product management, but it provides a clearer basis for deciding what should come first.

When is it not the right time?

An expert review is rarely the right first step when the service is only a loose idea, when the target audience is unknown or when the greatest uncertainty is whether the need exists. Start with user research, concept development or product strategy instead.

The method is also insufficient if you need evidence of what users actually do, a full WCAG audit, penetration testing or a technical performance analysis. A good initial meeting should make these boundaries clear before you place an order.

Professional foundation

The assessments draw on more than 15 years of experience with digital products, established interaction design and usability principles, and the specific context of each service. See also ISO 9241-11 on usability and Nielsen Norman Group's heuristic evaluation workbook.

Do you have a service I should review?

Request an expert review

Briefly tell me which service you would like reviewed and which questions you want answered. I will reply with a proposed scope, delivery time and price.

Keep reading