A mental model is a representation of how something works. Depending on the context, mental models take different forms. A common analogy is that they are like tools in a toolbox.
Mental models help Product Managers to learn how systems work and to make better decisions.
A system is a set of things working together as whole. Mental models help to optimize a system by highlighting the core components and how they work together. Almost anything in the world can be described as a system.
Making good decisions without needing to know every detail is a common scenario. Mental models are frameworks for thinking. They simplify complex things by cutting through the noise.
There are a few mental models that are relevant to the key aspects of Product Management.
On this section
Eisenhower Decision Matrix (Urgent vs. Important)
This model helps to prioritize, which is key for Product Mangers to succeed. The idea is to clearly define what “urgent” and “important” mean and use the matrix to determine which quadrant a task belongs.
What is important is seldom urgent and what is urgent is seldom important - Dwight Eisenhower
The four classes, in order, are:
- Urgent and important: Tasks you should do immediately.
- Important, but not urgent: Tasks you should schedule to do later.
- Urgent, but not important: Tasks you should delegate to someone else.
- Neither urgent nor important: Tasks that you should cut.
A common mistake of new Product Managers is to get caught on urgent but unimportant tasks. Learn to delegate.
This model states that the higher the level of the system to optimize, the greater the return of investment (ROI).
Most of the time, people try to optimize a specific part of a system to increase or improve a return. But this only lead to diminishing returns over time.
Systems can be part of a larger system. When thinking about the larger system, optimization tipically lead to higher returns.
The Inversion Principle
This mental model visualizes how failure looks like to get an idea of what requires to get there. By focusing on how failure looks like, Product Managers visualize what to avoid to succeed.
The process of using the Inversion Principle is very simple:
- Define the goal: What are you trying to do?
- Invert it: What would guarantee not achieving the goal?
- Come up with solutions: How would you prevent that from happening?
When trying to achieve a goal, Product Managers should fast forward months ahead and assume a complete failure. Then work backwards and tell the story of how it happened to find the main reasons and root causes.
The ability to recognize and control our emotions is fundamental for Product Managers. The same goes for understanding and responding to other people’s emotions. These are the foundations of team work.
For leaders, the first task in management has nothing to do with leading others; step one poses the challenge of knowing and managing oneself - Daniel Goleman
As leaders without authority, Product Managers need to master the following:
- Self-awareness: To understand and take control of our moods and emotions.
- Self-management: To understand what motivates us.
- Empathy: To understand what others are going through and treating them with compassion.
- Social Skills: To understand how to interact with our team and build healthy relationships.
This model break the myths around monetized incentives to improve performance. It describes how such incentives can go awry, especially in situations where outcomes can be manipulated by people who have direct control over them.
A perverse incentive is an incentive that has an unintended and undesirable result or “cobra effect” which is contrary to the interests of the incentive makers.
This is a first draft and a just a glance of mental models for Product Managers. Take the time to learn from the resources below. We keep them up to date!
Do you have any feedback? Please, let us know here.