the validation brief

there’s a type of brief that looks like a research question but isn’t.

it comes in as: “we want to understand how users feel about X.” or “we want to know if this direction is right.” it has the shape of genuine inquiry. and maybe it started that way. but by the time it reaches you, someone in the organisation already has a strong view about the answer. the work has been framed by that view. the options on the table reflect it. and what’s actually being asked is: find evidence that supports where we’re already heading.

i’ve been on both sides of this. i’ve been the researcher handed a brief that turned out to be a validation exercise. and i’ve been the person who, if i’m honest, needed validation more than i needed the truth.

the reason this is worth naming: validation briefs produce validation findings. the way you design a study shapes what you can find in it. if the question is already decided, the research will confirm it — not because anyone cheated, but because that’s what happens when you go looking for evidence of a hypothesis you’re attached to.

which means you can spend four weeks doing rigorous work, show up to the readout with a deck full of quotes and themes, and still not have learned anything that would change the decision. the decision was never in question. the research was cover.

i don’t think most people doing this are being cynical. they’re doing what the organisation requires, which is: don’t make a significant decision without research to back it. so the decision gets made, and then the research gets done. the sequence is just slightly out of order.

but if you’re the person running the research, that matters. because you can do honest work inside a validation brief — you just have to know that’s what it is. then you can ask: what would have to be true for us to change course? and you can look for that specifically, rather than looking for confirmation that the current course is fine.

the findings that challenge the direction are always in there somewhere. if you’re not looking for them, you won’t surface them. if you are, you’ll find them, and then you have a choice about what to do with them.

the harder situation is when you find the challenging thing and the organisation doesn’t want to hear it.

i’ve been in that room. the research is done. the synthesis is honest. the finding is: the assumption this direction is built on isn’t holding. and the response is some version of: “that’s interesting, but we’re committed to this path.” which is a reasonable thing to say — sometimes you are committed, and knowing the assumption is soft doesn’t change the bet you’re making. that’s a legitimate call.

the problem is when it gets papered over instead. the finding disappears from the deck. the direction proceeds as if the challenge never came up. and now the organisation has paid for research that made them feel like they did due diligence, while running on an assumption nobody’s willing to test.

i’m not trying to make the validation brief sound like a moral failure. it’s a structural reality of how decisions get made inside organisations. the brief you get is rarely the clean, open question you’d design from scratch.

but knowing which brief you’re actually working on — discovery or validation — changes how you approach it, what you surface, and how you talk about what you found.

the clearest signal i’ve found: at the start of the engagement, ask what it would take to change the decision. if no one can answer, you’re validating.

if you’ve got a body of research that produced a lot of findings but nothing that actually moved anything — i offer synthesis. sometimes the useful insight is in there; it just wasn’t framed in a way that created any traction. $300.