From Digging Up Cities to Digging into Systems

The capstone: why the gap between the blueprint and the behavior is the most human problem there is.

When I was little, I wanted to be an archaeologist. Not for the artifacts; for the enigma. How did a society actually work? What made people build what they built, trust who they trusted, abandon what they abandoned? I wanted to understand the invisible operating system underneath the visible ruins. I never did pick up a trowel. But I've come to realize I've been doing a version of that work my whole career.

I studied sociology because I was drawn to the same question in living form: how people behave in groups, what motivates them, what shapes the decisions they make without ever noticing they're making them. Alongside my major, two subjects pulled at me; statistics and linguistics. One taught me to think in probabilities, to see the pattern under the noise. The other taught me that language isn't just how we communicate; it's how culture actually gets transmitted, reinforced, and occasionally rewritten. For a long time, those felt like separate fascinations. They aren't.

Two operating systems

What I do now at SimplexityPM is, at its core, the same investigation. Every organization has two operating systems: the one written down ; the ISO manual, the SAFe framework, the compliance program, the EOS traccard and the one people actually run on every day. The gap between those two is where transformations quietly die. Companies don't struggle because they bought the wrong system. They struggle because the behavior never caught up to the blueprint.

The archaeologist in me looks for that gap; the difference between the monument and the daily habit. The sociologist reads the group dynamics that hold the old behavior in place. The statistician asks whether the pattern I'm seeing is real or just a story I want to be true. And the linguist listens to the words a team uses; because the language of a workplace is its culture. Change the words people use in a standup, and you've started to change what they believe is possible.

The archaeologist looks for the gap between the monument and the daily habit.

Everything in this series lives in that gap

This whole series has really been an excavation of that one gap, from different angles. The respect that keeps a business close to the human it was built to serve. The integrity it takes to name what's wrong when the room would rather not hear it. The trust that lets you strip away the complexity fear built. The humility to log the slow mile and make the messy middle visible. None of those are documentation problems. Every one of them is human.

That's the whole idea behind the adoption layer we build; making the operating system a client already owns actually run in daily behavior, not just live in a binder. You can't buy your way across that gap. No framework installs itself. What carries a change across is a culture where the truth travels freely, up and down and sideways, because people are respected enough to tell it and leaders are humble enough to hear it. Same enigma that thrilled me as a kid. Different dig site.

So here's the question worth sitting with. Think about the system your team was so excited about the day you rolled it out; the framework that was going to fix the bottleneck, tighten the handoffs, make the chaos make sense. Where is it now: running in how people actually work, or quietly living in a binder while everyone reverts to the old habits? If you already know the answer, you already know where the real work is.

That gap between the blueprint and the behavior is exactly the thing I help teams close; without ripping out what you've already built. The SIMPL™ Diagnostic is where the dig begins: a clear-eyed map of where your written system and your real one have drifted apart, and the specific behaviors that will close the distance. If that's the puzzle you're sitting with, it's worth a conversation.