Latest Insights

Most founders I work with can tell you their technical debt down to the line of code. They track it, plan sprints around it, and treat it like the operational liability it is.

When I talk to leaders whose operations are running well, they mention the same thing about their calendars. The meetings look different because they're focused on strategy and decision-making rather than putting out fires. That change captures something most leaders don't realize until they experience it themselves. You're not suddenly working less, and you're just not spending all your time being the answer to every question anymore. What I notice when I'm working with teams where this is actually happening is that a few things are just there, already running in the background.

When you stop running on heroics and start running on a system, growth doesn't have to feel chaotic.

In my experience, I've seen what heroics looks like in enough companies to recognize the pattern early.

Recently, we've talked about the "human middleware" problem, which brings attention to when people become the logic layer between broken systems. Something else that gets overlooked, believe it or not, is that leadership creates this. Not intentionally, but you may have seen this before. We do it every time we celebrate someone for staying late, for answering messages at 9 PM, for being the person who "always saves the day." We say, "We couldn't do this without you." And we mean it as a compliment. But what if that's the problem?

If you've been following my posts on operational scaling, you know I've been digging into the 'human middleware' trap. Here's the other side of that story. The person who makes impossible integrations look easy is your biggest operational risk.