Produce a Problem Definition Pack in Markdown (in-chat; or as files if the user requests):
1) Context snapshot (product, user, trigger, decision, constraints) 2) Problem statement (1-liner + expanded) + why now 3) JTBD (primary job + key sub-jobs) + target segment notes 4) Current alternatives (including analog/non-digital) + gaps + switching costs 5) Evidence & assumptions log (what we know vs what we’re guessing)
6) Success criteria (outcome metric(s), leading indicators) + guardrails 7) Scope boundaries (in/out, non-goals, dependencies) 8) Prototype / learning plan (fast prototype + tests to de-risk) 9) Risks / Open questions / Next steps (always included)
Defina un problema de producto y produzca un paquete de definición de problema (enunciado del problema, JTBD, alternativas actuales, evidencia y suposiciones, métricas de éxito, límites de alcance, prototipo/plan de aprendizaje). Úselo para aclarar el espacio del problema. Fuente: liqiongyu/lenny_skills_plus.