LinkedIn Post Ideas for Management Consultants

We spent three weeks perfecting a single waterfall chart for the steering committee. Fourteen iterations. Two partner reviews. A color palette debate that consumed an actual hour of billable time. The client glanced at it for maybe six seconds during the presentation and said, "Can you just tell me the number?" What actually moved the engagement forward was a five-minute whiteboard conversation the following Tuesday where we sketched the three scenarios and their trade-offs in marker on glass. I am not saying decks do not matter. Structure and clarity matter enormously. But we confused production value with persuasion value. The client did not need a beautiful chart. They needed someone to stand in front of them and say, "Here is what we think and why." I build fewer slides now.

The first 48 hours of any engagement follow the same pattern. Hour one: resist the urge to solve anything. Listen to the client's framing, then set it aside. Hours two through eight: build the issue tree. Break the core question into three or four mutually exclusive branches. Each branch gets a hypothesis and a test. On a recent cost transformation engagement, the client framed it as "we spend too much on procurement." The issue tree revealed that 60% of the cost gap was actually in logistics — a branch procurement would never have examined. Hours eight through forty-eight: pressure-test the tree with data. Kill dead branches fast. The discipline is unglamorous. But every engagement that went sideways in my career started with a skipped issue tree.

Halfway through a six-month org redesign engagement, the CHRO pulled me aside and said, "I have known we need to eliminate that layer for two years." She was not paying for the answer. She was paying for an external voice to say it in a board presentation with data behind it. Is that legitimate value? I used to feel conflicted. Now I think the answer is usually yes. Internal executives carry political debt. Every recommendation they make is filtered through relationships, history, and career risk. An outside firm carries none of that weight. The analysis still has to be rigorous. The recommendation still has to be correct. But pretending clients always hire consultants because they lack the insight is naive. Sometimes the deliverable is confidence.

I went back through twelve engagements from the past four years and tracked what happened to our recommendations. Total recommendations delivered: 47. Fully implemented within 18 months: 19. Partially implemented: 11. Ignored entirely: 17. A 40% full implementation rate. That number should bother every consultant who reads it. The pattern was clear. Recommendations that were implemented had three things in common: a named owner on the client side, a first action achievable within two weeks, and explicit connection to a metric someone was already measured on. The ignored ones were typically correct but structurally orphaned — no one's job depended on executing them. I now refuse to put a recommendation in a final deck without a named owner and a 14-day first step.

Most stakeholder interviews produce polished talking points. Here is one technique that consistently breaks through. Stop asking for opinions. Ask for stories. Instead of "What are the biggest challenges in your function?" try "Walk me through what happened last Tuesday when that shipment was delayed." The specific instance forces detail. Detail reveals process breakdowns, workarounds, and emotional weight that no opinion question ever surfaces. On a post-merger integration last year, a VP gave me a clean narrative about cultural alignment for twenty minutes. Then I asked her to describe her last cross-entity meeting. The actual story contradicted everything she had just said. She was not lying in the first answer. She was performing. The story gave me the truth. Interviews are not surveys. Treat them like fieldwork.

In 2023 we recommended a client consolidate their three regional supply chains into one centralized operation. The business case showed $14M in annual savings. They thanked us, paid the invoice, and did nothing. Two years later, their new COO found the deck, rebuilt the internal case using our analysis as the foundation, and executed the consolidation. Actual savings in year one: $11M. I only found out because the COO called to ask about a follow-on engagement. Consulting impact is not always immediate. Sometimes the analysis is right but the organization is not ready. Leadership changes, market pressure, or competitor moves create the conditions later. I no longer measure engagement success at final presentation. The real test is whether the work holds up when someone finally acts on it.

Frameworks I use on nearly every engagement: issue trees, value driver trees, MECE categorization, and the 80/20 on any data set. These are thinking tools, not presentation tools. Frameworks I never use: Porter's Five Forces (too static for any market moving at real speed), the BCG Growth-Share Matrix (useful in 1975, misleading today), and the McKinsey 7-S (too many variables, no prioritization). Controversial? Maybe. But I have never seen a client decision change because someone drew a five forces diagram. The test I apply: does this framework force a decision or does it just organize information? If it only organizes, I can do that with a spreadsheet. Frameworks should constrain your thinking, not decorate your slides.

An analyst on my last engagement produced a full market sizing deck in four hours using AI. The same deliverable would have taken two and a half days a year ago. The data gathering, the chart formatting, the slide layout — all compressed dramatically. The output was structurally correct and visually clean. But the "so what" was wrong. The AI synthesized three data sources that contradicted each other and averaged them without flagging the conflict. An experienced consultant would have stopped at the contradiction and reframed the question. Here is what this means for the pyramid model: the base is shrinking. Research, formatting, and first-draft analysis are being commoditized in real time. What remains is judgment — knowing which question to ask and which answer to trust. That is the product now. Adjust accordingly.

Every Sunday night before a Monday kickoff follows the same routine. 6 PM: Re-read the proposal and SOW. Not skim — read. I am looking for promises we made that will be difficult to deliver on the stated timeline. 7 PM: Review every stakeholder's LinkedIn profile. Not for surveillance — for context. Tenure, career path, and recent posts tell me who is likely an ally and who will resist. 8 PM: Draft the first week's interview guide. The questions I ask in week one determine whether the issue tree is right or wrong. 9 PM: Write the team a one-page note covering the three things that could derail this engagement and how we will watch for them. The client sees a polished kickoff Monday morning. They do not see Sunday night. That is by design.

I will go first. Three months into an engagement, the data made clear that the client's core product line — the one the founder built the company around — was unprofitable and had been for two years. Every other business unit was subsidizing it. The founder was still the CEO. I rehearsed the conversation four times. I brought the analysis, the margin waterfall, and two scenarios for restructuring. I did not soften the conclusion. He was quiet for about thirty seconds. Then he said, "I suspected this. I needed someone to prove it." They restructured the product line over the next six months. The hardest conversations in consulting are not about the analysis. They are about saying a true thing to someone who built their identity around the opposite. What is yours?