LinkedIn Post Ideas for Senior Leaders

I sat on a reorg decision for three weeks longer than I should have. I knew by week one that a leader on my team needed to move out of their role. I didn't act until week four. The three weeks weren't spent deliberating the merits — I was certain of the call by day three. They were spent managing my own discomfort: rehearsing the conversation, waiting for a "better" moment, telling myself I needed one more data point I didn't actually need. What it cost, measured after the fact: two direct reports of that leader had already started quietly job-hunting by week two, sensing the dysfunction before I acted on it. One left within two months of the eventual change — someone I'd have fought to keep. A cross-functional project stalled for three weeks because decisions were routing through someone whose judgment the team had already stopped trusting, even though I hadn't officially acknowledged it yet. The trigger that finally moved me wasn't new information. It was a peer executive asking me directly, in a hallway conversation, "is this still going to be a problem next quarter?" Hearing it from outside my own head made the delay impossible to justify to myself any longer. Decision latency is the tax senior leaders pay quietly. Nobody puts it on a scorecard. It shows up two quarters later as someone else's resignation letter.

By the time information reaches me at this level, it's usually been rehearsed twice — once by the person deciding what I need to know, and once by the person deciding how to frame it so it lands well. This isn't malice. It's the natural physics of altitude. Nobody hands their boss's boss the unfiltered version of a problem; they hand up the version that reflects well on their own handling of it. Multiply that by four or five layers and what reaches me is polished enough that I can miss a real problem entirely. What I've built to counter it: a standing skip-level rotation, where I talk to someone two levels down every other week, with an explicit no-consequences framing stated out loud at the start of the conversation. I ask process questions, not "is everything okay" — specifically, "what's the thing your manager would rather I not know right now?" Sometimes that gets a real answer. Often it doesn't, on the first ask. I also watch for the tell: when a report becomes unusually smooth and confident right when I'd expect friction, that's the signal to ask a follow-up question rather than accept the framing. None of this fully solves the problem. Altitude filters information structurally, and no back-channel fixes that completely. But it's closed the gap enough times that I trust it more than the org chart's official channels alone. How do you hear the unrehearsed version?

I used to spend 40 hours preparing for a board meeting — building slides nobody would read past page ten, rehearsing answers to questions that never came up. Now it takes four hours. Here's the shift. Hour one: I write the one-page story, not the deck. Three sentences: where we are, the one decision we need from the board, and the risk if we don't get it. Everything else in the meeting exists to support this page. Hour two: pre-wiring. I call the two board members most likely to have concerns about the contentious item, individually, before the meeting. Not to lobby — to hear their actual objection while there's still time to address it, or to at least not be surprised by it live. Hour three: I anticipate the three hardest questions, and I write a two-sentence answer to each. Not because I'll read them verbatim, but because the act of writing them forces me to find the honest answer instead of a comfortable one. Hour four: rehearsal, out loud, timed. If the story takes longer than 12 minutes to tell, I cut, not add. The deck still exists — it's an appendix now, not the main event. The meeting itself runs shorter, the board's questions land closer to what I anticipated, and the contentious items rarely surprise anyone, because the surprising part happened in the pre-wire calls, in private, where it belongs. Forty hours was theater. Four hours, spent right, is actual preparation.

We ran a four-question pulse survey last quarter to measure culture against what we say we stand for. The results stung more than I expected. The four questions: Do you trust your direct manager to tell you the truth? Do you believe good work here gets recognized regardless of who's watching? Would you recommend this team to a friend looking for a job? Do you feel safe raising a concern without career risk? We score ourselves internally as a company that values transparency and psychological safety. The survey said something more specific: 71% trusted their direct manager, but only 52% felt safe raising a concern without career risk — a 19-point gap between the value we claim and the one people actually experience. The gap wasn't evenly distributed. One department scored 38% on psychological safety. That's not a communication problem. That's a leadership problem in one specific place, and the aggregate company number had been hiding it for at least two survey cycles before we broke it out this granularly. We're not fixing this with a memo about our values. We're doing skip-levels in the lowest-scoring department, and we're re-running these same four questions every quarter, publicly, so the number can't quietly disappear the way an annual engagement survey usually does. Quantifying the gap between espoused and actual is uncomfortable. It's also the only way I know of closing it instead of just restating the values again.

One of our best people resigned eight months ago. Her exit interview rearranged my priorities more than any strategy offsite that year. She wasn't leaving for money — the counteroffer conversation confirmed that immediately, she'd already turned one down elsewhere before even telling me she was looking. She was leaving because she'd raised the same structural obstacle three times over eighteen months, in three different forums, and watched nothing change each time. Not because leadership disagreed with her. Because it was never anyone's single priority to fix. The specific issue: a cross-team dependency that added roughly two weeks to every project her team shipped, that everyone acknowledged was broken and nobody owned fixing. I could have treated this as one person's decision and moved on. Instead I pulled the org chart and asked a harder question: how many other high performers have raised something three times and gotten silence? The answer, once I actually looked, was at least four issues sitting in that same unowned space. We fixed the dependency that cost us her. Not because it would bring her back — it wouldn't and didn't — but because losing someone that good is the most expensive way possible to learn what your organization has been quietly ignoring. Most executives default to "she was going to leave regardless" language. The honest version is that we made her leaving the path of least resistance, three separate times, before she took it.

Five questions I ask before approving any major initiative, regardless of who's presenting it or how good the deck looks. 1. Is this reversible? If we're wrong, what does undoing it cost us in time and money? Irreversible bets get a completely different bar than reversible ones, and conflating the two is how organizations end up over-cautious on cheap experiments and reckless on expensive ones. 2. What's the opportunity cost? Not "is this good" — what are we not doing instead, with the same people and budget? Almost nothing gets rejected on its own merits. Things get rejected against what else that team could be doing. 3. Who owns this, specifically, by name? "The team" is not an owner. If I can't name one person accountable for the outcome, the initiative isn't ready for approval yet. 4. What's the kill criteria, decided now, before we're emotionally invested? I want the number or milestone that triggers a stop conversation, agreed before launch, not negotiated after eight months of sunk cost. 5. What breaks elsewhere if this works? Successful initiatives create second-order pressure — on capacity, on adjacent teams, on systems. I want that named upfront, not discovered as a surprise six months in. An initiative that survives all five gets approved with real confidence, not hope. This list has saved me from at least two expensive mistakes that looked great in the room and fell apart under question three or four.

Every leadership meeting I'm in right now includes someone asking whether we have an AI strategy. Almost nobody in the room can answer the follow-up question I actually care about: which decision, made differently, by whom. "We need an AI strategy" is not a strategy. It's an anxiety looking for a home. The version I actually respect: "Our regional pricing decisions currently take our pricing team three days per market; with a specific tool, that becomes same-day, which changes how fast we can respond to a competitor's move." That's concrete. That names the decision, the person, and the change. I've started asking every AI proposal that reaches my desk one question before anything else: what decision does this change, and who makes it differently as a result? If nobody can answer that in one sentence, the proposal isn't ready, no matter how impressive the technology demo was. This cuts through more hype than any governance framework I've built. It also surfaces the real opportunities faster, because the teams with a genuine use case can answer instantly, and the teams chasing the trend can't answer at all. Senior leaders don't need an AI strategy document. We need a standing habit of asking this one question every time the topic comes up, until the answer is reflexive across the organization instead of aspirational.

I audited my own calendar for a month, honestly, categorized by what actually happened versus what the invite said. The gap between intention and reality was bigger than I expected. Operating work (reviewing numbers, approving decisions, running my own team): I'd have guessed 25%. Actual: 34%. People work (1:1s, skip-levels, coaching, hiring): guessed 30%, actual 19%. This was the gap that bothered me most — the category I'd say matters most to me was the one quietly losing time to everything else. External work (customers, partners, board, industry): guessed 20%, actual 27%. Higher than I realized, and not all of it was high-value; some was relationship maintenance I could delegate. Thinking work — actual uninterrupted strategic thinking, no meeting, no phone: guessed 15%, actual 6%. This was the most honest and most uncomfortable number in the whole audit. Admin and reactive work I didn't even bother categorizing separately: it absorbed the remaining 14%, mostly in fragments between other things. The fix I've made: I blocked two two-hour thinking sessions a week, treated with the same protection as a board meeting, no exceptions for a "quick" request. Six weeks in, I've kept roughly 80% of those blocks intact. If you haven't audited your own calendar against your stated priorities recently, the gap is probably bigger than you assume. Mine was.

I championed a strategy for two years after the data started telling me it was fading. Not because I was blind to the signal. Because I'd publicly backed it, twice, in front of the board, and reversing course felt like admitting I'd been wrong in a very visible way. The signal was there by year one: adoption plateaued below target, and the customer segment we'd built it for was shrinking, not growing, for reasons outside our control. I kept funding it through year two anyway, reallocating budget from other initiatives to "give it more runway," which is sunk cost logic wearing a strategy hat. What finally forced the off-ramp: a newer executive on my team, with nothing invested in the original bet, asked me directly in a leadership meeting why we kept funding something below target for six straight quarters. I didn't have an answer that wasn't ego. The off-ramp I eventually built: I framed the wind-down publicly as "the market shifted faster than our original thesis accounted for," which was true, rather than "I was wrong," which would have been more honest but harder to say and, frankly, less useful for the team moving forward. Sunk cost doesn't feel like sunk cost from the inside. It feels like conviction. The only reliable check I've found is someone with no ego invested asking the question you've stopped asking yourself.

Senior leaders — who actually tells you the truth, and how do you know it's the truth and not just confident delivery? My honest answer: two people. My chief of staff, who has an explicit standing instruction to disagree with me in private before any decision goes public, and one peer executive at a different company entirely, who has nothing to gain or lose from how I perform internally. How I know it's real, not performance: both of them have told me something in the last year that I didn't want to hear and initially pushed back on, and both turned out to be right. That track record is the only real test. Anyone can claim to be a truth-teller. Few have actually told you something uncomfortable and been proven correct. What I don't fully trust, even though I want to: direct reports, no matter how much I tell them it's safe. The power gap is real regardless of what I say about it, and I've stopped expecting unfiltered truth to travel upward through the reporting line without real effort on my part to go get it. The view from up here is quieter than people assume — not because nobody has opinions, but because fewer people than you'd think will risk delivering one you might not like. Who's on your list, and what's the actual evidence they belong there?