product-framinglisted

# Product Framing Use before interface recommendations when problem, user outcome, segment, or evidence is unclear. Goal: prevent designing the wrong screen for the wrong reason, not create workshop artifacts. ## Core Model Frame: 1. User/context: actor, situation, constraints. 2. Need/job: progress sought. 3. Outcome: observable user or business state to improve. 4. Opportunity: pain, motivation, barrier, or unmet need. 5. Solution bet: candidate interface or behavior change. 6. Evidence: research, analytics, support, observation, or source. 7. Metric/counter-metric: value signal and guardrail. Evidence strength: user behavior, usability sessions, analytics, support logs, and production traces outrank stakeholder preference; primary standards/platform guidance outrank blog summaries; heuristics are risk signals, not proof. Frameworks: - Double Diamond: discover evidence, define problem/success, develop bets, deliver smallest testable intervention. - Opportunity Solution Tree: outcome -> opportunities -> solution bets -> evidence/criteria. - HEART/GSM: happiness, engagement, adoption, retention, task success; goal -> signal -> metric; counter-metric. ## Questions To Resolve Ask only if missing context would materially change the recommendation: - Which user segment is this for? - What task or outcome matters most? - Is the main risk desirability, usability, feasibility, viability, or trust? - What evidence already exists? - What existing product or workflow should t