Why founders should sit in on user research

Every founder says they're user-obsessed. Fewer have actually watched a stranger use their product without any help, in the last six months. There's a specific kind of conviction that only comes from being in the room — or on the call — when it happens, and no summary deck fully replaces it.

A report tells you what happened. Watching tells you how it felt

A researcher can write "3 of 5 users struggled to find the settings menu," and that's true and useful. What doesn't survive translation is the two-second pause before a user clicks the wrong thing, the sigh when they finally find it, or the moment they say "oh, I just assumed it would be here" — the exact language your onboarding copy should be arguing against.

It changes what gets prioritized

Teams that only read research reports tend to prioritize the loudest finding. Teams that watch the sessions prioritize the ones that made them personally uncomfortable — and that discomfort is usually a more honest signal than a severity score in a spreadsheet.

It's also a gut check on your own assumptions

Founders build strong internal models of their product because they use it every day, at expert speed, with full context. Ninety minutes of watching real users flounder through the same screens is one of the fastest ways to recalibrate that model back to reality.

How to actually make time for it

You don't need to sit in on every session. Pick two or three across a research round — ideally including at least one where you expect the product to perform well. Watching a session go badly when you were confident it wouldn't is the single most useful hour you can spend that week.