The First Month Isn’t for Being Right

Three weeks into a new role, I noticed the specific shape of a feeling I hadn’t had in years: the itch to be useful in a way someone could see. Every instinct I’ve built over two decades of leading engineering teams was telling me to find the fastest lever in the building and pull it, quietly, competently, the way I’ve always proven myself. I didn’t pull it. I’ve come to think that not pulling it is the actual job right now, and that the itch itself is the thing worth examining rather than the thing worth acting on.

The itch has an obvious source. A new leader is hired into a story that already has an ending in everyone’s head before day one: this person is going to fix something, and the sooner they show it, the more the hire looks justified. That pressure is real, it comes from every direction at once, and it is almost always wrong to act on quickly, for a reason that has nothing to do with competence and everything to do with information. You cannot yet tell the difference between a genuine problem and a decision someone made for a reason that hasn’t been explained to you yet.

I’ve watched this go badly for other people, and I want to describe it plainly because it is not a story about incompetence. A capable new leader arrives, reads the surface of a system quickly and correctly, spots what looks like an obvious inefficiency, and fixes it within the first month, fast and clean, exactly the kind of visible early win everyone was hoping for. Then, months later, the fix breaks something nobody had mentioned, because the thing that looked like inefficiency was actually load-bearing, a workaround for a constraint that predates the new leader and that nobody thought to explain because nobody asked. The trust that the fast win bought evaporates in a single incident, and it evaporates faster than it was earned, because now every future decision gets re-examined through the lens of the one that went wrong.

What I’m actually spending these weeks on has no line item and would look, from the outside, like very little. I’m mapping who owns which decision in practice, which is reliably a different chart than the one in the org tool. I’m asking why the product is built the way it is, not to relitigate the answer, but because the reasons split cleanly into two categories: real constraints I need to respect, and inherited history nobody has revisited because nobody’s had the standing to ask. And I’m watching for what a team protects under pressure, because that reflex tells you more about what actually matters to them than anything on a roadmap does.

None of this is patience for its own sake, and I want to be precise about that, because patience-as-virtue is a story people tell themselves to justify drift. This is patience with a specific, expiring purpose: to spend the only currency a new leader has, which is the benefit of the doubt, on understanding instead of on a fast answer that might be wrong. That currency does not replenish. You get exactly one stretch of being new, and once it’s gone, every action you take gets judged against a track record instead of against your potential, which is a much less forgiving standard.

This is, I’ll admit, the same discipline I’ve spent years writing about, aimed for the first time at myself instead of at a team I already understood. Calm beats chaotic. Predictable beats heroic. I’ve built those into other people’s teams for two decades, and it turns out the instinct to be the hero on day one is exactly the chaos those principles were built to resist, just wearing a more flattering costume. It doesn’t feel like heroics from the inside. It feels like helpfulness. That’s what makes it dangerous.

So for now, the work is unglamorous and largely invisible, and I’ve made peace with that faster than I expected to, maybe because I’ve watched enough other people skip this stretch to know exactly what it costs later. The first month was never for being right. It’s for becoming the kind of person whose future rightness the room will actually trust, and that has to be earned before it can be spent.