USABILITY TESTING SPRINT

Stop relying on assumptions. See what real users actually do.

A focused usability testing sprint with six moderated remote sessions, giving your team clear evidence of what works, where users struggle and what should change next.

You'll get direct insight from representative users, prioritised findings and practical recommendations your team can act on with more confidence.

Book a free scoping call

A free 30-minute call to discuss what you want to test, what you need to learn and the most useful next step.

THE PROBLEM

Do you need stronger evidence before deciding what to change?

Your team may already have a live product, journey or prototype and a clear sense of what needs testing.

What is often missing is direct evidence of how representative users actually experience it.

A Usability Testing Sprint helps you move beyond assumptions, internal opinion and stakeholder debate by observing where users succeed, where they struggle and why.

You are relying on internal opinion

The team has different views about whether the experience works, but no direct user evidence to settle the debate.

You are relying on internal opinion

The team has different views about whether the experience works, but no direct user evidence to settle the debate.

You have a prototype but do not know whether it is ready

The proposed solution looks convincing internally, but has not yet been tested with the people expected to use it.

Users are struggling, but the reasons are unclear

Analytics, support feedback or product performance may indicate a problem without explaining what is causing it.

Users are struggling, but the reasons are unclear

Analytics, support feedback or product performance may indicate a problem without explaining what is causing it.

Important tasks may be harder than expected

Users may be hesitating, misunderstanding content, missing key actions or taking longer than the team anticipated.

You need confidence before build or release

The team wants to identify problems before more time and budget are committed to development.

Existing user assumptions need challenging

Current personas or audience expectations may not fully reflect how real users behave, what they expect or what matters to them.

Existing user assumptions need challenging

Current personas or audience expectations may not fully reflect how real users behave, what they expect or what matters to them.

THE OUTCOME

Clear evidence of what works, where users struggle and what to improve

Direct user evidence

See how representative users understand and interact with the product, journey or prototype.

Clearer understanding of user behaviour

Understand not only what participants do, but the expectations, experience and context shaping their decisions.

Prioritised usability issues

Separate significant recurring problems from isolated observations and lower-priority concerns.

Practical recommendations

Get clear direction on what should be changed, simplified, investigated or tested further.

Better team alignment

Give product, design, delivery and operational stakeholders shared evidence rather than competing interpretations.

More confident product decisions

Decide whether the experience is ready to move forward, needs refinement or requires a more substantial rethink.

SCOPE

One defined product area, journey, feature or prototype

The sprint focuses on one agreed testing objective rather than trying to assess an entire product.

one end-to-end journey

one product feature

one live product area

one interactive prototype

one service flow

one internal workflow

a small number of closely related journeys

a proposed redesign that needs validation

✓ A good scope

Test whether customers can confidently manage their personal and payment details within the account area.

✗ A poor scope

Test the account area, checkout, support centre and mobile onboarding in one study.

Closely related journeys can be included where they sit within the same user context — for example, changing an address and updating stored payment information both sit within account management and support one connected research objective.

The scope is agreed before the sprint begins so the sessions remain focused and useful.

WHAT YOU RECEIVE

What you get from the Usability Testing Sprint

The sprint is designed to give your team clear, usable evidence — not a large research report that is difficult to act on.

01

Journey review summary

A concise written summary of what's working, what isn't, and why it matters.

02

Annotated journey findings

Screen-by-screen notes pinpointing where users hesitate, stall or drop out.

03

Prioritised issue list

Issues ranked by likely impact and effort, so you know where to start.

04

Practical recommendations

Clear, actionable suggestions your team can pick up straight away.

05

Playback session

A live walkthrough of the findings, with time for questions and discussion.

01

Research objective and scope

A focused definition of what is being tested, why it matters and what the team needs to learn.

02

Test plan and discussion guide

A structured session plan covering contextual questions, tasks, prompts and closing reflections.

03

Six moderated remote sessions

Six sessions with one primary participant group, usually lasting around 60 minutes each.

04

Contextual participant interview

A short introductory discussion at the start of each session to understand the participant's background, behaviours, expectations and relationship with the product or task.

05

Live client observation

Relevant stakeholders can observe sessions live, helping the team see user behaviour first-hand.

06

Session recordings

Sessions are recorded for analysis and note-taking, subject to participant consent and the client's data-handling requirements.

07

Synthesised findings

The evidence is reviewed across sessions to identify patterns, repeated issues and important differences in behaviour.

08

Prioritised usability issues

The main findings are organised by importance, severity and likely effect on the experience.

09

Practical recommendations

Clear guidance on what should be improved, simplified, explored further or retested.

10

Playback session

A live walkthrough of the findings, supporting evidence, implications and recommended next steps.

THE SESSIONS

Enough structure to stay focused — enough flexibility to learn

Each session will usually last around 60 minutes.

The exact structure will depend on what is being tested and what the team needs to learn.

Trying to fit too many tasks into one session is counterproductive. Where the proposed scope is too broad, I will recommend narrowing it so there is enough time to observe behaviour properly and explore the reasons behind it.

Introductions, consent and contextual questions

Usability tasks and follow-up probing

Overall reflection and closing questions

BEST FIT

Best suited to teams that need direct evidence before moving forward

've conducted usability testing across public and private sector, including government services, regulated products and consumer platforms — working with teams at the Home Office, HMCTS, DfE and GAMSTOP among others.

Teams with a live product

Known friction

Support issues

Unclear task performance

Teams with a live product

Known friction

Support issues

Unclear task performance

Teams with a new prototype

Pre-build validation

Interaction testing

Design confidence

Teams with a new prototype

Pre-build validation

Interaction testing

Design confidence

Fintech and regulated products

Complex journeys

Trust-sensitive tasks

Compliance-heavy flows

Fintech and regulated products

Complex journeys

Trust-sensitive tasks

Compliance-heavy flows

Enterprise and internal platforms

Operational workflows

Admin tools

Complex interfaces

Teams preparing for release

Risk reduction

Priority fixes

Stakeholder confidence

Teams preparing for release

Risk reduction

Priority fixes

Stakeholder confidence

Teams challenging product assumptions

Persona comparison

User expectations

Behavioural evidence

It is well suited to heads of product, design leads, product managers, service owners and founders who need focused evidence without commissioning a large research programme.

CHOOSING THE RIGHT SERVICE

Is this the right next step?

A Usability Testing Sprint is the right fit when:

You already have something that users can interact with

You want to understand where and why users struggle

The work can be contained within one defined testing objective

You need evidence from representative users

You need confidence before build, release or further investment

Not sure this is the right service?

A Journey Review is a better fit when one end-to-end journey is underperforming but the causes are unclear. A UX Review is a better fit when the problem spans a wider product area and the team needs expert diagnosis and priorities first. A Prototype Sprint is a better fit when the problem is understood but there is not yet a realistic solution to test.

SCOPE

What this is not

The Usability Testing Sprint is a focused qualitative research engagement.

Participant recruitment or incentive management — Quantitative validation or statistically representative research

A redesign of the tested experience — Accessibility certification

esting several unrelated journeys in one study — A full discovery or persona-development programme

Broad discovery or strategy — A detailed technical specification

The sprint is about observing real users, identifying important usability issues and giving the team a clear next step.

INVESTMENT

Clear scope, fixed fee

The price is fixed and visible up front. You know what you're getting, what it costs, and roughly how long it takes before you commit.

PROTOTYPE / FLOW SPRINT

From

£3,200

For a focused usability testing sprint covering one agreed testing objective, one primary participant group and six moderated remote sessions.

Most standard sprints are delivered within 7–10 working days once the scope, test material and participants are ready.

The starting price assumes client-supplied participants. The final price may be higher where the work involves additional participants, longer sessions, multiple participant groups or specialist data-handling requirements. This will be confirmed before work begins.

Book a free scoping call

THE PROCESS

How the Usability Testing Sprint works

1

Tell me what you want to test

Submit a short enquiry describing the product, journey or prototype, what you already know and what you need to learn.

1

Tell me what you want to test

Submit a short enquiry describing the product, journey or prototype, what you already know and what you need to learn.

2

Book a free scoping call

We discuss the research objective, participant profile, test material and what a useful outcome would look like.

2

Book a free scoping call

We discuss the research objective, participant profile, test material and what a useful outcome would look like.

3

Agree the scope and fee

I confirm the testing objective, participant group, sessions, timing and fixed fee before work begins.

3

Agree the scope and fee

I confirm the testing objective, participant group, sessions, timing and fixed fee before work begins.

4

Prepare and conduct the sessions

I review the product or prototype, create the test plan and moderate six remote sessions.

4

Prepare and conduct the sessions

I review the product or prototype, create the test plan and moderate six remote sessions.

5

Playback and next steps

We walk through the findings, evidence and implications together and agree the most useful next move.

5

Playback and next steps

We walk through the findings, evidence and implications together and agree the most useful next move.

4

Review and diagnosis

The focused review of the journey, end to end.

5

Playback and next steps

A live walk-through of findings and what to do next.

WHAT'S NEXT

Use the findings to make a better-informed decision

Some teams will take the recommendations forward internally. Others will need support refining the prototype, redesigning the experience or testing the next iteration.

POSSIBLE NEXT STEPS

Prototype refinement

Prioritised product improvements

Stakeholder decision-making

Further design or redesign work

A second round of testing

A wider UX or product design engagement

The sprint gives you the evidence needed to decide with more confidence.

BOOK A CALL

Stop relying on assumptions. See what real users actually do.

A focused usability testing sprint gives your team direct evidence of what works, where users struggle and what should change next.

Book a free 30-minute call to discuss what you want to test, what you need to learn and whether a Usability Testing Sprint is the right next step.

Book a free scoping call