Discover more from Product Solving by Tyler Wince
inversion <> uoısɹǝʌuı
or, How To Envision Failure So You Can Win.
Join hundreds of other entrepreneurs, product managers, and developers in leveling up your product building skills. Subscribe now so you don’t miss out on the next post!
What would it look like if you could ensure your team was working on the right stuff at all times?
They would be able to translate between where you are now with where you are going. They would be able to make good decisions about the architecture of the product to ensure future success. They might even highlight flaws with the direction of the product and work with you on ensuring it is correct.
Unfortunately, this isn’t a reality for most of us. Between urgent requests from stakeholders, customer bugs, and an overly-optimistic roadmap, most of us are barely keeping our heads above water, let alone spend enough time with our team to ensure they are never wasting any effort.
Using inversion will help you work on the high impact features you know your customers will love and ensure your team knows where you are headed.
We should operate with certainty that we are always working on the most important things. So that begs the question, which customer requests should we work on? Which requests should we avoid? Most of us have a set of criteria to evaluate a new feature request, but it doesn’t have to be complex if we start at the end and work backward.
What is Inversion?
Starting at the end and working backward is called inversion. Inversion is a powerful mental model popularized by the vice-chairman of Berkshire Hathaway, Charlie Munger, but it has its roots in mathematics. The main principle of inversion is to turn your problem around, start at the end, and work from there. This will ensure you see your problem in a new light and end up at the destination you set out for.
By combining forward and backward thinking we can see a better picture of reality and solve problems that seemed unsolvable. Take the following problem: what is the square root of two? Today, we know the square root of two is an irrational number, but in 200BC the Greek mathematician, Hippasus, was trying to figure that out. Other mathematicians at the time were trying to solve the problem by continually dividing larger numbers into each other. Instead, Hippasus turned it around and thought about what the implications of a solution to the square root of two would be. By thinking about what has to be true about mathematics and the world if we knew the square root of two, he discovered the first irrational number.
This type of thinking, achievement thinking, forces us to think about what the world would look like if we succeed in our pursuits. But there is another side of the inversion coin that can be even more valuable, failure thinking.
Investing in the stock market is typically viewed in one direction, how do I maximize my gains? Failure thinking is going to turn that goal on its head and instead investigate how to minimize losses. This type of thinking resulted in one of the greatest ideas in investment history, index funds. Finding ways that will guarantee your failure enables you to steer clear of paths that you may otherwise be blind to.
Applying these two types of inversion, achievement and failure thinking, to building products may not always be clear… let’s dive in.
“All I want to know is where I’m going to die, so I’ll never go there.” - Charlie Munger
Find assumptions about the problem you are solving by identifying what else must be true if you succeed. By working backward and breaking down those assumptions, you can find roadblocks you may not have anticipated.
Start by defining what the best-case scenario is. It could be what a feature looks like or what the optimal outcome to a problem would be. In the new world you have created, answer two questions:
What are my users now doing?
What are my users no longer doing?
The answer to these two questions should inform how you market, build, and train users on your product.
In the B2B space, the answers to these two questions can mean less manual labor as a result of implementing your product. One of the greatest problems you will have to ensure you answer when implementing your product is “what will my current employees do if they no longer do X.” Make sure your product explains positively how your users' future world will look. Change the world around them so they can utilize your product without hesitation.
Achievement thinking will help you find new steps you might have missed or gaps that need to be addressed. While this technique is easy to implement, it enables you to cast a vision of where the team is headed, and help people think about how you are going to get there in a different way.
Even though this is the most common way to implement inversion, I would argue failure thinking is an even better way to implement inversion in your product team.
To apply inversion to your everyday work as a product person, you must be able to use it when deciding a grand vision of the product, and also when deciding on the smaller details of running a product team every day. Do this by listing everything that will make your product fail. Maybe it is adding too many features before others are finished. It could be ignoring technical debt and not building your product for scale. Sometimes it is as simple as not communicating clear expectations to your team.
Compiling a list of things that will ensure your product fails gives you a filter through which to pass every request that comes your way. It doesn’t have to be a long list, about 5-10 criteria that will guarantee failure.
Let’s think of an example:
A stakeholder comes to you asking for a new feature to be implemented immediately for a customer. You ask for some more details and compare that to your list of failure criteria. You remember that one of the items on your list is that leaving any feature halfway done will ensure your product fails. You look at your roadmap and realize you are halfway through implementing another big feature. Because executing on this feature immediately is going to leave another half-baked, you have the confidence to let them know it can’t be worked on right now.
One thing I have found to be successful in implementing this model is getting buy-in from your stakeholders. Let them know you have created a “how we fail” list and iterate until everyone agrees. Getting this buy-in enables you to direct them to that list whenever you use it to say no to a stakeholder request.
Providing your team with a “how we fail” list also gives you the confidence that your team can act autonomously without steering off in the wrong direction. Failure thinking provides guardrails to ensure your product stays on the path to success.
“It is remarkable how much long-term advantage people like us have gotten by trying to be consistently not stupid, instead of trying to be very intelligent.” - Charlie Munger
Achievement thinking provides your team with insight into what the world looks like when you have reached your destination. Calling out any assumptions explicitly to ensure you address them while you are on your way.
Failure thinking gives your team guardrails to ensure they aren’t working on the wrong things and gives you confidence they are on the straight and narrow.
Using both achievement and failure thinking together gives you a framework to think about building your product from an inverted point of view. Combining this with your forward-thinking roadmap will make you unstoppable in ensuring your product is a success.
The biggest question we are always asking ourselves as product people, “Am I working on the right things? The biggest value and highest impact things?”. If you have a set of criteria you have developed using inversion, you don’t have to worry about ensuring you are working on the right things. As long as you are not working on the wrong things, you are moving in the right direction.
If you liked this post and want to get notified of new posts, sign up below.