"You talked to users. You ran the research. Created prototypes, did user testing and iteration, and shipped a solution you thought might genuinely solve the problem. But then it launches, and six weeks later, nothing's changed. When you go back to find out why, you discover the workaround: a word-of-mouth process, an unofficial channel, a habit so ingrained that nobody thought to mention it."
"Nobody hid this from you. It just never came up - because you asked about the feature and they answered about it. The workaround was so normal to them it didn't register as something worth mentioning. This isn't a research failure. It's the question that was never asked: How are users currently seeking help with this?"
"If you're working in B2B design, this is one of the most important questions you can make a habit of asking. This is a more common problem in B2B environments, because employees don't choose their tools: they're required to use them."
Product teams can follow rigorous research and development processes—conducting user interviews, prototyping, testing, and iterating—yet still launch solutions that users don't adopt. The disconnect often stems from overlooked workarounds: informal channels, word-of-mouth processes, or ingrained habits that users consider so normal they don't mention them during research. This occurs because research typically focuses on specific features rather than exploring current help-seeking behaviors. In B2B environments, this problem intensifies since employees must use assigned tools regardless of preference. The critical missing question is not about the proposed solution but about existing practices: How are users currently seeking help? Understanding these informal processes reveals why new features may fail to gain traction and what barriers prevent adoption.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]