Richard Merrick

A Product Designer from the world of video games, specialising in design vision, building research programmes, and early-stage product strategy. Turning ambiguous challenges into clear direction and engaging experiences.

Selected work

Riff

Taking Riff from proof of concept to launch

Riff

Taking Riff from proof of concept to launch

John Lewis app homepage

Integrating UX and setting a direction for the homepage.

John Lewis app homepage

Integrating UX and setting a direction for the homepage.

Curbee checkout

Taking checkout conversion from 2% to 10%

Curbee checkout

Taking checkout conversion from 2% to 10%

Holiday event

A burnout-inducing, expensive event format redesigned into a daily habit that lifted DAU 2.5% and cut production time in half.

Holiday event

A burnout-inducing, expensive event format redesigned into a daily habit that lifted DAU 2.5% and cut production time in half.

Gallery

Take a closer look at some final designs.

How I work

01 Understand

First, I break down what the product actually is. That means pinpointing what's innovative, identifying the core experience users will repeat, and checking that the basics are in place to compete.

02 Zoom out

Once you understand what the product is, you can review it in the right context. When results aren't coming, the instinct is to optimise harder, tweak a button, or add a feature. The problem is usually higher-level.

I map out the full experience, identify what each part is trying to achieve, what data exists for it, and where you need more insights. That review usually reveals the real problem and makes what to do now, next, and later a lot clearer.

03 Move forward

With a clear picture of what to work on, the question becomes how to do it without creating new problems.

I involve the whole team in problem-solving from the start, not just designers and PMs. I design and build in tandem, so engineers aren't waiting for designs to start, technical discoveries feed back into the design before it's too late to change, and everyone is working with the same context.

Changes are incremental so you can see what's working before committing to more.