LinkedIn Post Ideas for Managing Directors

I took over a $42M P&L in April, mid-fiscal-year, from a predecessor who'd left abruptly. Here's the honest version of the first 100 days, skeletons included. Week one: I inherited a forecast that assumed 14% growth. Within two weeks of real pipeline review, I knew it was closer to 6%. Nobody had corrected it because nobody wanted to be the one delivering the downgrade three months into the fiscal year. Weeks two through four: I found $1.2M in committed client discounts that weren't reflected in the margin model — verbal commitments made to retain two accounts, never formally logged. I had to disclose this upward before I'd even finished meeting my own team. Month two: I reset the forecast with the parent company, took the credibility hit early and deliberately, rather than letting it surface as a surprise miss in Q3. It was an uncomfortable conversation. It was a much better one than the alternative. Month three: first real wins — renegotiated one vendor contract that recovered $180K in annual margin, and restructured one underperforming account team that had been carrying two people misaligned to the work. By day 100: forecast credibility rebuilt, one client relationship stabilized, one still fragile. Transition stories from this seat are rare because admitting you inherited a mess feels like admitting weakness. It isn't. Correcting a bad forecast in month one is the most senior thing you can do in the first 100 days.

Our annual planning cycle used to take six weeks and produce a number that was wrong by month four. I stopped treating it as gospel and moved to a rolling quarterly reforecast instead. The old way: one detailed annual plan, built each October, defended in every subsequent meeting even after market reality diverged from it in January. We spent more energy explaining variance to a stale number than adjusting to reality. What changed: every quarter, we reforecast the next four quarters based on actual pipeline, actual churn, actual market signal — not a fresh six-week planning exercise, just a disciplined two-week reforecast using a template we refined over three cycles. The result, measured over five quarters: our forecast accuracy at the 90-day horizon improved from an average variance of 22% to 9%. More importantly, decisions about hiring and investment now happen on quarterly information instead of information that's up to nine months stale by the time a decision gets made. The resistance came mostly from finance at the parent-company level, who wanted one number to hold the whole organization to for planning simplicity. We compromised: the annual number still exists as a directional target for parent-company reporting, but my unit's actual operating decisions run off the rolling forecast. Planning-cycle fatigue is universal at this level. Most of us are quietly reforecasting anyway in a side spreadsheet. Just make it the official process instead of the shadow one.

I've been asked to review business units outside my direct expertise four times in the last two years — different product, different market, sometimes a different country. Here are the five questions that expose health in any P&L, regardless of the domain. 1. What's the margin trend over eight quarters, not two? A single bad quarter tells you nothing. A steady eight-quarter decline, even a small one, tells you something structural is happening underneath. 2. What does the pipeline look like by stage, and has the stage-to-stage conversion rate moved? A healthy top-of-funnel number hides a broken business if conversion from proposal to close has quietly dropped. 3. What's the churn rate among your top 10 accounts specifically, not the blended average? Concentration risk hides inside averages. 4. Who are the two or three people this unit cannot lose, and what's their flight risk? Every unit has irreplaceable talent risk it doesn't discuss openly. 5. What decision is this team making that depends entirely on a person or system outside their control? This surfaces dependency risk nobody flags until it breaks. I don't need domain expertise to ask these five questions well. I need the discipline to ask them in every review, in the same order, and to actually sit with an uncomfortable answer instead of moving past it. Generalist judgment isn't knowing more than the specialists in the room. It's asking the questions specialists are sometimes too close to ask themselves.

We grew revenue 18% last year. In the leadership review, I called it a bad year. A few people in the room disagreed with me, out loud, and I understand why — but the number was hiding real decay. Here's the separation between growth quality and growth quantity that changed the read. Margin mix: the 18% growth came disproportionately from our lowest-margin service line, which grew 34% while our highest-margin line grew only 4%. Blended margin actually compressed by 2.1 points even as top-line revenue rose. Client concentration: our top three clients moved from 31% of revenue to 44% over the year. Growth that concentrates risk isn't the same quality as growth that diversifies it, even at the same headline percentage. The contract that masked decay: one renewed multi-year contract, signed at a discount to retain the client, accounted for nearly a third of the entire year's growth number. Strip it out, and organic growth in our core business was closer to 4%, not 18%. None of this means the year was a failure. It means the headline number was telling a story the underlying numbers didn't support, and I'd rather correct that story in a leadership review than let the parent company celebrate a number that doesn't reflect the unit's actual trajectory. Sophisticated financial storytelling isn't pessimism. It's refusing to let a good headline hide a problem you'll be explaining next year instead.

An email hit my inbox at 11pm from our largest client's CEO, cc'ing three people on their side, expressing frustration serious enough that renewal was implicitly on the table. My delivery team had been managing the underlying issue for two weeks without escalating it to me. What my team needed from me: not a rescue. They needed me to show up in the room the next morning as a peer to their CEO, not as a problem-solver swooping in over their heads. I made sure the account lead was still visibly in charge of the relationship in that meeting — I opened, then handed the room back to her. What I almost did, and I'm glad I didn't: draft a response at 11pm, angry at my own team for not escalating sooner, and send something reactive before I had the full picture. I slept on it. By morning, I understood the miscommunication was mutual — their team had also changed a requirement without formally notifying us. What actually resolved it: a joint session the next day where both sides laid out the timeline without blame, and a revised SLA with weekly, not monthly, check-ins for the next quarter. The client renewed, at the same terms, six months later. Escalation craft at this level isn't about solving the technical problem personally. It's protecting your team's authority in the room while making sure the client feels the seriousness matched their concern.

Six signs your leadership team is quietly filtering what reaches you, learned the hard way after being surprised by a problem that had been visible to everyone below me for months. 1. Every unit reports green in the same review, quarter after quarter. Real businesses have uneven performance. Suspicious unanimity is a red flag, not good news. 2. Bad news arrives with a solution already attached, every time. Occasionally a problem should reach you before anyone's solved it — if that never happens, problems are being resolved quietly below you until they can't be. 3. Updates get shorter over time, not longer, as a business unit matures. Maturity usually adds nuance to reporting. Shrinking updates often mean people have learned what gets questioned and are avoiding it. 4. Nobody in the room disagrees with the most senior voice present. Healthy teams have visible tension. Total agreement usually means dissent has moved to side conversations you're not in. 5. The same three risks appear on every risk register, unchanged, for a year. Either the risks are genuinely static, which is rare, or nobody's being honest about new ones emerging. 6. You learn about a problem from a client or the parent company before you learn about it internally. This is the clearest sign of all, and by the time it happens, the filtering has already cost you real time. Information asymmetry is the silent killer of decision-making at this level. Watch for the pattern, not the individual report.

Headcount freezes are back across our portfolio, and I've been through enough of these cycles now to have a clear triage order. Here's what I protect first, in priority, and why. First: revenue-generating and revenue-protecting roles. Account managers on our top 10 clients don't get touched, full stop, even under real pressure — the cost of losing a relationship dwarfs the cost of one salary. Second: single points of failure. Any role where exactly one person holds critical operational or technical knowledge gets protected next, because the cost of losing them isn't the salary, it's the multi-month recovery if they leave under freeze-induced uncertainty and take undocumented knowledge with them. Third: pipeline builders — business development and early-stage client success roles. These feel cuttable in a freeze because their impact lags by two or three quarters, which is exactly why cutting them is a mistake that shows up right when you need the pipeline most. What I do cut first, without much hesitation: newly approved but unfilled roles that were expansion bets, not maintenance needs, and any role that was justified primarily by growth assumptions that are no longer holding. What surprised me most this cycle: the pressure to freeze evenly across every team, for optics, rather than triaging by actual risk. Even freezes, applied without judgment, protect the wrong things and gut the ones that matter most quietly. Concrete prioritization under constraint is the actual leadership test here, not the freeze decision itself.

My monthly business review has one deliberately awkward segment, and it's the part that makes the rest of the meeting worth running. The standard agenda: 10 minutes on the scorecard, no discussion unless something's off-target. 15 minutes on pipeline and forecast movement since last month. 10 minutes on client health, specifically our top accounts by revenue, not a general summary. The awkward part, 15 minutes: misses get discussed by the function that owned them, without anyone else in the room assigning blame or piling on. I set this rule explicitly at the start of every session — the person presenting a miss gets to finish their explanation of what happened and what they're doing about it before anyone else speaks, including me. It took real discipline to build this norm. Early sessions, other leaders would jump in defensively or critically before the presenter finished, and misses started getting hidden or softened in advance to avoid the pile-on. Once the norm held for a few cycles, people started bringing real misses earlier and more completely, because they trusted the room wouldn't turn on them for it. Last 10 minutes: decisions and owners, logged live, visible before anyone leaves. Meeting architecture gets copied fast in this world, and I think the awkward segment is the one part worth copying most deliberately — the discipline to let a miss be explained fully before it gets judged.

I centralized our regional account support function into one shared team to cut cost. It looked right on paper — an estimated $310K in annual savings from de-duplicating roles across three regions. Within five months, we'd lost two clients, worth a combined $1.1M in annual revenue, both citing a decline in responsiveness and a loss of the dedicated relationship they'd had with a named account manager who now covered work across regions instead of a focused book. What I missed: the savings math counted headcount efficiency. It didn't count relationship equity — the years a specific account manager had spent learning a specific client's internal politics, preferences, and history, which evaporated the moment coverage became generalized and shared. What we settled on: a hybrid model. Centralized the genuinely commoditized support work — routine reporting, standard renewals — where relationship depth doesn't matter much. Kept dedicated, named account ownership for our top 15 clients by revenue, non-negotiable, regardless of the efficiency math. The corrected model still saved roughly $190K annually, less than the original plan, but without the client damage. I'd rather defend a smaller number that holds than a bigger number that costs relationships I can't easily rebuild. Admitting this cost us two clients in a leadership review was uncomfortable. It also built more credibility with my team than defending the original decision would have — they'd watched it fail in real time and needed to hear me say so.

I currently have nine direct reports, and I think that's one too many. Managing Directors, what's your number, and where did it break for you? At six direct reports, two years ago, I could genuinely track each person's development, sit in enough of their client meetings to coach specifically, and catch a problem early because I had real texture on how each part of the business was running underneath me. At nine, following a reorg that consolidated two smaller units under me, I've noticed my 1:1s have become status updates rather than coaching conversations, and I caught a client relationship problem in one unit roughly six weeks later than I would have at six reports, because I simply had less firsthand visibility into that part of the business. What broke specifically: my own calendar. Nine direct reports at even 45 minutes weekly is nearly seven hours before any other leadership work happens. Something gave, and what gave was depth, not frequency — I kept the meetings, I lost the substance. I'm restructuring back toward six to seven by promoting one report into a layer that absorbs three of the current nine, which I should have built proactively instead of reactively discovering the ceiling. What's your real number, and what specifically broke at the one above it? I think the honest answers here matter more than any span-of-control theory.