Mental Models a Senior Engineering Leader Uses and How to Know When You’re Using the Wrong One

I’ve read a lot of mental model articles over the years. Most of them fall into the same trap. They treat mental models like Pokémon. Gotta know them all. I’ve made that mistake myself. At senior levels, that’s not the problem. The problem is misapplication. Using a clean, elegant model in a messy situation. Reaching for structure when you need exploration. Applying control when what you actually need is clarity. What follows isn’t a greatest hits list. It’s a working set. These are the models I actively reach for,  why  I reach for them, and the moments when I’ve learned to put them away. Sense making models When I reach for them When everyone sounds confident but no one agrees. When requirements keep changing names. When the room is full of solutions and empty of shared understanding. This usually shows up early in initiatives, during incidents with unclear blast radius, or any time we’re operating in a domain we don’t actually understand yet. Why they matter When cause and effect ar