You Watched Five People Try Your Feature and Most of Them Could Not Find It
Your team finally ran a usability session. Five people from outside the team were asked to complete a task using the new feature you built, while you watched quietly on a call. Three of them never found the button. One found it and then did not trust what it did. Only one finished without help. You spent six weeks on that feature. Watching it fail in silence is one of the hardest kinds of…
Your team conducted a usability session with five testers unfamiliar with the team. Three of them struggled to locate the new feature's button, while one found it but doubted its functionality. Only one successful user completed the task without assistance. Discovering the feature's shortcomings is one of the most challenging forms of feedback to receive, as it is behavior, not opinion.
This type of feedback is invaluable, as it reveals genuine user struggle, unlike other kinds of feedback which are subjective opinions or untested assumptions. Resist the urge to explain or defend the feature, as the testers were not the target users and may have been influenced by the context. Instead, observe the exact moments of hesitation and note the participants' actions and utterances.
Users excel at indicating where a problem lies but are less reliable at suggesting a solution. If someone suggests making the button red, acknowledge their difficulty in seeing it and collaborate with the design team to determine an effective findability solution. Lastly, express gratitude to the testers for their time and request to observe the next usability session before investing any further development time, as the most cost-effective learning opportunity is to address these issues early.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
