Running Stores Isn't Running a District

The job you got promoted for and the job you got promoted into are not the same job. Almost nobody tells you that part.

---

This was a few years back. Late August — that ugly stretch where the high school kids are starting fall sports and your night crews get cut in half overnight. I was supporting a portfolio at the time, and there was a DM in that group I'll call Dani — best in her region by a long stretch. Sharp. Knew every store routine, every GM’s motivators, every 90-day rolling average in her district cold. The kind of operator every DO and VP wants two of.

It was a Tuesday. Second day of the first two-day stretch she'd taken off in four months. Around three in the afternoon, her phone buzzed on the kitchen counter. One of her GMs — order didn't post right, the truck rolls in at four, what do you want me to do.

She typed back the answer. Set the phone down.

An hour later, it went off again. Different store, different GM — assistant manager had walked out mid-shift and the closer was already an hour late calling in. She handled it.

By six she was standing in her own kitchen watching the phone on the counter like it might detonate. By the time she went to bed, she'd already canceled one of the two days she'd had scheduled for next week.

She told me about it like it was a badge of honor. She wasn't bragging — she was venting. But underneath the frustration was a quiet kind of pride. Look how much they need me. Look how much I'm carrying.

That's the trap.

The district ran because Dani ran it. When she wasn't in the rotation, it didn't operate the same way. She'd accepted that as a sign she was a strong DM. It was actually a sign that she was the job. Pull her out, the portfolio shifted. Put her back, it stabilized.

That's not good multi-unit leadership. That's load-bearing risk.

Two different jobs, same uniform

Here's what nobody told Dani — and probably nobody told you — when you got promoted.

The job you were promoted for and the job you were promoted into are different jobs. Single-unit operations and multi-unit operations share the word operations. They don't share a job description.

Running a store is doing — or at least, building a team that does. You showed up, you ran a clean building, you developed your shift leaders, you made your numbers. That's what got you the territory. You were excellent at it. They wanted more of it. So they handed you seven stores and called you a DM.

Running a district is something else entirely. It's not running each store yourself — it's developing GMs who run their stores as clean as you used to run yours. It's not solving the problem at three p.m. on Tuesday — it's making sure your GMs have the critical thinking ability to solve it themselves, week after week, without dialing you. It's not visiting every building, everyday. It's making a lasting impact in such a way the building performs the same whether you're in it or not.

Most DMs were never taught the second part. So they do what any capable person does when the instructions are missing — they improvise. They drive more miles. They take more calls. They run from store to store. They put themselves in every fire. Sitting on your couch, on a Saturday afternoon, fixing a managers broken schedule.

And it works. Until it doesn't.

Where it breaks

It breaks the first time you try to take a real PTO week and your phone won't stop. It breaks the first time you try to promote a strong GM into a multi-unit role and watch their store wobble because that one person was holding up the whole building. It breaks the first time you try to spend a week doing the actual work the role was built for — real GM 1:1s, real bench development, real period planning — and you can't, because the operational fires keep arriving and you're the one being called to put them out.

It breaks because what you've built isn't a portfolio that performs. It's a portfolio that performs when you're in the rotation. Those are two different things.

The first one travels. You can take it on PTO. You can promote out of it. The second one has a ceiling — and the ceiling is the number of hours you can be on the phone, in your truck, in the office and in a store without breaking.

You can hold a district together with your own hands for a year. Maybe two. But every hour you spend solving a GM-level problem is an hour you're not spending developing the GM who should've solved it.

The harder you work, the tighter the trap gets.

The diagnostic

So what do you actually do about it.

When you notice the gap — your GMs handle it when you're in the building, dial you the second you're not — your first instinct is going to be I need to be in stores more. Don't trust that instinct. Showing up more masks the gap. It doesn't close it. It actually deepens it, because every time you cover the gap with your own judgment, your GM learns that this kind of problem is your problem to solve, not theirs.

The right move is to ask what walks out the door with you.

Usually it's one of three things.

A resource walks out with you. Your judgment. Your authority to make a call. A piece of know-how nobody else on your team has built yet.

Fix: put that resource somewhere your GMs can reach without you in the room — a written playbook, a clear decision rule, a real delegation of authority.

A routine walks out with you. A check you run, a follow-up you do, a question you ask your GMs every time you walk a store. You've been running it in your head. When you're gone, the routine doesn't run.

Fix: write it down. Make it part of the GM's own weekly cadence. Build it so it fires whether you're there or not.

An environment shifts when you leave. The standard relaxes. The pace relaxes. The GM's posture relaxes the second your car pulls out of the lot.

Fix: stabilize what your portfolio feels like at baseline — not just what it feels like when you're walking it.

In all three, the answer moves off the GM and onto you. Not your effort — your design choices. What did you build into your GMs. What did you fail to build into them. What still lives in your head that's never been written down or installed.

The reframe

Most DMs think the goal is to be the DM whose visit makes the store run.

The real goal is to be the DM makes a real impact and whose absence from a store doesn't change how the store runs.

That sounds backwards. It feels like you're trying to make yourself unnecessary to your GMs. You're not. You're making yourself unnecessary to their daily — so you can be indispensable to their development. The DM whose absence doesn't change anything is the one who runs ten stores. Then a region. Then a division. They take real PTO. They develop GMs who get promoted into multi-unit seats instead of burning out under them.

The Hero Trap feels like a compliment, but it pays like a punishment.

Find what walks out the door with you. Build the portfolio so it doesn't.