Choosing help
What working with a consultant is actually like
If you've only ever bought agencies or hired staff, an independent engagement can feel unfamiliar. Here's the whole anatomy, first call to handover, so nothing about the process is a surprise.
The short answer
A scoped engagement runs the same way whatever the discipline: a first conversation that's a diagnosis rather than a pitch, a written scope with deliverables and a fixed price, a short setup where you provide access, the work itself with a steady cadence of contact, and an ending designed so the thinking stays with your team.
Your side of the bargain is access and decisions: to the people, data and systems the work depends on, and to whoever can act on what it finds. Engagements fail on missing access far more often than on missing effort.
Before anything is signed
The most important part of the engagement happens before it exists.
The first conversation is a diagnosis, not a pitch
Expect questions about your users, your evidence, what you've tried and who needs to act on the answer. Sometimes the honest outcome is that you don't need a consultant, or need a different discipline than you thought. That call is worth having either way.
Scope goes in writing
Deliverables, timescale, price, and just as important, what's out of scope. A written scope is what lets you judge the work against a promise instead of a feeling, and it's what makes a fixed price possible.
Fixed price means the risk sits with me
If the work takes longer than I estimated, that's my problem, not a revised invoice. It also means I have to scope honestly up front, which is a discipline you want in a consultant regardless of who carries the risk.
While the work runs
The middle of an engagement should feel unremarkable: steady contact, visible progress, no theatre.
Access is the fuel
Depending on the work: analytics, prior research, staging environments, time with stakeholders, and a way to reach real users. Lining this up in the first days is the single biggest thing you can do to make an engagement land. Most delays are access delays.
Cadence is agreed up front
Short regular check-ins and written progress notes, sized to the engagement. A two-week review needs less ceremony than a research programme. What you should never get is silence followed by a big reveal.
Findings surface as they're found
If usability testing exposes something urgent on day two, you hear about it on day two, not in the final report. The report is the record of the findings, not the release date for them.
Your team is in the room
Observing research sessions, joining workshops, seeing the analysis take shape. Knowledge transfer isn't a handover meeting at the end. It's the by-product of doing the work in the open.
How it ends, and what stays
A good engagement is designed backwards from its own exit.
A deliverable you can act on
Findings tied to evidence, prioritised, with a recommended order of attack, whether that's a research report, a service blueprint, an accessibility roadmap or a conversion review. If it can't survive being read without me in the room, it isn't finished.
A walkthrough, not a hand-off
The deliverable gets presented live, questioned, and argued with, including by the people who have to act on it. Disagreement in that session is healthy; it means the findings are being taken seriously enough to test.
Capability stays with the team
Recordings, data, maps, templates and the reasoning behind the recommendations all remain yours. Where the engagement includes mentoring or critique, the explicit goal is that your team needs me less afterwards, not more.
A clear next step, which may be nothing
Some engagements end with a recommended follow-on; many end with 'your team can take it from here'. What you shouldn't experience is an automatic upsell into a retainer. If more work is genuinely warranted, it gets scoped and priced like the first piece.
The same anatomy, nine disciplines
Whether the engagement is a research sprint, a service blueprint, an accessibility review or a conversion diagnosis, it follows the shape above. Pick the discipline your problem lives in.
Start with the first conversation
Pick the engagement that matches your problem. Each one lists its deliverables, timescale and fixed price, or start with a conversation about which one fits. Either way, the diagnosis comes before the invoice.
Still deciding?
Frequently asked questions
How much of my team's time will an engagement take?
Modest but real. Expect a concentrated burst at the start: providing access, a kick-off, introductions to stakeholders. Then light touch through the middle: short check-ins and the occasional question. The one thing worth protecting time for is observation: watching a usability session or joining a workshop does more for your team than any summary of it will.
What happens if the scope turns out to be wrong?
It happens. Diagnosis sometimes reveals that the real problem lives somewhere else, like a conversion review that keeps surfacing information architecture problems. The fixed scope still gets delivered, and the finding itself becomes part of the value: you learn where the problem actually is. Any follow-on work is scoped and priced as its own engagement, not absorbed into a drifting original.
What happens after the engagement ends?
The deliverables, evidence and recordings are yours, and they're written to be acted on without me. Plenty of clients simply take the findings and run. That's the design, not a failure mode. Where teams want ongoing senior input, that exists as its own explicit arrangement, from fractional leadership by the day to critique sessions by the hour, never as an assumed retainer.
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