Straight answers
before you commit.

In an expert review, I go through the product myself and record what’s broken or confusing. In usability testing, I watch real people try to do real tasks. Both are useful. They answer different questions, and I won’t pass one off as the other.

Yes. Most people do. Tell me what’s bugging you, who uses the product and what they’re trying to do. The method finder gives you a starting point, and we pick the method together on the first call.

Yes, as research. I check what your analytics can and can’t tell you, find where people get stuck, and give you ranked ideas to test and a plan for testing them. I don’t promise an uplift. Anyone who does is guessing.

Me, Brian McCabe, from the first call to the findings. The proposal names who does what and which methods we’ll use.

The five case studies under Work are client projects delivered end to end. Each is a written account of the research, findings and recommendations.

The other examples show how I work: a review of Homegrown, my own project; a self-review of my previous website; a review of Hexis; and example scenarios.

No. Made-up personas can help frame questions. They’re not people, and they can’t tell you what real people do.

No. Recording needs everyone’s agreement and consent. We agree recruitment, who sees the recordings and when they’re deleted before any session runs.

It depends on what you need to find out. We agree the scope first. Then you get a written proposal with the price, what drives it and what’s not included.

No. I find the problems and tell you what to fix first. You choose who fixes them. That keeps the advice independent.

Only if we agree it up front. A fix isn’t verified until someone has checked it, so a retest is worth planning for.