Get Grounded First

Every instinct screams fix it now. But the first job isn't to fix — it's to get grounded, fast, on a machine you don't yet understand.

Here's the friction, named before I waste your time: when you take over something broken, every instinct screams fix it now — and acting before you understand the terrain is how smart people make a mess worse. The first job isn't to fix. It's to get grounded, fast, on a machine you don't yet understand.

Let me put myself in the chair first. I've walked into operations with a head full of solutions before I'd learned a single real thing about how the place actually ran, and I've paid for it every time. You come in wanting to prove you were worth hiring, so you start changing things in week one — and you change the wrong things, because you were solving the problem you imagined instead of the one that was actually there. Confidence without grounding isn't leadership. It's just a faster way to break something.

Why grounding is the whole first month

In aviation, before you fly into unfamiliar airspace, you get the picture first — the terrain, the weather, the traffic, the field. You don't take off and figure it out on the way. Business is no different, and it's the step everyone skips because it doesn't feel like progress.

Getting grounded means going to the people, because in most companies the truth of how things work isn't written down anywhere. It lives in heads. So you interview. You transcribe the conversations so you can actually study them instead of half-remembering them. You set the communication standards and the operational standards that never existed. And slowly you build the one thing the business has never had: an honest map of how it really runs — not the org chart's fantasy, the real thing, with all its undocumented workarounds and silent dependencies.

It's slow, and it looks like nothing. Nobody claps for a week of interviews. But you cannot fix a process you haven't seen, and you cannot see a process that only exists as muscle memory in three people's heads until you've done the unglamorous work of pulling it into the light.

The mistake grounding prevents

Here's what happens when you skip it. You arrive, you feel the chaos, and you reach for the big visible move — usually technology, usually "let's put a system on this." I've written about why that's the wrong first step, and grounding is the reason it's wrong: you can't automate or redesign a process you've never actually mapped. Skip the grounding and you're not solving the business's problem. You're installing your assumption about the business's problem, at full speed, with real money — and assumptions made on day three are almost always wrong, because the real problem is usually one layer beneath the one that's visible from the door.

Most companies, even the struggling ones, are more coherent than they look once you get grounded — the mess is rarely as complicated as the panic suggests. It's just invisible, because nobody wrote it down and everybody's too busy running to explain it. The grounding is what turns "this place is chaos" into "these four processes are broken and here's the order to fix them." You can't get to that sentence by guessing. You get to it by listening first.

You cannot fix what you have not yet honestly seen — and seeing it is the work, not the warm-up.

Grounding is not paralysis

Let me be clear about what I'm not saying, because "get grounded first" can be misused as an excuse to never act. Grounding is not endless study. It's not committees and analysis while the building burns. It has a clock: you get grounded fast, because the business doesn't stop bleeding while you learn. The discipline is to spend your first stretch deliberately listening and mapping instead of reflexively fixing — not forever, just long enough to be solving the real thing.

And grounding usually surfaces the low-hanging fruit on its own. As you map, you'll spot the obvious wins — the invoice that never goes out right, the receivable nobody chases, the five-step process that's secretly ten. Those become your early, visible wins. So grounding isn't the opposite of action. It's what makes your first actions land on the real target instead of the imagined one.

The two operators

Let me make it concrete. Two people take over the same struggling department. Both are smart. Both want to prove themselves.

The first one arrives certain. Within a week they've announced changes — a new tool, a reorganized workflow, a couple of policies. It feels decisive, and for about a month it looks like leadership. Then it starts to unravel, because the new tool broke a handoff nobody had told them about, the reorganized workflow cut a step that was quietly load-bearing, and the policies solved a problem that wasn't the real one. Now they're firefighting messes they made, on top of the messes they inherited, and the team has quietly decided the new person doesn't understand the work.

The second one arrives curious. The first weeks look like almost nothing — conversations, notes, questions, a lot of listening. No announcements. And then, once they can actually see the terrain, they make three changes instead of thirty, and every one lands, because every one is aimed at a real problem they watched with their own eyes. By the time the first operator is cleaning up self-inflicted wounds, the second is compounding small, correct wins — and the team has decided this one gets it.

Same intelligence. Same intentions. The only difference is that one of them mistook motion for progress and the other spent a quiet few weeks earning the right to be right. Grounding didn't slow the second operator down. It's the only reason their speed later actually went somewhere.

The move for Monday

If you're stepping into anything unfamiliar — a new role, a new company, a broken process someone handed you — resist the urge to fix in the first week, and here's the move that replaces it: spend your first real stretch on interviews, not initiatives. Sit with the people who actually do the work, ask them to walk you through it step by step, and write it down — because nobody else has. Set one standard: that from now on, this is where the real process lives, in the light, not in someone's head. You'll be tempted to skip straight to fixing, because fixing feels like value and listening feels like delay. It's the opposite. The listening is the value. The fixing is just what becomes possible once you can finally see.

I'm not the expert here. I'm the guy who charged in with answers before he had questions, more than once, and learned the expensive way that the fastest path through a broken business is the slow, quiet week of actually learning it first. Take what fits. Leave the rest.