← ClaudeAtlas

problem-validationlisted

Validate whether a problem is worth solving before building anything. Use when asked to validate a problem, assess problem-solution fit, decide whether to build something, or evaluate if a problem is real. Scores problems on frequency, intensity, willingness to pay, and existing workarounds.
AashutoshR2062/productskills · ★ 2 · AI & Automation · score 75
Install: claude install-skill AashutoshR2062/productskills
Validate problems with evidence, not opinions. A problem worth solving is one that people encounter frequently, feel intensely, and have already tried to solve. If nobody has attempted a workaround, the problem isn't painful enough to build for. ## Scoring Framework Rate each dimension 1-5 based on evidence: ### Frequency (How often does this happen?) - 5: Daily or multiple times per day - 4: Weekly - 3: Monthly - 2: Quarterly - 1: Rarely or once ### Intensity (How painful is it when it happens?) - 5: Blocks critical work, causes real losses (money, time, reputation) - 4: Major friction, significant workarounds needed - 3: Annoying but manageable - 2: Minor inconvenience - 1: Barely noticeable ### Existing Workarounds (Are people already trying to solve it?) - 5: Paying for imperfect solutions or built custom tools - 4: Cobbled together multi-tool workflows (spreadsheets + email + manual steps) - 3: Have a basic process but it's tedious - 2: Occasionally Google for solutions - 1: Haven't tried to solve it ### Willingness to Pay (Would they pay to make this go away?) - 5: Already spending money on partial solutions - 4: Have explicitly said they'd pay (and named a number) - 3: Would "probably" pay (hypothetical — discount this) - 2: Want it free - 1: Haven't considered paying **Validation Score = Frequency x Intensity x Workarounds x WTP** - **250+**: Strong signal. Build. - **100-249**: Promising. Needs more evidence on weak dimensions. - **Under 100**: Weak. Either p