How to run a customer interview without leading the user
Asking paying customers if they like a new feature usually yields polite nods that mean nothing. During our user research sessions last quarter, I noticed participants would enthusiastically agree with my ideas just to be nice.
The shift happened when I stopped asking hypothetical questions about future features and started asking about their past behavior. Instead of wondering if they would use an automated report builder, I asked when they last built a manual spreadsheet and how long it took.
That specific timeline revealed their actual pain points without biasing their answers with my assumptions. We redesigned the workflow around real bottlenecks, which cut user drop-off by forty percent in the next release cycle.
Focus exclusively on what users did last week, not what they plan to do next month.
Watch where they hesitate on their current screens instead of listening to their feature requests.
Uncovering real habits saves weeks of building the wrong thing. How do you separate polite feedback from genuine user demand during discovery calls?
Replies
Yeah for sure, I recently watched
Eric Migicovsky's video about a similar concept.Hypotheticals are definitely bad because it's something you or the user has never experienced before. And when that happens, users usually incline towards the "nicer" side instead of being realistic.
Great tip!
Totally agree, we’re building an AI presentation tool. Would you start by asking founders to walk through their last deck, or watch them make a small edit? I’m trying to understand where the time actually goes.