Skip to main content

Costs of being wrong

Sometimes it's fine to make an intuition-based decision as long as the costs of being wrong are acceptable.

Imagine, or remember, as it's a widespread situation, your company decided to be data-driven. Your boss goes around throwing quotes like:
In God we trust, others must bring data.
What gets measured, gets done.
Data beats opinions.
and so on and on and on.

All those quotes are certainly correct. Having data is great. Using data in decision-making is smart. But. And this "but" is related to human nature to absolutise everything.

Once decided to be data-driven, we tend to apply that approach to every decision we're making. Even when the costs of the process are greater than the best possible impact this decision could bring.

Mind the size

In our example you're a new product owner is a company. You are responsible for a little area of a product. Your next task is to decide the positioning, colour and shape of a button on a page.
- Perfect case for an A/B test, - says your boss.
And so you start A/B test preparation. You spend 2 hours writing a hypothesis. 1 hour discussing it with engineers. 2 hours analyzing the impact on other A/B tests currently running. 6 hours collaborating with designers and UX to come up with variants. Another hour to finalise the plan with your boss. A couple of hours to QA and release the test. Finally, it's running. But. Numbers come in so slowly. Turned out your page is not that popular and the traffic is low. So you wait almost 3 weeks until you have significant results.

Results show the following picture: 100 people came to your page. 25 preferred option A, 35 - option B and 40 went for option C. Ok, so results are not conclusive. And you already spent a month doing that test.

Instead of continuing the test, you look at the bigger picture. Turns out the page you tried to optimise is among the least visited. It is insignificant in the context of the whole product. You can substitute this page with a picture of your dog, and it wouldn't affect the rest of the product. And if it would be a picture of your cat - you could even increase your traffic. You realise that you spent a month worth of work to make a worthless decision.

Instead, if you'd know the costs of being wrong with this decision - you'd not waste so much time.

Costs of being wrong

Next time faced with a product decision, try the following exercise.
Ask yourself:
  • What is the worst that could happen if I do this wrong? (negative impact)
  • What is the best outcome if I do this right? (positive impact)
  • What are the costs of actions to increase my confidence? (time, work and resources of all people involved)
Having answers to those questions - think whether the costs of actions justify the impact.
Say a base value of a thing you work on is a virtual 100.
A best positive impact is 20 and costs of actions (to increase your confidence) = 100 - you may want to go for it. But.
If a worst negative impact is 20 and costs of actions (going with your intuition) = 10 - this might be the better option. Keeping in mind, it could mean positive impact as well.
The trick is that both negative and positive impacts are potential. While costs of actions are real. We never could be fully confident about the potential impact. But very often the costs of being wrong are much smaller than the costs of actions to increase our confidence.

Knowing your costs is key

You must know your operational costs.
You should have an idea about an impact (both positive and negative) your actions might cause.
Knowing the costs of being wrong could speed up your decision-making, freeing up resources for really important choices.

One of my favourite subject-related quotes is:
If we have data - let's go with it. If we only have opinions - let's go with mine.
Knowing the costs of being wrong, this quote no longer just sounds cocky but could be a better way of making certain product decisions.

Popular posts from this blog

Product management and operations tools - Jira Product Discovery review

  JPD is a new player in the market of product management software. Jira (and the whole Atlassian suite) has been one of the most popular tool stacks for teams to deliver software products. Now they're adding a missing piece - product discovery.

Product Vision: an elevator pitch for your product

On this blog, I write a lot about making data-driven decisions . But what if you just starting to think about your product? You have a vague idea and nothing more. No point to go for prototyping or even talking to customers as you don't know yet who to talk to and what to talk about. In such situation - start from creating a product vision.

2 simple but powerful filters for your problem and product ideas

Nowadays lots of people and companies want to innovate. They want to generate new ideas and turn them into profitable products. But how would you separate good ideas from not so good ones? How would you make sure you invest only in good ideas?