Product Kata
Use it when you need a repeatable, team-wide routine for uncovering real user problems before you build.
Category
Originator
Time to implement
Difficulty
Popular in
What is it?
Product Kata is a structured, repeatable routine invented by Melissa Perri to help product teams shift from guesswork to continuous problem discovery.
Inspired by martial-arts “kata” practices, it breaks down user insight and validation into short, daily or weekly loops. Each cycle guides you through setting a clear problem focus, forming hypotheses, running micro-experiments, gathering qualitative and quantitative feedback, and rapidly iterating. By embedding this pattern into your workflow, you build muscle memory for turning raw customer signals into validated user problems, and you avoid wasting time on untested features.
Product Kata solves the fundamental challenge of aligning cross-functional teams around data-driven problem solving, so you always know what to build next and why.
Why it matters?
Embedding Product Kata stops you from building features nobody uses. By making problem discovery habitual, you pinpoint high-impact opportunities, slash wasted dev hours, and deliver experiences that drive adoption, retention, and referral. Over time, that translates directly into faster growth and lower churn.
How it works
Growth co-pilot turns your toughest product questions into clear, data-backed recommendations you can act on immediately.
1
Define the Target Problem
Kick off each cycle by agreeing on a specific user pain point or research area. Frame it as a clear ‘challenge statement' so your team stays focused.
2
Formulate Hypotheses
Translate the challenge into testable assumptions about user behavior or needs. Keep hypotheses narrow and outcome-oriented to avoid vague research.
3
Plan Micro-Experiments
Design quick, low-cost experiments, interviews, prototypes, surveys, analytics dives, that directly address your hypotheses. Aim for one experiment per day or week.
4
Execute and Collect Insights
Run the experiment, capture qualitative notes and quantitative data, and log raw user quotes. Use templates or shared docs to keep feedback centralized.
5
Reflect and Iterate
Gather the team, review what you learned, and decide whether to pivot, persevere, or reframe. Update your challenge statement based on real feedback.
6
Repeat the Cycle
Schedule your next Kata session immediately. Consistency creates a habit that turns ad hoc research into a strategic advantage.
Frequently asked questions
Growth co-pilot turns your toughest product questions into clear, data-backed recommendations you can act on immediately.
You've built a relentless problem-discovery engine with Product Kata. Now fire those validated insights into the CrackGrowth diagnostic to expose hidden friction and design experiments that turbocharge your metrics.