# Deep Problem Knowledge Predicts Untested Solutions ## Claim The better you understand a user problem, the more likely you are to skip validating your solution to it, because problem certainty feels like solution certainty. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds where the same person or team owns both problem research and solution design, so no outside party has to be persuaded the solution actually works. - Breaks where those roles are separated and the solution designer has to convince the researcher — the handoff forces validation as a side effect of the org structure. - This describes a bias mechanism, not a claim that expert-designed solutions are usually wrong — only that they're tested less than their apparent certainty would predict. ## Evidence A WordPress core contributor's retrospective on a punted 7.1 Site Editor feature: the team had deep, well-documented knowledge of the underlying user problem (from FSE Outreach Program testing) but that knowledge didn't substitute for testing the actual fix, and the feature was punted for lack of validated design. > [!quote] > Knowing a user problem deeply doesn't replace user feedback on the solution at hand. ## Links - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — because applies-in; this is a recurring product-process failure mode worth checking against release plans generally. - [[3. Resources/Permanent Notes/A Test That Cannot Return No Cannot Validate Yes]] — because extends; both describe conditions under which a check stops functioning as a real check. ## Tests / falsifiers - Compare feature ship rates and post-launch revision rates for teams that separate problem-research and solution-design roles versus teams where one team does both. If separated teams don't show fewer post-launch revisions, the claim is weaker than stated. - Find a case where deep problem expertise co-existed with rigorous solution testing by the same team, absent any external validation requirement — a genuine counterexample to the mechanism. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/Behind the scenes of a punted feature of 7.1]] — reports the punt's stated causes and the team's own retrospective framing.