Build Better Products with HYPOTHESIS TRACKER KALPESH SHAH KSHAH@INTRAEDGE.COM
Kalpesh Shah Digital Product Coach, Speaker and Trainer Director of Agile/Digital Transformation at IntraEdge. Working with clients ranging from Fortune 50 companies to startups, helping them make the transition to Agile way of working, implementing Agile at Scale, employ Lean Product Development approaches and instill Lean Startup mindset. @AgileBrightSpot in/KalpeshShahASU
If you followed up to know that Feature was Hit or a Miss? If it FAILED, you initiated effort to have that feature removed! If you knew exactly how that feature will be measured? If you have build a Feature?
Customers don’t want your Feature ! They want their Problem Solved !
Finish Line Has Moved Product Delivered Sale Is Done Customer Does its Job Well
But Yet… Conversations start with User Stories & Acceptance Criteria … and end with Feature release
HYPOTHESIS TRACKER Product Release Feature Before Launch Hypothesis Behavior Target Metric By When? Actual Result After Launch Why? New Insight Decision @AgileBrightSpot
BEFORE LAUNCH FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN
BEFORE LAUNCH This is the simplest part of the FEATURE hypothesis tracker, just list the HYPOTHESIS name of the feature or the CURRENT BEHAVIOR experiment you are trying to NEW BEHAVIOR create. TARGET METRIC BY WHEN
BEFORE LAUNCH List the hypothesis that you are FEATURE making around the problem this HYPOTHESIS feature/experiment will solve. CURRENT BEHAVIOR Entire team works on this NEW BEHAVIOR together. TARGET METRIC BY WHEN
BEFORE LAUNCH We Believe that FEATURE <building this feature> HYPOTHESIS <for these people> CURRENT BEHAVIOR Will achieve <this outcome> NEW BEHAVIOR TARGET METRIC BY WHEN
BEFORE LAUNCH What is the current user behavior FEATURE that you are trying to change with HYPOTHESIS this feature/experiment CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN
BEFORE LAUNCH What is the new user behavior FEATURE that you expect to see once this HYPOTHESIS problem solved! CURRENT BEHAVIOR NEW BEHAVIOR *Note: Not when feature is released but when the problem is solved. TARGET METRIC BY WHEN
BEFORE LAUNCH What metric will be measured to FEATURE check if the feature was HYPOTHESIS successful in solving the problem. CURRENT BEHAVIOR NEW BEHAVIOR Success Metric(s) for the feature. TARGET METRIC BY WHEN
BEFORE LAUNCH This includes elements like, Usage, FEATURE Click Through, Conversion etc.. HYPOTHESIS You are looking for statistical CURRENT BEHAVIOR significance to make conclusion NEW BEHAVIOR and decide next actions! TARGET METRIC BY WHEN
Story creation, Backlog WHEN grooming, Sprint Planning WHO Product, Tech, UX & Data
AFTER LAUNCH ACTUAL RESULT WHY NEW INSIGHT DECISION
AFTER LAUNCH Document the actual result ACTUAL RESULT around how metrics and user WHY interactions. NEW INSIGHT DECISION
AFTER LAUNCH Data tells what happened but ACTUAL RESULT does not tell why it happened WHY NEW INSIGHT Was the change in metrics truly the result of your feature! DECISION
AFTER LAUNCH Did we get any new insights? ACTUAL RESULT Do we see any new changes in WHY user behavior/usages? NEW INSIGHT Do we see any new opportunities that can be explored? DECISION
AFTER LAUNCH Based on the actual results and ACTUAL RESULT findings decide to: WHY - Scale the feature NEW INSIGHT - Refine the feature - Trash the feature DECISION
Product Retrospective, Sprint WHEN Review WHO Product, Tech, UX & Data
HYPOTHESIS TRACKER Product Release Feature Before Launch Hypothesis Behavior Target Metric By When? Actual Result After Launch Why? New Insight Decision @AgileBrightSpot
BUILD PRODUCTS PEOPLE LOVE Kalpesh Shah kshah@IntraEdge.com
Recommend
More recommend
