adair16caldwell
0 active listings
Last online 4 months ago
Registered for 5+ months
Send message
All seller items (0)
skitterphoto.com/photographers/2896844/epstein-andresen
About seller
A widely cited attribution to Henry Ford asserts that if he had asked customers what they wanted, they would have said a faster horse. The attribution is probably apocryphal, but the distinction it captures is genuine and important for product design: what users say they want and what would actually solve their problems are often different things. Users articulate desires in terms of familiar solutions — more of what they already have, or modifications to what they know — not in terms of the underlying needs that their desired solution would serve. Design that responds to stated wants without understanding underlying needs produces incremental improvements to existing solutions rather than solutions that genuinely serve the need better. https://dnsk.work/blog/ux-iceberg-problem-research-excuse The Root Need ProblemUsers are not typically aware of their underlying needs in a form that is useful for design, because the need is experienced as dissatisfaction or a problem rather than as an explicitly articulated requirement. A user who asks for a "search that actually works" is expressing dissatisfaction, not specifying a requirement. The underlying need — finding the specific item or information they are looking for with reasonable effort — might be served better by improving search or by a better navigation structure or by a recommendation system that surfaces the right item without search. Responding to the stated want ("fix search") without investigating the underlying need can produce an improved search that does not serve users better if the real problem is that they are using search to compensate for navigation that fails to get them where they want to go.Separating Problem and Solution SpacesEffective UX research maintains a clear separation between the problem space — the users' needs, contexts, and goals — and the solution space — the specific features and designs that might serve those needs. Research activities that operate in the problem space (what are users trying to accomplish? what frustrates or blocks them?) provide the foundation for design that genuinely serves needs. Research activities that operate in the solution space (which of these two designs do users prefer?) provide guidance on execution. Teams that skip problem space research and move immediately to solution space validation risk validating the wrong solution — one that users prefer among the options they are shown, but that does not serve their underlying needs as well as a different solution they were not shown.Bridging Needs and FeaturesBridging from understood user needs to specific product features requires explicit reasoning that is often skipped in practice. A product team that understands a user need should be able to articulate why the features they are building serve that need — what specific aspect of the need does this feature address, how does it address it, and how would we know if it was addressing it effectively? This reasoning, made explicit, is more testable and more communicable than the implicit "this feature serves users" assumption that most features carry. When the reasoning is made explicit, gaps and weaknesses in the connection between needs and features become visible, allowing the team to either strengthen the features or reconsider whether they are the right response to the need.
adair16caldwell's listings
User has no active listings