I created a handy worksheet to help you put this tool into practice. You now have much more leverage for solving the problem. The tight deadlines are imposed by managers and teams believe it's not their place to push back.Īs you can see, by looking beyond immediate events, you are able to find a root cause of a problem.
Investigating further, you discover that teams value shipping on time over the quality of their work. Teams also typically have tight deadlines to ship a feature. Digging deeper, you find that teams don't plan for testing before releasing a feature. If you look back in time, you see that every released feature comes with several bugs. That's obviously not enough if you want to prevent it from happening in the future. Your instinct might be to react to it and start fixing them. Suppose there are a couple of bugs in the feature your product team just released. Let's look at a real-world example to better understand how the iceberg model works. Especially when it comes to the mental models which are hard to document, let alone see in plain sight.Įxample of the Iceberg model by Justin Farrugia Example It's important to note that answering these questions will likely require some research and digging. What values, beliefs or assumptions shape the system?.Where are the connections between patterns?.What has been happening over time? What are the trends?.Here are some questions to help you understand each level within a certain problem or situation. The deeper you can go in the iceberg, the more leverage you'll have. Structures and mental models tell you why it's happening. These structures are in turn based on the underlying mental models of people.Įvents and patterns show you what is happening. Structures are the relationships and feedback loops inside a system. They are the clue for understanding the system structures that are behind those patterns. Looking below individual events, you can see trends over time-patterns. Example of an iceberg model by Justin Farrugia
0 kommentar(er)
