LinkedIn Post Ideas for General Managers

A GM role is deliberately broad — P&L, ops, sometimes product — which makes it hard to explain in a resume line but easy to demonstrate through specific decisions on LinkedIn.

Writing about a tradeoff between growth and margin, or a team restructure and why it worked, signals GM-level judgment far better than a generic "leadership" post.

What actually demonstrates GM-level judgment is a specific tradeoff and its aftermath — the margin you protected by walking away from a growth initiative, the restructure you made and what broke in the first month, the P&L call that looked wrong on paper for a quarter before it paid off.

Vague "leadership philosophy" posts don't show any of that; a real decision does.

GMs who post this kind of specific decision-making consistently tend to be recruited for roles that require exactly that judgment — board members and executive recruiters read these posts as evidence of how someone actually operates under ambiguity, which a resume of titles and revenue figures can't demonstrate on its own.

1. 1

   Owning everything, controlling little: the GM paradox in practice

   A personal essay on being accountable for a P&L while shared services, brand, and pricing sit elsewhere. Names the defining tension of the role, which earns instant recognition from peers.

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   My P&L is $34M this year. I own every number on it. Except I don't set the price list — pricing sits with a central team two floors up. I don't pick my own marketing spend — brand controls 70% of my lead flow and decides the campaign calendar. I don't hire my own recruiters — talent acquisition is shared services, and my req sits in a queue with eleven other business units. When the number misses, nobody asks how pricing performed or whether shared services filled my roles on time. They ask what I did about it. That used to frustrate me. Now I've made peace with a specific version of the job: I'm accountable for the number, but my actual leverage is in the 30% I do control — sales execution, service quality, cost discipline, and how fast my team adapts when the other 70% moves without warning. The skill nobody teaches you: influencing the functions that report to someone else. I've learned to show up to the central pricing review with my own unit economics, not complaints. I've learned to make the case for my headcount req with retention data, not urgency. I win maybe 60% of those arguments. That's still better than sitting back and letting the miss happen to me. If you run a unit P&L, you already know this tension. You're judged like an owner. You operate like a tenant. What's the one lever outside your control that moves your number the most?

2. 2

   Your best department is probably subsidizing your worst. Find out

   A contrarian push toward unit-level economics, with the cross-subsidy you discovered in your own business. Forces GMs to question blended numbers they report every month.

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   For three years I reported one blended margin number for my business unit: 18%. Last quarter I broke it apart by department. Retail ops: 26% margin. Our installation/service line: 4% margin, and some months negative once you allocate labor properly. Retail had been subsidizing service for three years. Nobody noticed because the blended number looked healthy enough that leadership never asked the follow-up question. Once I saw the split, three things became obvious: — We were pricing service calls below what they actually cost to deliver, because the original pricing model was set five years ago and never revisited. — Our best sales reps were quietly avoiding service upsells because they knew, informally, that it dragged their numbers — even though it helped the unit's blended margin look consistent. — The department getting the least investment attention (service) was the one bleeding the most. We repriced service, cut two low-margin SKUs from the install menu, and reallocated $80K of the marketing budget away from service promotion toward retail, where the real margin was. Blended margin moved from 18% to 21% in two quarters. Not from growth. From stopping the subsidy. If you manage a unit with more than one department, pull the department-level P&L this week, not the blended one. You are almost certainly funding something you'd cut if you could see it clearly.

3. 3

   How I walk the floor: what I look for in 30 minutes

   A how-to on management by walking around done deliberately: the questions, the corners you check, the signals of drift. Old-school operational craft framed for modern audiences.

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   I still walk the floor every morning. Thirty minutes, no agenda on paper, but a real checklist in my head. Minute 0-5: the entrance and the first employee I see. Are they making eye contact with customers or looking at their phone? That tells me more about morale than any engagement survey. Minute 5-15: the backroom or the ops corner nobody tours for visitors. Inventory staged neatly or piled up? Maintenance tickets open for more than a week? This is where drift shows up first — three weeks before it hits a customer-facing metric. Minute 15-20: one conversation with a frontline employee, not a supervisor. I ask one question: "what's the most annoying part of your job this week?" I've fixed six process problems in the last year from that one question alone — a broken scanner, a scheduling app nobody trained people on, a form that took nine clicks to submit. Minute 20-25: the queue or the wait time, whatever the bottleneck point is for your business. I time it myself, not from the dashboard. Minute 25-30: one thing I praise specifically, by name, before I leave. Not generic — specific to something I actually saw. The dashboard tells me what happened last week. The floor tells me what's about to happen next week. Both matter. Only one of them you can only get by showing up in person.

4. 4

   Labor cost hit 31% of revenue. The schedule rebuild that fixed it

   A data-led operations story on scheduling against demand curves instead of habit. Specific percentages and a before-and-after make it a reference post for operators.

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   Labor hit 31% of revenue in Q1. Our target is 24%. That's a $410K annualized gap on a unit this size. The old schedule was built off habit — the same shift pattern we'd run for two years, adjusted only when someone quit. Nobody had rebuilt it against actual hourly demand data in that time. We pulled 12 months of transaction timestamps and mapped labor hours against real demand curves, not assumed ones. Two things jumped out: — We were staffed at Tuesday 2-4pm levels that assumed foot traffic we hadn't seen in 18 months. — Saturday mornings, our highest-revenue four hours of the week, were staffed identically to Saturday afternoon, our lowest. We rebuilt the schedule around the actual curve: cut two shifts from the dead Tuesday window, added one to Saturday morning, and moved from fixed shift lengths to three tiers matched to demand blocks. Result after eight weeks: labor at 26.5% of revenue, service scores unchanged (actually up 3 points, because the right people were on the floor when customers actually showed up), and $290K of the $410K gap closed. The remaining gap is real — some of it is a genuine mix issue, not a scheduling one. But two-thirds of what looked like a labor cost crisis was actually a scheduling habit nobody had questioned in two years. If your labor percentage is off, pull the demand curve before you cut headcount.

5. 5

   The customer complaint that revealed a broken process, not a person

   A case anecdote tracing one angry customer back to a systems failure three steps upstream. Teaches root-cause thinking through narrative rather than methodology jargon.

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   A customer complaint landed on my desk last month naming a specific employee: rude, dismissive, wouldn't help. My first instinct was a coaching conversation. I'm glad I checked the full story first. The employee had been handling a return that our system flagged as "exception — manager approval required" — for the fourth time that shift. The approval queue routes through a manager who was in back-to-back interviews for three hours. The employee had no way to resolve the customer's issue and no way to escalate faster than "wait." Three steps upstream, the actual problem: our return policy exception threshold hadn't been recalibrated in over a year, so a growing share of ordinary returns were tripping a rule meant for rare edge cases. The employee wasn't rude. She was stuck in a process that manufactured five customer standoffs a day and gave her zero authority to fix any of them. We raised the exception threshold, gave frontline staff approval authority up to $75, and the manager-approval queue dropped from 40 requests a day to 6. The coaching conversation I almost had would have fixed nothing and cost me a good employee's trust. The root-cause question — "what had to go wrong for this to be possible?" — found the actual fix in twenty minutes. Before you coach the person, trace the three steps behind them.

6. 6

   8 numbers I check every Monday before anything else

   A listicle revealing your operating dashboard: sales, labor, inventory or utilization, NPS, safety, cash. Every GM keeps a mental version of this list and wants to compare.

   Show example post ↓

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   Eight numbers I check every Monday morning before I open email. 1. Same-store sales vs. last week and vs. last year — the first tells me momentum, the second tells me if we're actually growing or just riding seasonality. 2. Labor as % of revenue, trailing 7 days. My threshold is 25%. Above that, I'm looking at the schedule by Tuesday. 3. Inventory turns / utilization rate, depending on which unit I'm reviewing that week. 4. NPS or CSAT, trailing rolling 30 — one bad week doesn't move me, but two in a row does. 5. Safety incidents, any severity, zero tolerance for trend. This one gets checked first, not eighth, if anything's non-zero. 6. Cash position and days-on-hand, because P&L profitability and cash reality diverge more than people expect at the unit level. 7. Staff turnover, trailing 90 days, by tenure band. Losing someone at 11 months tells me something different than losing someone at 3 weeks. 8. The single largest customer complaint theme from the prior week, read verbatim, not summarized by my team. None of these are exotic. The value isn't in the metric — it's in checking the same eight, in the same order, every single Monday, so a shift in any one of them is visible against a stable baseline instead of buried in a monthly report three weeks late. What's on your Monday list that isn't on mine?

7. 7

   Corporate rolled out AI scheduling. My team had opinions

   React to head-office technology mandates from the receiving end, with what adoption actually required on the ground. The corporate-versus-field gap is rich, safe territory for honest commentary.

   Show example post ↓

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   Corporate rolled out an AI scheduling tool to every business unit last quarter. The pitch: 15% labor savings, no manager time needed to build a schedule. My team's actual experience the first month: the tool built a schedule that was mathematically optimal and operationally useless. It scheduled our most experienced closer for a Tuesday morning shift, and put two brand-new hires alone on our busiest Friday night — because the model optimized for hourly cost, not for skill mix or who'd trained whom. We didn't reject the tool. We fought for two weeks to get override rules added: skill-tagging for closers, a rule requiring at least one tenured employee per shift over $2,000 in projected hourly revenue, and a manager veto window before the schedule published, not after. Once those guardrails existed, the tool delivered. Labor cost down 9% in two months, without the chaos of month one. But that 9% only happened because five site managers pushed back hard enough that corporate actually changed the model. The lesson I keep relearning: head office builds for the average unit. The field lives in the exceptions. A mandate rolled out without a feedback loop from the floor either gets quietly worked around, or it breaks something nobody in the boardroom will see until the exit interviews start. If your team pushed back on a corporate tool recently, that pushback was probably data, not resistance.

8. 8

   What month-end close week looks like from the GM chair

   Behind-the-scenes on the scramble: accruals questions, variance explanations, the line item you investigate personally. Demystifies the rhythm of operational leadership for aspiring GMs.

   Show example post ↓

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   Month-end close week, from where I sit. Day 1: preliminary numbers land. I already know within 2% what the final will look like, because I've been tracking daily flash sales all month. The surprise, if there is one, is usually in a cost line, not revenue. Day 2: accrual review with finance. This is where I earn my keep. Last month I caught a $22K marketing accrual booked to my unit for a national campaign we didn't run locally. Nobody questions accruals unless the GM does. Day 3: variance explanations. Every line more than 5% off budget needs a written explanation before it goes to the VP. I write these myself for anything above $15K — not because I don't trust my controller, but because I need to know the story cold before someone asks me live. Day 4: the line item I always investigate personally is supplies and consumables. It's small enough that nobody else looks closely, and it's the line that quietly creeps when nobody's watching, 2% at a time, until it's suddenly 40% over budget for the year. Day 5: the close call with my VP. Fifteen minutes if the story's clean. Forty-five if it's not. None of this is glamorous. All of it is the difference between a GM who can defend their numbers cold and one who's reading them for the first time in the meeting.

9. 9

   I held a price increase too long. Volume did not save me

   A mistakes post on pricing courage: the margin erosion you tolerated and the customer math that finally moved you. Pricing hesitancy is the most common and least admitted GM error.

   Show example post ↓

   Example post

   Customize in FormatterCopy

   Personalize with your experience

   Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

   I sat on a price increase for fourteen months. Input costs had risen 9% over that stretch. I told myself we'd lose volume if we passed it through, and volume was the number I was most afraid of losing. I finally moved the price up 6% — still short of the full 9% — after a board review where the margin trend finally forced the conversation. Volume dropped 2%. Revenue and margin both rose, immediately. The math I'd been avoiding for over a year: even a meaningful volume hit is almost always cheaper than a margin that erodes silently every single month. A 2% volume loss against a 6% price gain is still a clear net win on both revenue and margin. I'd been protecting the wrong number. What actually delayed me wasn't analysis. It was fear of the conversation with my sales team, who I assumed would tell me customers would walk. Two customers out of 340 accounts pushed back hard enough to threaten leaving. One left. The other renegotiated a volume discount and stayed at a still-improved margin. Fourteen months of eroded margin, to avoid a conversation that took twenty minutes and cost us one account. Pricing hesitancy is the GM mistake I see most often and admit least. If you're sitting on a price increase right now because you're scared of the volume number, ask yourself honestly which number you're actually protecting — the business's, or your own comfort.

10. 10

    GMs: which function do you wish you had rotated through?

    A question post on career gaps, with your own blind spot named. Generalists love auditing their own development, and the answers guide younger operators in the comments.

    Show example post ↓

    Example post

    Customize in FormatterCopy

    Personalize with your experience

    Illustrative example: adapt the structure, but do not claim these names, numbers, companies, or events as your own.

    GMs — which function do you wish you'd rotated through before taking a P&L, and what's it costing you now that you didn't? Mine is finance. I came up through operations and sales, which means I can run a floor and close a deal, but I still lean on my controller for things I should intuitively understand myself — working capital dynamics, how a lease gets treated on the balance sheet, why a decision that looks great on the P&L can still hurt cash position for two quarters. It shows up in small ways. Last year I nearly approved a capital request that looked cheap on paper because I was reading it as an expense, not understanding the depreciation schedule and its multi-year cash impact. My controller caught it. I shouldn't have needed her to. I think every GM has one blind function — the one you compensate for by leaning on a peer or direct report, instead of actually understanding it yourself. It's rarely the function you came up through. It's almost always the one you skipped. If you could go back and rotate through one function before your first GM role, which one, and what's the actual gap it left? Curious whether finance is the common answer or if it splits more than I'd expect.