The XY Problem
Summary
The XY problem describes a scenario where individuals ask about their attempted solution rather than the underlying problem, leading to inefficiency in tech help-seeking. It provides guidelines to improve communication by sharing broader context and details.
View Cached Full Text
Cached at: 08/25/26, 03:44 PM
Similar Articles
Am I the problem? Interviewing another team to find out
A DevOps engineer recounts interviewing the infrastructure team at ngrok to compare how other teams handle technical disagreements, prompting a personal reexamination of his own work relationships and career.
@kentcdodds: Problem -> Solution -> Problems -> Solutions -> Problems -> ... think... replace previous solution with better solution…
Kent C. Dodds shares a reflection on the iterative cycle of solving problems in software development, emphasizing replacing previous solutions with better ones to reduce complexity.
Don't answer the first question
The article argues that engineers should resist immediately answering users' first questions, instead using follow-up questions to uncover the deeper problem, which improves both the user's mental model and the product itself, using examples from the Perfetto performance debugging tool.
Why Problem Statements Aren't Enough
This essay explains why problem statements alone are insufficient for career growth, introducing the concept of 'contextual range' across technical, organizational, and business contexts that engineers need to understand.
@thdxr: for so many products, the first step after deciding to try it is some survey on "what is your role, where did you hear …
A tech user complains about the prevalence of surveys immediately after deciding to try a product, questioning why this UX design is so common.