LinkedIn Post Ideas for Regional Directors

Same training program. Same POS system. Same corporate playbook, distributed identically to all 12 locations in my region. Performance spread: our best site runs 94% of target, our worst runs 54%. A 40-point gap on paper-identical inputs. For a year I assumed it was manager quality, full stop. Replace the weak manager, close the gap. I did that twice. The gap didn't close both times — once it did, once the new manager hit the same wall within two quarters. What the data actually showed once I dug in: local labor market tightness explained about half the spread. Two of our worst-performing sites are in markets where we compete with three other employers paying $2-3/hour more for the same role, so turnover was structurally higher regardless of who managed it. The playbook assumed a labor market that doesn't exist in every one of my nine markets. The other half really was leadership quality — but only visible once I controlled for the labor market difference. Now I run two separate diagnostics before I judge a site: is this a market-condition problem or a leadership problem? They require completely different fixes, and treating one as the other burns a manager's confidence or wastes a market-adjustment nobody needed. If you run multiple sites against one playbook, the variance is telling you something specific. It's rarely just "management quality" — that's the easy, and often wrong, answer.

I used to spend nearly half my travel days at my best-performing sites. They were easy visits — the manager had it handled, the team was sharp, I left feeling good about the region. I was avoiding my actual job. Six months ago I rebuilt my travel allocation with a hard rule: no site above 85% of target gets a scheduled visit unless it's been over 90 days. Everything below 70%, and every site with a manager in their first 90 days, gets priority. The uncomfortable part: my best site managers noticed the drop in visits and some read it as neglect. I had to have that conversation directly — you're not being deprioritized, you're being trusted. That landed better than I expected once I said it out loud instead of just quietly redirecting my calendar. What changed in the region: my two struggling sites got roughly triple the visit frequency they'd had the prior year. One turned around within a quarter. The other confirmed what I suspected — the manager wasn't going to close the gap, and I made that call two months faster than I would have on the old circuit. The comfortable visit circuit feels like leadership. It's actually avoidance dressed up as thoroughness. Your struggling sites and your newest managers are where your time changes outcomes. Your best sites mostly need you to leave them alone.

How I onboard a new site manager, days 1 through 45. Days 1-7: I'm on-site for at least two full days. Not training them — watching them run the floor, meeting their team, understanding what they inherited. I don't hand over full P&L visibility yet; that comes week two, once they've seen a real week. Days 8-15: weekly video check-ins move to twice weekly. I give them authority over scheduling and minor purchasing decisions, but staffing changes still route through me. This is the stage where I catch whether they ask good questions or just nod. Days 16-30: full operational autonomy on day-to-day decisions. I shift to a weekly 30-minute call, structured around three questions every time: what surprised you this week, what decision are you unsure about, what do you need from me. I'm listening for whether the surprises are shrinking. Days 31-45: first solo month-end close, with me reviewing but not co-piloting. This is the real checkpoint. If they can explain their own variances without my help, autonomy expands to include hiring and full budget ownership. The early warning I watch for the whole time: a manager who never says "I'm not sure" in the first 30 days. That's not confidence. That's someone who hasn't yet realized how much they don't know, and it shows up as a crisis around day 60 instead of a question at day 20.

Nine markets, one region, one corporate playbook. I centralize pricing bands, brand standards, and the core training curriculum without exception. I localize staffing models, promotional calendar timing, and local vendor relationships without apology. The line I refuse to cross: forced identical staffing ratios across markets with wildly different labor dynamics. Corporate pushed a standard staffing model last year — same headcount-to-revenue ratio in every market, for consistency and easier regional reporting. I fought it for one specific market: a college town where demand spikes 3x during an eight-week window and drops to near nothing during summer break. The standard model would have had us overstaffed nine months a year and critically understaffed for eight weeks that generate 35% of that site's annual revenue. I built a seasonal staffing exception, presented it with the actual revenue curve, and won a market-specific carve-out. That site hit 106% of target that year. The other eight markets, running the standard model, averaged 91%. Consistency is valuable for anything the customer experiences directly — brand, pricing, training. It's actively harmful for anything that's supposed to respond to local reality. The mistake regional leaders make is treating both as the same kind of decision. Where do you draw your own line between what corporate should standardize and what the market should dictate?

Every metric green. Floor spotless. Team smiling, on-script, word for word. My scheduled visit to one of my sites last spring was, on paper, the best 90 minutes of my month. Something felt off. Too rehearsed. The manager mentioned, almost proudly, that the team had "done some prep" for my visit. I came back unannounced three weeks later, on a Tuesday afternoon with no warning to anyone. Different picture. Two employees on their phones near the register. A backroom stacked with inventory that should have been on the floor two weeks earlier. The manager, caught mid-crisis on a staffing gap, was actually more impressive in that moment — I watched her solve a real problem live, calmly, without an audience. What the scheduled visit told me: this team can perform for an hour. What the unannounced visit told me: this team, under real pressure with no notice, was actually fine — better than fine. The real risk wasn't the team. It was that the manager had learned my visits were theater, not oversight, and had optimized for the wrong thing. Every field leader has a version of this story. The polished visit tells you what your team thinks you want to see. The unannounced one tells you what's actually happening. I still schedule visits — but I no longer trust them as the whole picture.

Six metrics that predict a location's slide about 90 days before it shows up in revenue. 1. Staff turnover upticks — even two unexpected departures in a month at a small site is a leading signal, not noise. 2. Online review velocity dropping, independent of star rating. Fewer reviews often means fewer engaged customers, before the rating itself moves. 3. Manager response lag to corporate or regional emails. A manager who used to reply within hours and now takes two days is usually underwater on something they haven't escalated. 4. Schedule churn — last-minute shift changes and call-outs climbing, which precedes a service quality drop by weeks. 5. Inventory or supply order irregularity — either over-ordering (masking shrink) or under-ordering (cash flow stress at the site level). 6. A manager's tone shifting from specific to vague in weekly reports. "Things are mostly fine" replacing the detailed updates they used to send is one of the most reliable signals I track, and the easiest one to miss if you're only reading dashboards. None of these show up in a standard weekly sales report. All six showed up, in some combination, at every site I've watched decline in the last three years, roughly a quarter before the revenue number confirmed it. What's on your early-warning list that isn't in the standard dashboard?

We rolled out a remote camera and dashboard system across the region eighteen months ago. The pitch: real-time visibility into every site without the drive time. What it actually delivered: more data, less insight. I had access to live camera feeds from nine sites and a dashboard refreshing every fifteen minutes. I found myself checking it constantly and understanding my region less than when I was just calling managers directly. The problem: cameras show you what's happening, not why. I watched a slow Tuesday afternoon on camera and assumed a staffing or motivation issue. A phone call with the manager revealed the actual cause — a competitor had opened two blocks away the prior week, something no dashboard metric was going to surface for another month. What actually improved performance wasn't more monitoring. It was fewer metrics, checked less often, paired with more real conversations. I cut my daily dashboard checks to twice weekly and added one unscheduled manager call per site per week — just a conversation, no agenda. The surveillance-flavored tools aren't worthless; they catch real operational gaps faster than a monthly report would. But they're not a substitute for a manager who trusts you enough to tell you what's actually going on, and no camera feed builds that trust. A conversation does. What's your actual ratio of tech monitoring to real conversation, and has it helped?

This week, in numbers: 1,100 miles driven, 7 sites visited, 3 fires actually put out, and roughly 14 hours behind the wheel that don't show up on anyone's calendar as "work." Monday: 220 miles to our northernmost site for a scheduled visit that turned into an unscheduled one — the manager had quit that morning, no notice. Spent four hours stabilizing coverage with the assistant manager before getting back on the road. Tuesday: 340 miles, two sites, one genuinely good visit and one where I found a compliance gap that needed same-day correction. Wednesday: office day that wasn't — spent it on the phone managing the fallout from Monday's resignation, interviewing two internal candidates for the role remotely. Thursday: 380 miles, three sites in one day, the kind of day where you eat lunch in the car and answer email at red lights. Friday: 160 miles home, plus the write-up I'm doing right now instead of actually being done for the week. The windshield time isn't the job. It's the tax you pay to do the job, which is actually the conversations and judgment calls that happen once you arrive. Nobody sees the 14 hours of driving. Everybody sees whether the region hit its number. If you lead multiple sites, what's your actual weekly mileage, and does anyone above you know the real number?

I knew by month three that a manager at one of my sites wasn't going to make it. I didn't make the call until month nine. Here's what those six extra months actually cost. Turnover beneath him: four employees left in that window, two of them strong performers I'd have fought to keep at another site. Replacing them cost roughly $9,000 in hiring and training, conservatively. Revenue: the site ran 15 points below its comparable peers for two consecutive quarters. Call it $140,000 in lost revenue against what a stable manager should have delivered. My own credibility: my regional VP asked me directly, in month seven, why I hadn't acted yet. I didn't have a good answer. I'd been telling myself I was "giving him a real chance," which was true for the first three months and an excuse for the three after that. What actually delayed me: I liked him personally, and I didn't have a clean replacement lined up, so the decision felt premature even after it stopped being premature. Both of those are real considerations. Neither justified six months. The lesson I now apply everywhere: if I can articulate the specific gap by month three, the clock on making the call should start then, not when I finally have a replacement ready. The replacement search should run in parallel with the decision, not before it. Hard calls delayed are still hard calls. They just get more expensive.

Multi-site leaders — scheduled visits or unannounced? I've done both, and I still don't think there's a clean answer, so I want yours. My current split: roughly 60% scheduled, 40% unannounced, weighted toward unannounced for any site showing early warning signs and toward scheduled for new managers who need the visit as a coaching session, not a test. The case for scheduled: it lets you actually prep, review the manager's numbers in advance, and use the time for real coaching instead of just observation. A new manager benefits far more from a structured visit than a surprise one. The case for unannounced: I've caught real problems — a staged visit at one of my sites, a compliance gap at another — that a scheduled visit would never have surfaced, because teams perform differently when they know you're coming. The camp I respect least: leaders who only do scheduled visits and call it thoroughness. That's touring the highlight reel, not managing the region. Where I land: unannounced for anything below target or for a manager you're actively evaluating, scheduled for coaching and for anyone in their first 90 days. But I'd genuinely like to hear the case for going harder in either direction. Defend your ratio. What's convinced you it's right?