Productivity
discovery.problem_framing avatar

discovery.problem_framing

Frame core customer problems, supporting evidence, and success hypotheses to ensure discovery work is grounded in data before solutioning begins.

Introduction

This skill acts as a structured framework for product managers to articulate a clear problem statement, validate it with empirical evidence, and define measurable success criteria prior to committing engineering or design resources. It is designed to bridge the gap between initial research insights and actionable product development, helping teams avoid 'solutioning' too early. By requiring specific inputs like interview transcripts, market data, and usage metrics, it enforces a disciplined approach to the discovery phase, ensuring that every initiative is tied to a genuine customer pain point and supported by verifiable signals.

  • Facilitates the creation of a concise 2-3 sentence problem statement backed by research.

  • Maps qualitative insights and quantitative signals into a structured evidence table, assigning confidence and relevance scores to each source.

  • Defines a robust success hypothesis that includes leading metrics, anti-goals, and explicit scope boundaries.

  • Generates alignment questions to facilitate triad discussions between product, design, and engineering partners.

  • Promotes a culture of evidence-based decision-making by forcing teams to explicitly state key assumptions.

  • Users should provide recent research inputs such as interview transcripts in markdown format and relevant analytics dashboards.

  • The workflow is optimized for product teams using the codex CLI or similar agent orchestration platforms.

  • Pre-run preparation is essential; users must confirm they have synthesized research findings and aligned with design/analytics leads on persona focus.

  • The output includes a formal problem statement, an evidence summary table, a detailed success hypothesis, and a list of next-step alignment questions.

  • Constraints include a strong reliance on existing documentation and data; the quality of the output is directly proportional to the depth of the provided research files.

  • Users are encouraged to link the output to their product backlog or discovery tracker for long-term accountability.

Repository Stats

Stars
0
Forks
0
Open Issues
6
Language
Python
Default Branch
main
Sync Status
Idle
Last Synced
May 3, 2026, 07:46 PM
View on GitHub