Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Hypothesis driven development

372 views

Published on

I created this deck some time ago for a client project. It was a quick introduction for the client on our approach to design, develop, and test their new product.

The hypothesis driven development approach is pretty well known now although I don't see it employed very often, possibly because of the cultural and logistical implications.

Published in: Internet
  • Be the first to comment

  • Be the first to like this

Hypothesis driven development

  1. 1. Hypothesis Driven Development Small Experiments to Validate the New Strategy, Demonstrate Concrete Action Items, Forecast ROI
  2. 2. Define the Hypothesis Step 1 of 6 (for each experiment) We believe <this capability> Will result in <this outcome> We will have confidence to proceed when <we see this measurable signal> Seamless Teamwork Customer Centered Experiment
  3. 3. Design the Solution Step 2 of 6 Lightweight Docs Lightweight Design
  4. 4. Build Step 3 of 6 Together...
  5. 5. Test Step 4 of 6 Test with Real Users
  6. 6. Controlled Release Step 5 of 6 Gather Facts
  7. 7. Analytics & Feedback Step 6 of 6 Fact Based Decision
  8. 8. What do we need for testing?
  9. 9. Feature Flags Option 1: Mechanism for gathering feedback What it is A technique to turn some functionality of your application off, via configuration, without deploying new code Why use it Efficiently and seamlessly manage the [Dev]-[Test]-[ControlledRelease] lifecycle We are engaging in actual development so we can address all three outcomes at once (engagement, flexibility, cost) Real Users Requirements ● Access to Codebase ● Codebase must be capable of supporting it (needs analysis) ● Able to create a staging environment
  10. 10. JS Experimentation Platform Option 2: Mechanism for gathering feedback What it is A tool which adjusts design via JavaScript, post-render of the page Why use it ● Lightweight ● Real Users Limitations ● Does not modify actual site code ● Primarily for content and visual changes (functionality changes are limited) Requirements ● 1 Line of Code in website ● Optimizely Account (Paid or Trial)
  11. 11. Internal Guided & Unguided User Testing Option 3: Mechanism for gathering Feedback What it is A tool which adjusts design via JavaScript, post-render of the page Why use it ● Able to gather anecdotal, qualitative feedback ● Able to gather emotional feedback Limitations ● Feedback can be biased ● Can be time consuming Requirements ● Access to Codebase ● Able to create a staging environment
  12. 12. External Unguided User Testing Option 4: Mechanism for gathering Feedback What it is A tool which adjusts design via JavaScript, post-render of the page Why use it ● Able to gather anecdotal, qualitative feedback ● Able to gather emotional feedback Limitations ● Feedback can be biased ● Can be time consuming Requirements ● Access to Codebase ● Able to create a staging environment ● Starting at $99 / Test

×