Skip to main content

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

Popular posts from this blog

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 configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally 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-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…