Build Better Products with HYPOTHESIS TRACKER KALPESH SHAH - - PowerPoint PPT Presentation

Build Better Products with HYPOTHESIS TRACKER

KALPESH SHAH

KSHAH@INTRAEDGE.COM

Kalpesh Shah

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.

Digital Product Coach, Speaker and Trainer @AgileBrightSpot in/KalpeshShahASU

If you have build a Feature? If you knew exactly how that feature will be measured? If you followed up to know that Feature was Hit or a Miss?

If it FAILED, you initiated effort to have that feature removed!

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

Conversations start with User Stories & Acceptance Criteria But Yet… … and end with Feature release

Product

HYPOTHESIS TRACKER

Release

Feature Hypothesis Behavior Target Metric By When? Actual Result Why? New Insight Decision

Before Launch After Launch

@AgileBrightSpot

BEFORE LAUNCH

FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN

BEFORE LAUNCH

FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN

This is the simplest part of the hypothesis tracker, just list the name of the feature or the experiment you are trying to create.

BEFORE LAUNCH

FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN

List the hypothesis that you are making around the problem this feature/experiment will solve. Entire team works on this together.

BEFORE LAUNCH

FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN

We Believe that <building this feature> <for these people> Will achieve <this outcome>

BEFORE LAUNCH

FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN

What is the current user behavior that you are trying to change with this feature/experiment

BEFORE LAUNCH

FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN

What is the new user behavior that you expect to see once this problem solved!

*Note: Not when feature is released but when the problem is solved.

BEFORE LAUNCH

FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN

What metric will be measured to check if the feature was successful in solving the problem. Success Metric(s) for the feature.

BEFORE LAUNCH

FEATURE HYPOTHESIS CURRENT BEHAVIOR NEW BEHAVIOR TARGET METRIC BY WHEN

This includes elements like, Usage, Click Through, Conversion etc.. You are looking for statistical significance to make conclusion and decide next actions!

WHEN WHO

Story creation, Backlog grooming, Sprint Planning Product, Tech, UX & Data

AFTER LAUNCH

ACTUAL RESULT WHY NEW INSIGHT DECISION

AFTER LAUNCH

ACTUAL RESULT WHY NEW INSIGHT DECISION

Document the actual result around how metrics and user interactions.

AFTER LAUNCH

ACTUAL RESULT WHY NEW INSIGHT DECISION

Data tells what happened but does not tell why it happened Was the change in metrics truly the result of your feature!

AFTER LAUNCH

ACTUAL RESULT WHY NEW INSIGHT DECISION

Did we get any new insights? Do we see any new changes in user behavior/usages? Do we see any new opportunities that can be explored?

AFTER LAUNCH

ACTUAL RESULT WHY NEW INSIGHT DECISION

Based on the actual results and findings decide to:

• Scale the feature
• Refine the feature
• Trash the feature

WHEN WHO

Product Retrospective, Sprint Review Product, Tech, UX & Data

Product

HYPOTHESIS TRACKER

Release

Feature Hypothesis Behavior Target Metric By When? Actual Result Why? New Insight Decision

Before Launch After Launch

@AgileBrightSpot

Kalpesh Shah kshah@IntraEdge.com

BUILD PRODUCTS PEOPLE LOVE