Disruption in the insurance market - e.g. charity insurance products
Can we claim that we are the biggest InsurTech company in the UK?
We’re going global… talk about the US?
disorders I’ve healed in SB
teams often suffer from more than one
I have cures, but no vaccines
CLICK
This is going to be sick!
Using the maladies to identify when team/org losing its way
A language for the challenges
You’ll have to do the hard work of fixing
Self-identify problems (harder, so less likely)
There are a lot of illnesses, however, there are a lot of ways to lose your way.
Patients – one or more examples
Symptoms – what to watch out for
Diagnosis – naming the malady
Consequences – what happens when symptoms go unchecked
Root causes – the emotional angle
Coaching – questions to ask teams
Cure
Tested to see if PayPal would get click-throughs
It did
But PayPal is more expensive than current provider.
We would never switch just because people would use it
The test did not test if we got a better conversion rate, just if anyone would click on Paypal as a payment option.
Doing experiments without success criteria or a way forward
Everything must be statistically significant otherwise can’t be believed
Choosing tests based familiarity with the technique
Ask show of hands:
Have you seen this malady?
Have you cured it?
Time wasted on experiments which don’t matter
Experimenting because we should
Lack of accountability for results
While A/B tests are critical for incremental changes, they can’t be the only tool in the arsenal
Fear (of damaging something) / lack of courage
Doing “what has been asked”
No deep understanding of goals
Intolerance of failure
Q: Is this valuable?
Q: Are we moving fast enough?
Q: What does success look like? .
Understand what to learn, then design experiment. Reverse is time waste
Make teams accountable for results, not number of experiments
Conduct discovery about why customers are doing something before going straight to a treatment
Sometimes tests cost more than they could possibly be worth. Just make the change
Ask show of hands:
Have you seen this malady?
Have you cured it?
Fixed numerous small niggles in our back office for our call center team
This should prove value of investment in a product team
Substantial progress was always next quarter
In the end, the team’s performance was questioned
Continuous quick wins to prove we are worth it
Marginal metric improvements
Big change is coming (but not yet)
Low results
No vision
Fear of not proving value
Expectation of immediate results
Start with a valuable goal and don’t be distracted
We did an A/B test about an improved quote comparison page (toggling)
Then did not act on the positive results
Because people questioned: “are we sure?”
We did an A/B test about an improved quote comparison page (toggling)
Then did not act on the positive results
Because people questioned: “are we sure?”
Few ideas on how to move forward
“Nothing different will happen so don’t try”
Having to prove every step, an inch at a time. Results not accepted. Like court case against a powerful person
Major questions unresolved in spite of much activity
Business questions do not move forward, or at slow pace
Business failure
Don’t want to look bad (in one’s field of expertise)
Lack of understanding of what change is needed
Listening to others, but no point of view
External pressure
Anchored in current world, rather than desired future
What are your riskiest assumptions?
What happens if you are wrong about the way things work?
Can you make progress without resolving this dilemma?
Decide/negotiate ahead of time the burden of proof. Then meet that proof
Test the riskiest assumptions, regardless of sensitivities
Once proven, questions/learnings are not permitted to be reopened
“You can question the methodology, but you can’t question the outcome” .
We needed to reach out to insurance partners to with our proposition
We kept enhancing and enhancing our deck to make sure it was perfect
Without actually testing the pitch on any ‘customers’
In the end, when we did reach out, we didn’t even use the deck
We spent a year researching the needs of our higher value customers
Without making actual progress in choosing a segment or moving to implement what they might want.
We kept asking: is this an opportunity, rather than, how do we take advantage of the opportunity
No choices made while more tests are run
Continuously asking: “is this the best opportunity?”
Dipping toes in the water, never jumping in
Fear of mistakes
Questioning of value from senior leadership
Is what you know good enough to move forward?
How will you decide the best path? What are the criteria? How hard will it be to get the answer? .
Finding the “best” is hard/expensive. Choose good and go for it
Choosing which opportunity will likely be a heuristic or gut feel
Make the most of that good opportunity
Over time, optimise
The team executed a series of experiments
Always comfortable that the experiments would pan out and that they had a clear path forward
In the end they hadn’t solved the tricky problems
But focussed on delivery instead
No emotional highs and lows as difficult truths learned or overcome
Building something truly new is never easy. If it appears to be, something is likely wrong. Feeling of running a startup is similar to a roller coaster.
Expect that
Going to comfort is easy
Lack of time pressure (metered funding)
“Positivity” culture (bad news is punishable) .
What could mess you up?
What concrete data do you have that this will work?What would you do to get it? .
Ensure actual progress on riskiest assumptions(not excessive positivity)
Regular pivot/persevere/kill meetings
Insist on strong (and improving) evidence .
Experiments proved a gap in the market for the product we wanted to develop
But we continued to speculate if other providers had good enough products for the sector
In addition to Caged-in Syndrome, we hadn’t diligently documented our learnings.
This made it easy to continuously reopen every question
Debate is never closed
Weak documentation of learning (hard to find, if documented)
Opinions trump data
Tests run forever, or poorly designed
Lack of governance (missing: standups, experiment design, documentation standards, pivot/persevere/kill meetings, prioritisation, retrospectives, communication)
No innovation accounting metrics (or not up to date)
What little progress that is made, is quickly unravelled
Learning stuck in individuals’ heads
Learning not in priority order
People on team fear owning the result (mercenaries)
Lack of leadership
No accountability given or asked
Too many non-dedicated team members
Q: Where can I see what you’ve learned?
Q: When did you last finish an experiment?
Q: Do you have the resources to succeed? .
Bi-weekly cadence in which riskiest assumptions are reduced. Failure to make progress is pivot situation (accountability)
Track governance carefully. May be only way to know if a team is making progress (innovation accounting)
If needed, team capability must be addressed . .
We kept looking for the most valuable way we could serve our high value customers.
This led to us not choosing a way forward.
There were more and more tests to be run, none landing the killer conclusion
Lots of time passes, and you are just on the verge of moving forward, but then…
Fear of making a call
Must know everything to decide what to do
Waiting for the spreadsheet to give answer .
Q: What progress have you made in the last two weeks?
Q: If you had to, what would you build right now?
Q: What are the riskiest assumptions still to be identified?
Make small iterative steps in the right direction, rather than giant leaps
Track the reduction or change in riskiest assumptions carefully
Expect changes on the order of weeks, not months or years
.
We launched a new product for commercial landlords.
Before it had traction, we pulled the funding because we had higher short-term value opportunities.
Pulling the funding meant that the product never reached our target performance metrics
We launched a new product for commercial landlords.
Before it had traction, we pulled the funding because we had higher short-term value opportunities.
Pulling the funding meant that the product never reached our target performance metrics
Even if the experiment is a success, there are no resources to follow up the success
Funding gets pulled early
Experiments have no value since they won’t be followed up or get the support they need
Leadership never committed to project in the first place
People expect the numbers to look good right away(no innovation metrics)
Q: How important is this to the business?
Q: If the tests succeed, are the funds/people ready to move forward?
It’s all about the people/team. The more entrepreneurial, the better.
Fear of messing up is powerful; courage is needed
Culture, and culture of experimentation is crucial (you can’t fake it)
Must be ready to invest into ambiguity
Good and bad experimentation can be hard to tease apart. Maladies provide strong early signals