This post is an excerpt from Flock Not Clock: Chapter 1.
Next (in the traditional model), we need a control structure. We need processes because we need to make sure that we understand every single step of a process that has not happened yet and that will constantly be changing.
The ideal structure for this doesn’t exist, so we will repurpose our favorite structure of all time: the org chart. Simply turn it on its side and voila—the flow chart. Excellent! An org chart is really just a “tree” network. It follows a pretty typical pattern of branching where there is a trunk (inverted) at the top (CEO) that leads to the main branches (VPs, directors, etc.), which in turn branch down into the next level of hierarchy, and so on.
We love tree-like charts because we love hierarchies. They make us feel safe. They make us feel like we are in control. They get us. We can’t quit them. We love our trees so much that when it comes time to get down to action steps, we head straight for our go-to diagram—the org chart. Org charts make us feel in command of the troops and flow charts make us feel in control of processes. We like to feel in control, even if we are not. Again, we should be clear that org charts or flowcharts are not the enemy. Our concern is with mental models that are out of alignment with reality. Our experience shows that org charts and flowcharts are two of the most popular ways that we incorporate faulty mental models into our organizations. We used a flow chart last week, and not too long ago we used an org chart. The difference was that it was an appropriate use. In the case of the process, it was a very simple, linear process that followed four sequential steps. That’s a perfect place for a tree-like flow chart. For simple linear processes, a linear process diagram is a perfectly fine choice.
See the previous mental model here. See the next mental model here.