The Quick Win You Should Write Down and Not Act On

Every operator who's changed jobs knows the feeling of the second week. You've been there long enough to watch how the work actually moves, and some of it looks plainly wrong. A report that goes to eleven people and gets read by two. An approval step that adds four days and has never once caught anything. Two groups maintaining the same list in different systems, both convinced theirs is the real one.

You can see the fix. That's not arrogance, it's the job. Fresh eyes are one of the few genuine advantages of being new, and they have a short shelf life, because in about four months you'll have stopped noticing any of it.

So the instinct is to go fix it. And that instinct, acted on too early, is how capable people spend their first year digging out of a hole they made in month one.

What the new person actually sees

The fresh read is accurate about the artifact. The report really does go to nine people who don't read it. The approval step really is slow, and the people living with it will tell you so before you've finished asking.

What the fresh read can't see is the reason. Every piece of an operation that looks stupid from the outside is sitting on top of a history you weren't there for. Somebody built that approval step after something went badly wrong. The duplicate list exists because one system couldn't do a thing the other could, and rather than fight it for six months, two managers made a workaround that has quietly held the operation together ever since.

Sometimes the reason is dead. The thing that caused it got fixed years ago and nobody went back to remove the scar tissue. That happens constantly, and those are real wins sitting there waiting.

But you can't tell the difference between dead scar tissue and load-bearing structure by looking at it. They look identical. The only way to tell them apart is to find out why it's there, and finding that out takes weeks, because the reason usually isn't written down anywhere. It's in somebody's head, and that somebody may not report to you, may not know you yet, and may not volunteer it to a new director who's already started moving things around.

The cost of being right too early

The failure I've watched most often isn't that the new person is wrong about the problem. They're usually right about the problem. It's that they spend the only currency they have before they've learned what things cost.

You arrive with a fixed amount of credibility that you didn't earn there. It came with the title. You can spend it on changes, and every change you make that turns out to have a reason behind it takes a chunk of it, because the people who knew the reason now know you didn't ask. Some of them will be annoyed, which passes. The part that doesn't pass is what they've just learned about how you operate, which is that you move before you understand. That read is hard to reverse, and people are slow to update it once they've formed it.

There's a version of this that's worse and quieter. You change something, it breaks a thing three steps downstream, and nobody tells you it was your change that did it, because you're new and senior and they don't know yet whether that's safe. So you get the bad outcome without the feedback, which means you don't learn, which means you do it again.

Meanwhile the thing you actually needed in those first months, which is people telling you what's really going on, gets harder to come by. Nobody hands the uncomfortable truth to someone who's demonstrated they'll act on half of it immediately.

Write it down instead

The discipline that works is almost embarrassingly simple: keep a running list of everything you'd change, and don't change any of it yet.

Not a mental note. An actual document, with the date you noticed each thing, what looked wrong, and what you'd guess the fix is. Then you leave it alone and go on learning.

The list does three things at once, and only one of them is obvious.

The obvious one is that it captures the fresh-eye read before it evaporates. Four months in you'll have normalized most of it, and that list will be the only record of what the operation looked like to someone who hadn't been trained by it yet. That alone is worth the effort.

The second is that it gives the itch somewhere to go. If you're the kind of operator who came up by fixing things, and most of us are, sitting on your hands for a quarter is genuinely uncomfortable (I've never met anyone good at this who found it easy). Writing the fix down scratches enough of that to keep you from acting on it. You've done something with the observation. It's captured, it's not lost, you'll get to it.

The third one is the one that pays. As you go along and learn the whys, you get to watch your own list change. Some items you'll cross off entirely, because you found the reason and it's a good one. Some will get more specific, because you now know the actual constraint instead of the symptom. And a few will get bigger, because you'll realize the thing you spotted in week two was a surface feature of something much larger that nobody's named yet.

That third category is where a new operator earns their keep, and you can't get to it by fixing things in month one. The month-one fix would have been the surface feature, done well, and it would have made the real problem harder to see because the symptom you were using to find it is now gone.

What you're doing while you wait

Waiting isn't passive, and this is the part that gets lost when people talk about a listening tour like it's a formality before the real work starts.

You're learning why the company does what it does, which is different from learning what it does. The what is on the org chart and in the process docs. The why is in decisions made three years ago by people who may or may not still be there, and it's the thing that tells you which parts of the operation are principled and which are accidents that hardened.

You're learning the divisions and, more usefully, where they touch. Most of what goes wrong in a mid-sized company doesn't happen inside a function. It happens in the handoffs between them, and those are invisible on any chart. You find them by asking people what they're waiting on and who they have to chase.

And you're learning people, which takes the longest and matters the most. Not names and titles. Who actually knows how something works versus who's supposed to. Who's been trying to get a specific thing fixed for two years and has a whole diagnosis ready if anyone ever asks. That person is worth more to you in month three than any dashboard, and they're not going to open up to somebody who's been there ten days and is already rearranging things.

I've walked into an operation that had been through leadership turnover and needed rebuilding, and the part that mattered wasn't the plan. It was the first stretch where I mostly asked questions, because the people there had already watched somebody arrive with a plan.

When the list starts paying

There's no clean date when absorbing stops and acting starts. It's staggered, and the list tells you the order.

Some things you'll act on early because the reason turns out to be genuinely dead and the fix is small and reversible. Those are worth taking, partly because they're real improvements and partly because they show you can close something. Just make sure the reason is actually dead. That's the whole test.

The bigger items wait until you can explain the why to the person who built it, in their terms, and have them agree with your read. When you can do that, you're not a new person overriding history. You're someone who did the work and reached a conclusion the people closest to it can recognize. Those changes stick, because the people who'd have to unwind them helped you get there.

The trap on the other side is real too. Absorb forever and you're the leader who studies and never moves, which burns the same credibility, only slower and with less to show for it. A quarter of mostly listening is a reasonable ceiling for most roles. Past that we're not learning anymore, we're avoiding, and the people around us can usually tell which one it is before we can.

The pull most of us have to prove ourselves through visible action in the first month is the thing worth watching. Wanting that is normal and mostly healthy. It's just an expensive way to buy something we'd get for free by month four, when we'd be right about more of it and the fixes would actually hold.

Keep the list. Date it. Let it get smarter than you were when you started it.