Menu

Strategy

Concierge Testing

A practical UX and product strategy method for validating service value through real manual delivery before investing in automation.

How to use concierge testing to validate user value, learn from real outcomes, and decide what to build before committing development resources.

4 min read

What it is

Concierge testing is a UX method where a product or is delivered manually to users instead of being automated.

Users receive a real outcome, but behind the scenes a person is doing the work rather than a .

Unlike , users are aware that the is being delivered manually.

This approach is often used to test ideas, , or without building full technology.

The focus is on value, , and outcomes rather than .

The goal is to validate whether the is useful and worth building.

Concierge testing is most useful when the key risk is value uncertainty, not implementation uncertainty.

When to use it

Use this method when you want to validate value before investing in .

It is most useful when:

You are testing a new service or concept
You want to understand real user needs
You need to validate outcomes, not just interactions
You are working with complex or uncertain ideas
You want to reduce development risk

It is less useful when:

the service requires full automation to function
scaling manually is not possible even short-term
users expect instant or real-time responses
Concierge testing is often used in early-stage product development.

Key takeaway

Use concierge testing when you need proof that the outcome is valuable before deciding how much technology to build around it.

How to run it

Set up properly

Be clear on the you are testing, what you will deliver by hand, and what success means. Concierge testing validates whether the outcome is wanted before anything is automated.

Be honest with participants that is manual. Concealing it turns a test into a deception and poisons the relationship you are testing.

Run the method

Concierge testing delivers the manually to real people. It is the fastest way to find out whether the holds before spending on building it.

  1. Offer the to a small number of real users with a genuine need, not to colleagues.
  2. Deliver the outcome by hand, however inelegantly. What matters is whether the result is valuable, not how it was produced.
  3. Interact directly. The conversations around are where you learn what the automated will have to handle.
  4. Observe and closely: whether they come back, what they ask for next, what they do with the output.
  5. Adjust the approach as you learn, since the point is to find the right rather than to test a fixed one.

Resist automating early. Every manual round teaches you something that would have been built wrongly, and the manual is deliberately unscalable.

Capture and make sense of it

The value comes from validating demand before building. After the test, document:

  • Whether people valued the outcome enough to return or pay
  • What they asked for that you had not anticipated
  • The parts of that would be hardest to automate
  • Whether the proposition holds, including when it does not

Use this to decide whether to at all. A concierge test that fails has saved considerably more than it cost.

What to look for

Focus on:

Value: whether the service solves a real problem
Behaviour: how users engage with it
Expectations: what users expect from the service
Return behaviour: whether anybody comes back for it
Demand: whether users want more of it

Where it goes wrong

Most issues come from:

If it doesn’t deliver real value, it’s not worth building.

Testing on colleagues rather than people with the need
Automating before you have learned what the manual version teaches
Concealing that delivery is manual, which makes it a deception
Judging the process rather than whether the outcome was wanted
Delivering once and never seeing whether anybody returns

What you get from it

Done properly, this method gives you:

Evidence of whether the outcome is valued before you build it
Requests you had not anticipated, which shape what to build
The parts of delivery that will be hardest to automate
Permission to stop, when the proposition does not hold

Key takeaway

It helps you prove the idea before investing in technology.

Get in touch

If this sounds like something you need, we can help you validate your ideas through concierge testing before you invest in building them.

No guesswork. No assumptions. Just real value, tested properly.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is concierge testing in UX?

It is a method where a service is delivered manually to test its value.

When should you use concierge testing?

Use it in early stages to validate ideas and services.

How is it different from Wizard of Oz testing?

Users know the service is manual, and the focus is on outcomes rather than simulation.

What can you test with it?

Services, workflows, and complex concepts.

Does concierge testing improve UX?

Yes. It helps ensure you are building something users actually want.

Quick take

If you want to test a service before building it, deliver it manually.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer