I spent 13 years inside one of the most technically complex organizations in the world, and I was good at it. I understood systems. I could read a workflow, find the failure point, map the dependencies, and build a fix. That's what engineers do.

But the problems that kept me up at night weren't technical.

They were the meetings where the most important thing went unsaid. The talented engineer who stopped contributing after one too many ideas got dismissed. The team that hit every technical milestone and still felt like it was falling apart. The leader who genuinely wanted to do right by their people and had no idea where the disconnect was happening.

I started paying attention to a different set of systems — the invisible ones. The communication structures that determined whose voice carried weight. The resource gaps that forced people into workarounds instead of solutions. The workflows that were technically efficient but humanly unsustainable. The unwritten rules about what was safe to say, to whom, and when.

Those systems were just as real as anything on an engineering diagram. They had inputs and outputs, failure modes and leverage points. They just weren't being designed. They were defaulting.

That's the gap I couldn't stop seeing. And eventually, I couldn't stay in a role that wasn't letting me fix it.

I left Boeing and built a practice around what I'd spent 13 years learning: that culture is an operating system. It runs underneath everything: decision-making, collaboration, retention, innovation. And like any system, it can be diagnosed, designed, and rebuilt.

That practice became Spille:Play. The framework became Creating Culture. The clients who followed were organizations that had stopped pretending the human stuff was separate from the performance stuff — because it never was.