LinkedIn Post Ideas for Interim CEOs

First 72 hours walking into a company mid-crisis as interim CEO. Here's the actual sequence, reconstructed from notes I took at the time. Hour 1-4: cash position, first and alone. Before any conversation with the team, I needed the real number — not the board's summary of the number. Found we had 5.5 months of runway at current burn, not the 8 months the outgoing leadership had been reporting. Hour 5-18: flight-risk conversations, one-on-one, with the four people whose departure would be existential. Not reassurance — honest questions: "what would make you leave in the next 30 days," and genuinely listening to the answer instead of pitching them to stay. Hour 19-40: building the actual picture. Pulling real numbers myself rather than trusting handoff documents, because two of them turned out to be stale or optimistic in ways nobody had corrected. Hour 41-72: the all-hands. I said three things: here's what's actually true right now, including the parts that are worse than you've heard; here's what changes in the next two weeks; here's what I need from you specifically. No false confidence, no vague reassurance. That all-hands either earns you the room or loses it. Ours earned it, mostly because the runway number I gave matched what people already suspected was true, and matching suspicion with honesty builds trust faster than any polished speech.

An interim CEO auditioning for the permanent role is, in my experience, structurally compromised — even with the best of intentions. Here's the mechanism: every hard decision an interim makes gets filtered, consciously or not, through "how will this affect my case for staying." Should we cut this underperforming but politically connected team? An interim with no stake in the permanent job cuts it if the data says so. An interim angling to stay might soften it, worried about the internal enemies that decision creates for their own future tenure. I've taken four interim mandates. I've turned down the permanent role twice when boards offered it afterward, partly because I believe the incentive purity matters more than people assume, and partly because interim work has become its own specialty I'm good at and enjoy. The counterargument I hear most: "wanting the job proves you care enough to do it well." I don't buy it. Caring about the company and wanting personal tenure there are different motivations, and only one of them stays clean when a hard, unpopular decision is the right one. This will divide opinion, I know. Purists will agree entirely. Pragmatists will say I'm overthinking a hypothetical conflict. Where do you land — can an interim genuinely stay unbiased while auditioning, or is the incentive always quietly there?

Every interim mandate has a hundred things that look broken. Fixing all of them isn't the job — triaging correctly is. My filter, refined across four mandates: is this reversible or irreversible, and does fixing it now require context only I currently have? Reversible, low-context problems — a clunky expense process, a meeting cadence nobody likes — I leave alone. My successor can fix these with fresh eyes and full authority, and my fixing them now just adds unnecessary change during an already unstable period. Irreversible or context-dependent problems, I fix immediately. A key customer relationship deteriorating because nobody's addressed it in months: that's actively getting worse every week I wait, and I have context right now (why it broke, who's actually upset) that will be harder to reconstruct for whoever comes next. The hardest category: things I could fix, but shouldn't, because the fix properly belongs to whoever takes this permanently. I keep an explicit "deferred decisions" document — not a todo list, a record of things I saw, decided not to touch, and why, so my successor inherits my judgment instead of just my mess. The restraint is the actual skill. Anyone can fix things. Deciding which things aren't yours to fix is what separates a professional interim from someone playing hero for six months.

40% burn reduction in 90 days. The sequence mattered more than any individual cut. Week 1-2: protected first, cut nothing yet. I identified the three teams whose morale and output were most load-bearing for the turnaround — engineering shipping the one feature that mattered, and customer success keeping our largest accounts stable. Announcing cuts before protecting these would have triggered exactly the flight risk I couldn't afford. Week 3-4: the biggest single cut, done once, done clearly. A 15% reduction in force, communicated in one day, with real severance and real transparency about why, rather than a slow drip of smaller layoffs stretched over months. Morale mechanics matter here: one hard day beats six months of "is my job next" anxiety across the whole company. Week 5-8: vendor and tooling audit, cutting roughly $80K in monthly spend on tools and services nobody could defend using in the past 60 days. Week 9-13: renegotiated two major contracts, extracting better terms by being honest with vendors about our situation rather than pretending strength we didn't have. The lesson in the sequencing: doing the hardest, most painful cut first and clearly, instead of drawing it out, let every subsequent action feel like recovery instead of more bad news. Turnarounds fail more often from sequencing mistakes than from wrong decisions.

Week one as interim CEO, the outgoing CFO tested my authority directly, in a room, in front of three other executives. He challenged a decision I'd made about a vendor contract, not with a private conversation first, but by publicly questioning it in a leadership meeting, clearly gauging whether I'd fold or hold the line with an audience watching. I held it, calmly: explained the reasoning once, clearly, and then said, "I've made the call, let's execute and revisit if new information changes things." No escalation, no power display, just clarity and a boundary. What happened next mattered more than the meeting itself. He tested me twice more over the following two weeks, smaller stakes each time, clearly calibrating how consistent I'd be. By week four, the testing stopped entirely, and he became one of my more useful allies for the rest of the mandate, once he'd confirmed the authority was real and stable. I've since learned this is close to universal in interim situations. Someone in the org, usually a senior person who was close to the outgoing leader, will test a new interim's authority within the first two weeks, deliberately or instinctively. How you handle that single moment sets the tone for the entire engagement far more than any all-hands speech does.

Seven questions I ask every board before accepting an interim CEO mandate. Skipping any of these has cost peers of mine engagements that ended badly. 1. What's the real reason the last CEO left? Not the press release version — the actual dynamics, however uncomfortable. 2. What does success actually look like in six months, specified concretely, not "stabilize the company"? 3. What decision rights do I genuinely have versus what requires board sign-off? Get this in writing before day one. 4. Is there already a preferred permanent candidate, internal or external, that I should know about? 5. What's the real cash runway, verified independently, not just as reported to me? 6. Who on the executive team is a flight risk, and does the board already know this? 7. What's the board's appetite for hard decisions — layoffs, restructuring, difficult customer conversations — versus their stated appetite? I once took a mandate where the answer to question one, had I pushed harder, would have revealed a board conflict that made my job nearly impossible from day one. Now I push on every one of these, even when it feels like it might cost me the mandate. A board unwilling to answer honestly here is telling you something important before you've even started.

More boards are reaching for interim leadership instead of rushing a permanent search. Having sat inside several of these decisions now, the quiet reasons rarely match the public explanation. The stated reason is almost always "we need stability while we search properly." The real reasons, from what I've actually observed in board discussions: Uncertainty about the company's real direction. Several boards I've worked with genuinely didn't know if the right next move was a pivot, a sale, or steady-state growth, and hiring a permanent CEO before that question resolves risks hiring the wrong profile entirely. Deferred succession planning. More than one board admitted, once I'd earned enough trust to ask directly, that they simply hadn't done succession planning at all, and interim leadership bought time to build a process they should have started a year earlier. Genuine appetite for transformation that a search firm's typical permanent-candidate pool doesn't serve well. Turnaround specialists like interim leaders bring a skill set many permanent-CEO candidates don't have and don't want. None of these reasons are bad ones. But "we need stability while we search" and "we don't actually know what we need yet" are different situations, and boards rarely say the second one out loud, even to the interim CEO living inside the ambiguity.

Handover week, permanent CEO arriving after my six-month mandate. Here's what actually happens in those final five days. Day 1-2: the memo. Not a report — a direct, candid document covering every decision I made and why, every relationship that needs careful handling, and every problem I deliberately left unsolved for them to own with fresh authority. Day 2-3: I point out where the bodies are buried, literally naming the two employee relationships that are fragile, the customer who's one bad week from churning, and the board member who needs more hand-holding than the others. Day 4: public deference, deliberately visible. I make sure the team sees me defer to the new CEO's calls in meetings, even on topics I know well, because the org needs to see the authority transfer completely, not gradually. Day 5: I leave. Genuinely leave — no lingering advisory role unless explicitly asked for, because a former interim hovering nearby undermines a new permanent leader faster than almost anything else. Endings done well are quieter than beginnings, and they're the part of this work that actually builds my reputation for the next mandate. Boards remember whether you left cleanly as much as whether you fixed anything.

I restructured a 40-person department in eleven days, when I should have taken three weeks. The board backed me. I still think I moved too fast, and I've changed how I operate since. The pressure was real: burn was unsustainable, the board wanted decisive action, and I read that as license to skip the listening tour I'd normally do before a restructure this size. I made the calls based on org charts and financials, without enough direct conversation with the people actually doing the work. The result: the restructure was directionally right — the cuts made financial sense and the org that emerged was healthier. But I misjudged two roles specifically, cutting one that turned out to be more load-bearing than the chart suggested, and reorganizing a team in a way that ignored a dependency only the people in the room would have known to flag. The board backed the decision anyway, impressed by the speed and the willingness to act. I don't think speed was actually the right thing to be impressed by. I've since built a non-negotiable rule for myself: even under real time pressure, no restructure without at least five days of direct conversations with the people closest to the work, no exceptions. Even specialists who've done this many times overcorrect toward speed under pressure. Admitting it, I've found, builds more credibility than pretending the fast version was the smart version.

Genuine dilemma I've never fully resolved across four interim mandates: how do you ask a team for real commitment while you, personally, embody the fact that you're leaving? The honest tension: I need people to trust me enough to follow hard decisions, take risks, and stay engaged through a difficult period. All of that requires the kind of trust usually built over years with someone who's staying. I have months, and an expiration date everyone in the building knows about. What's worked, imperfectly: I've stopped pretending the temporariness doesn't matter and started naming it directly. "I won't be here to see the next chapter, so my job is to make sure whoever leads that chapter inherits a company set up to succeed, and that requires your full effort now, not despite my leaving, partly because of it." Oddly, that framing seems to land better than trying to inspire loyalty to me personally. I still don't think I've solved this cleanly. The best interims I know lean into being a trusted, temporary steward rather than trying to substitute for the kind of leader who'll actually be there long-term. Fellow interims and permanent CEOs both: how do you think about motivating people around a leadership relationship you know has a deadline?