This transcript was produced by robots and left as-is. Accuracy and elegance are not guaranteed.

Okay, everything in the last few episodes has been about what you do differently. This episode is about why that’s so hard to sustain, and it has nothing to do with discipline or intention. So most engineers who step into leadership are running a new job title on an old operating system. The title changed, the responsibilities changed, the identity didn’t.

The reflex to solve it. The certainty habit. The urge to step in when something’s going sideways. These aren’t character flaws. They’re residual identity. The person you built your career as is still showing up because that person worked for a long time. That person was exactly who the job needed. And why does it persist? The feedback loop never stopped.

Every time you step in and fix something, your brain files it as evidence. This is who I am. This is how I add value. The identity stays anchored to what it knows because what it knows keeps getting reinforced. It’s not a discipline problem. It’s a system behaving exactly as designed.

Engineers who work with control systems know what a slow time constant looks like. Step the input, the output moves, but it takes time to get there. The system isn’t broken, it just has a long time constant. It needs enough cycles to settle at the new value. Identity works the same way. Your title is the input, your identity is the output.

Change the input fast and the output lags behind. Not because you’re resisting, but because the time constant is long. Identity updates on feedback and feedback takes time to accumulate. The problem is that the old feedback loop is still running in parallel. Every time you step in and the situation resolves, that’s a signal. Clean, fast, and unambiguous. The new identity doesn’t generate signals like that. Its feedback is slower, noisier, and harder to read. So the time constant stays long, not because the new loop is slow, but because the old loop keeps winning on response time. That framing matters. This isn’t about who you are. It’s about where your identity is in the settling process.

So here’s a question worth sitting with. When you step in to solve something, is it because the situation genuinely requires you or because solving is still where you feel like yourself? That’s not a judgment, it’s a diagnostic. The honest answer tells you more about where your identity is anchored than any performance review ever will.

Now, back in the first episode, I mentioned that I coach youth soccer. And I said that the moment I realized I cared more about how people developed than how systems operate, that wasn’t a decision. It was a recognition. Here’s the fuller version of that story. My role coaching youth soccer is pretty simple. I want every player to be better at the end of the season than they were at the beginning, and I want them to love the game. That’s it. Winning or losing doesn’t really matter, but winning is always more fun.

Here’s the thing about coaching kids. I can’t play for them. I am no longer a kid. I am a long ways from it. When one of them is struggling to mark a player, or make a decision under pressure, there’s nothing I can do except guide, encourage, and let them work through it. The external constraint is total. I have no option to step in even if I wanted to. What I noticed is that the forced removal was useful because I could see the development happening in real time. I could see the feedback cycles doing their work. And the only thing that would have disrupted that was me inserting myself into a problem they needed to solve themselves.

Coaching taught me something that took longer to apply at work. My job is to show, not do. The constraint was obvious on the soccer pitch. In the engineering world, I had to choose it, and it took a while.

When I’m deploying engineers to site, people who are much sharper than me, than I probably ever was, nobody is stopping me from weighing in with wisdom and experience. I could jump in and I used to think I should. Part of it is just time. I’ve done enough site work. I don’t need to prove anything out there anymore. But the more honest version is this. My stepping in would have been about me, not about what the situation needed. And the time constant would have stayed long, both mine and theirs. There wasn’t a single moment where I decided to stop being the guy with the answers. It was more like I looked up one day and realized I’d stopped needing to be.

So the way your identity shifts is not through intention. It’s not through deciding to be different. It’s through accumulated evidence. You have to stay out of the problem long enough for someone else to solve it and then register what happened. And it’s not they got it done despite me stepping back. Instead it’s they got it done because I didn’t step in. That is a different data point. Collect enough of them and the identity starts to update. The time constant starts to shorten. The insight doesn’t do it. The evidence does.

So here’s something simple to try this week. Find one thing you would normally solve directly. Don’t solve it. Ask a question instead, something that puts the thinking back on the other person. Then notice what happens inside you. Not what happens to the outcome, what happens in you. That discomfort is useful information. It’s the gap between your current role and your current identity showing up in real time. It’s not a problem to fix. It’s a feedback cycle starting.

Now, identity affects decisions too. When your sense of self is tied to having the right answer, every decision carries more weight than it should. Next episode is about calibrating how much precision a decision actually requires and why getting that calibration wrong is one of the most expensive things a leader does.

That’s it for this one. If any of this landed close to home, good. That’s the gap being visible. We’ll see you next time