Strategyzer webinar learnings: Designing experiments that matter

Strategyzer put on a free webinar to discuss how to design business experiments that matter, with David Bland & Alex Osterwalder providing the discussion.  I stumbled on these guys after being recommended the book 'Business Model Generation' (http://cuddletech.com/?p=910), and subsequently reading the follow-up book 'Value Proposition Design' (my present CTO is encouraging VPD practices) - plus using many of their resources.

(Will add a link to the recording here when it arrives...)

Big lessons


  1. When companies start seeing failure as success, culture is moving.
    • e.g. I am so glad we learned there was nothing in this idea; we saved millions of investment dollars
  2. The ramifications of incentivizing output instead of outcome
    • Current software development methods reward output (deliver by a certain date, deliver a feature or product) instead of rewarding the outcome
    • This leads to focusing on building instead of learning
  3. Learn / Build / Measure loop
    • Start with learn!  Almost everyone starts w. build
    • Tightly couple learning with building

Thoughts

  • Output vs. outcome:  How does this fit into or change the Agile w. DevOps view?
    • How do you balance getting things done with experimentation?
      • Is 'getting things done' a preconceived notion that traps us?
  • What needs to change to allow (enforce?) 'experiments with evidence'?
  • Fear of failure is an easy theme here - how, practically, can this be addressed and mitigated?

Other notes



  • Are you focusing on building? or learning?
  • Are you throwing away things you've built?
    • If not, the things you are building are too expensive!
  • Lean is about deferring commitment
    • Be crafty/scrappy/creative in your experiments
    • Gets very hard to throw away things that have a big investment in infra/code
  • In environments where regulatory or legal barriers are present - don't assume commissions/legal depts automatically want to shut you down
    • Talk to them!
    • Find out what you can and can't do


Design thinking notes

  • Three parts that must not be separated - they inform each other:
    • Desirable - do they?
    • Viable - should we?
    • Feasible - can we?
  • Multi-disciplinary teams help keep them together
    • e.g. Engineering, sales, business, etc
  • Desirability
    • Start with customer interviews in teams of two
    • Landing page test
      • Use the words of the customers
  • Pricing tests also should not be ignored - treat the same way

Further reading


  • Express Executive Education - http://cuddletech.com/?p=910
    • Despite the name, a lot of valuable lessons for anyone trying to make things better
  • (added to my future book list...) https://www.amazon.ca/Monetizing-Innovation-Companies-Design-Product/dp/1119240867/ref=sr_1_1?ie=UTF8&qid=1493142562&sr=8-1&keywords=monetizing+innovation
  • https://www.amazon.ca/Business-Model-Generation-Visionaries-Challengers/dp/0470876417/ref=sr_1_1?ie=UTF8&qid=1493142532&sr=8-1&keywords=business+model+generation
  • https://www.amazon.ca/Value-Proposition-Design-Products-Customers/dp/1118968050/ref=sr_1_1?ie=UTF8&qid=1493142537&sr=8-1&keywords=value+proposition+design

Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many of us work in seem to apply this as law - an
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible on
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99A
Read more