Thought leadership
Skill anotb/management-consulting-plugin/skills/thought-leadership
Management consulting skills for Claude Code, Cowork, Codex, and other agents. Strategy, operations, and transformation workflows for the full engagement lifecycle.
npx -y skills add anotb/management-consulting-plugin --skill thought-leadershipAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Develops thought leadership content: points of view, white papers, case studies, industry briefs, and research reports. Use when building credibility through published content, creating assets for business development, turning anonymized engagement patterns into reusable insight, or positioning a practice as a trusted authority on a topic. Covers the full arc from thesis through research, structuring, drafting, and quality review. Keywords: point of view, POV, white paper, case study, industry brief, research report.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
19.6 KB, as published. Nobody here has run it
Thought Leadership
Create content that demonstrates real expertise: points of view, white papers, case studies, industry briefs, and research reports. Take a clear position backed by evidence. A generic survey of a topic is not thought leadership. A defensible argument nobody else is making is.
Before You Begin
Credibility depends on what the firm can actually claim. Establish these before drafting:
- What engagement experience can the firm reference? Which industries, what scale, what results?
- What is the firm's real point of view? Has anything been published on this topic already?
- Who is the audience and what is the business purpose (lead generation, credibility, recruitment)?
Never fabricate first-person experience. Claims like "across 40+ engagements we've observed..." require data the user supplies. Without it, use conditional framing: "organizations that do X tend to see Y" or "research and practitioner evidence suggests..." Fabricated engagement counts in published content are a credibility risk that outlives the piece.
Asset Types
Match the asset to the goal. The wrong format kills a good thesis.
| Type | Best For | Total Length | Density |
|---|---|---|---|
| Point of View | Taking a position on a trend or issue | 800-1,500 words (1-3 pages) | High. Every sentence earns its place. No throat-clearing. |
| White Paper | Deep analysis with recommendations | 3,000-6,000 words (5-15 pages) | Moderate. Room for evidence and examples, no padding. |
| Case Study | Showcasing engagement results | 600-1,200 words (1-3 pages) | Story-driven. Lead with results, then explain how. |
| Industry Brief | Current state and outlook for an industry | 1,500-3,000 words (3-5 pages) | Data-dense. Charts and tables do heavy lifting. |
| Research Report | Original research findings | 5,000-10,000 words (10-20 pages) | Methodology-driven. Evidence first, interpretation second. |
Step 1: Define the Asset
Establish what you are building and why before writing a word.
- Type: Which asset above.
- Topic: The subject area.
- Thesis: The core argument in one sentence. This is the most important element. If you cannot state it in one sentence, the thinking is not sharp enough yet.
- Target Audience: Who reads this (C-suite, functional leaders, industry practitioners).
- Business Purpose: What it achieves (credibility, lead generation, client education, recruitment).
Strong vs. weak thesis statements
The thesis is the single sentence that decides whether the piece is worth reading. Most consulting thought leadership fails here by being too obvious or too vague.
Point of View:
- Weak: "Digital transformation requires strong change management." Everyone knows this. Nobody would disagree. No reason to read on.
- Weak: "The future of work is changing." True of every era. Says nothing.
- Strong: "Companies that embed AI into their core operating model within the next 18 months will open a capability gap that laggards cannot close through later adoption." Specific, time-bound, debatable, has implications.
- Strong: "The biggest barrier to supply chain resilience is not technology or cost. It is that most companies try to optimize for efficiency and resilience at once and achieve neither." Names a specific, non-obvious tension.
White Paper:
- Weak: "Organizations should consider multiple factors when evaluating cloud migration." Which factors? Why? This is a table of contents, not a thesis.
- Strong: "Most cloud migrations deliver 40-60% of projected savings because they replicate on-premises architecture in the cloud rather than redesigning for cloud-native economics." Quantified, causal, actionable.
Case Study:
- Weak: "A major retailer improved its supply chain with our help." So what? How much? What was different?
- Strong: "By shifting from forecast-driven to demand-sensing replenishment, a $4B retailer cut inventory carrying costs by 23% while lifting in-stock rates from 94% to 98.5%." Specific results, specific method.
The test: if your thesis could run in a competitor's publication and nobody would notice, it is not distinctive enough.
Step 2: Build the Evidence Base
Research-backed, not opinion dressed as insight. Build four kinds of evidence.
Market Intelligence
Gather external data: industry reports, academic research, expert commentary. For each source, capture the key finding and whether it supports or challenges the thesis. Evidence that only confirms your view is a warning sign you have not looked hard enough.
Engagement Experience
The most distinctive evidence comes from real client work. This is what separates consulting thought leadership from journalism and academic research. Identify patterns across engagements: what you observed, how often, in which industries, and what it means. Always anonymize. The pattern is the insight. The client name is irrelevant.
Frame it with specificity. "Across 30+ supply chain transformations over the past three years, we observed that..." is credible. "In our experience..." is hand-waving. Only assert a count the firm can substantiate. If the number is not verified, drop to conditional framing rather than inventing one.
Counterarguments
Map the opposing views. For each, judge its validity (strong, moderate, weak) and prepare a response. Thought leadership that ignores counterarguments reads as advocacy, not analysis.
- Strong: Acknowledge it, concede the valid part, then explain why the thesis still holds. "This is true in stable markets. In volatile environments the calculus changes because..."
- Moderate: Name it, explain why it is partly right, and show the conditions under which your position is more useful.
- Weak: Do not demolish straw men. It signals insecurity. Skip it or handle it in one sentence.
Worked example (strong counterargument):
"The obvious objection: will faster adoption mean higher failure rates? The data suggests otherwise. Companies that moved early on cloud between 2015-2018 had lower total migration cost than late movers, mainly because they migrated simpler workloads first and built institutional capability before tackling complex systems. Speed of decision is not speed of execution."
Data Points
Collect specific statistics with source and context. "According to [Source], X% of [initiatives] failed to meet their stated objectives" is useful: specific, sourced, verifiable. "Digital transformation is hard" is not. Label any illustrative figure as an example and flag it for validation. Present benchmarks as illustrative with their source and context, never as authoritative fact.
Step 3: Structure the Content
Each asset type has a proven structure. Do not reinvent it. Word counts are approximate. The point is proportional emphasis, not hitting a number.
Point of View (800-1,500 words)
- The Shift (150-250). What is changing. Open with the most surprising or counterintuitive data point, not with context-setting.
- Why It Matters (150-250). Impact on organizations and leaders. Quantify the stakes.
- The Opportunity (200-400). What leading organizations are doing. Use 2-3 specific examples (anonymized client work or named public companies).
- Our Perspective (200-400). What should be done and why. This is the thesis section. Take a clear position.
- Getting Started (100-200). 3-5 first steps, specific enough to act on Monday morning.
White Paper (3,000-6,000 words)
- Executive Summary (300-500). Findings and recommendations. Must stand alone. A reader who sees only this gets the thesis, the evidence, and the recommended action.
- The Challenge (400-800). Problem definition with data. Quantify the cost of the status quo.
- Current Landscape (500-1,000). State of the market. What has been tried, what worked, what did not.
- Analysis (800-1,500). The deep dive. This is where the original thinking lives.
- Framework (500-1,000). Proposed approach or model. Actionable, not just conceptual.
- Case Examples (400-800). 2-3 illustrative, anonymized examples. Focus on the pattern, not the story.
- Recommendations (300-500). 5-7 specific actions ranked by impact and feasibility.
- About the Authors (50-100). Credibility and contact.
Case Study (600-1,200 words)
- Client Context (100-200). Industry, size, situation (anonymized). Enough for the reader to see themselves.
- The Challenge (100-200). The problem. Quantify the pain.
- Our Approach (200-400). Methodology and key activities. What was distinctive, not a generic process description.
- Results (100-200). Quantified outcomes. Lead with the headline number. Include timeline.
- Key Takeaways (100-200). 3-4 generalizable lessons. What would you tell someone facing the same situation?
Industry Brief (1,500-3,000 words)
- Industry Snapshot (200-400). Key metrics and trends. Table or chart format is ideal.
- Forces Shaping the Industry (400-800). 3-5 drivers and disruptors with evidence for each.
- Implications (400-800). What this means for participants. Segment by player type if relevant.
- Outlook (200-400). Near-term (12 months) and medium-term (3-5 years) forecast with specific predictions.
- Recommended Actions (200-400). 5-7 strategic priorities, rank-ordered.
Research Report (5,000-10,000 words)
- Executive Summary (500-800). Headline findings. 5-7 takeaways, one sentence each.
- Methodology (300-500). How the research was run. Sample size, approach, limitations.
- Findings (2,500-5,000). Data and analysis, section by section. Lead each section with the finding, then show the evidence.
- Discussion (800-1,500). Interpretation and implications. What the findings mean for the thesis.
- Recommendations (500-800). What to do with the knowledge.
- Appendices. Full data tables, methodology detail.
Step 4: Draft the Content
Opening Hooks
The first 2-3 sentences decide whether anyone reads on. Most consulting content opens with context-setting ("In today's rapidly evolving business landscape...") and loses the reader immediately.
Lead with a counterintuitive finding:
"The companies spending the most on cybersecurity are not the most secure. Our analysis of 200 enterprise security programs found an inverse correlation between budget growth and breach reduction after the first $10M in annual spend."
Open with a specific, surprising number:
"It takes the average Fortune 500 company 14 months to fill a Chief Digital Officer role. By the time they start, the strategy they were hired to execute is already obsolete."
Start with what everyone gets wrong:
"The conventional wisdom on pricing is backwards. Most companies start by analyzing willingness-to-pay. The companies capturing 15-20% more revenue start by analyzing willingness-to-lose: which customers will actually leave, and at what price?"
Name the tension directly:
"Every CEO we spoke to this year says they want to move faster. Every operating model we assessed this year is built to prevent exactly that."
Openings to cut:
- "In today's rapidly changing..." Content-free.
- "It's no secret that..." Then why write about it?
- "As organizations increasingly..." Slow, passive, generic.
- "The world of [X] is undergoing a transformation..." Could open any article about anything.
- "Now more than ever..." Every era says this. It never adds information.
The discomfort test: take a position the reader might reject. If everyone nods along, the thesis is too soft. The best thought leadership makes the reader uncomfortable before it persuades them. An opening that offends no one interests no one.
The Consulting Voice
Consulting thought leadership has a voice that separates it from journalism, academia, and marketing. It says: we have done this work, repeatedly, and here is what we learned.
-
Claim the experience directly, but only what is real. "Across 40+ operating model transformations" beats "many companies find that..." when the firm can back the number. When it cannot, do not invent it. Use evidence-based framing instead: "Organizations that make this transition successfully tend to..." or "Research and practitioner evidence suggests..." If the user supplies real firm experience, use it. Otherwise frame insights as industry patterns, not personal claims.
-
Be specific about scale. "Most companies" is weak. "In 23 of 30 organizations we assessed" is credible. Numbers need not be exact ("30+", "roughly two-thirds") but they need to be there. Without the firm's real figures, use conditional framing: "Firms that have run 20+ transformations in this space report that..."
-
Name what surprised you. The most credible thing a consultant can write is "We expected X but found Y." It signals genuine inquiry, not marketing dressed as analysis.
-
Use "we believe" deliberately. Reserve it for opinion that goes past the data. "We believe the next 18 months will set market position for a generation" is a belief. "Organizations with flatter structures make faster decisions" is a finding. Do not confuse the two.
-
Kill consultant cliches. "Best practice," "world-class," "synergies," "leverage" as a verb, "holistic," "robust," "unlock value," "drive transformation." These signal lazy thinking. Say the specific thing. Instead of "best practice," describe what the best performers actually do. Instead of "holistic approach," name the three things you would integrate. Instead of "unlock value," say what the value is and where it comes from.
-
Show your work. Describe the analysis, not just the conclusion. "When we mapped decision latency against organizational layers, the correlation broke at layer 6" convinces where "too many layers slow decisions" does not.
-
Say "it depends," then say what it depends on. Nuance is not weakness. "This works for companies above $500M in revenue with existing digital infrastructure. Below that threshold, a different approach is needed" is more useful than a universal claim.
Visual Elements
Recommend visuals that add understanding text cannot carry alone:
- Charts and graphs: quantify key points. One clear chart beats three cluttered ones.
- Frameworks and diagrams: visualize a model only when the picture teaches something the prose cannot.
- Pull quotes: pull the single most provocative sentence from each major section for scanners.
- Callout boxes: practical tips or supplementary detail that would interrupt the main line of argument.
Client Approval for Content Referencing Engagement Work
Any piece that draws on client engagement experience, even anonymized, needs a clear approval process. Getting this wrong creates legal exposure and destroys client trust.
| Content Type | Approval Required | Process |
|---|---|---|
| Anonymized pattern ("Across 30+ transformations, we observed...") | Internal review only | Engagement manager confirms no identifying details. Legal/risk reviews when the pattern is industry-specific enough to narrow identification. |
| Anonymized case study (specific situation, disguised) | Client approval required | Send the draft to the client sponsor. Allow 2 weeks. Accept redactions without argument. |
| Named case study (client identified) | Written client approval | Formal sign-off from the client's communications/legal team, not the sponsor's verbal OK. Include the final publication form. |
| Quoting client personnel | Written approval from the individual and their comms team | Provide the exact quote in context. Let the individual revise. Some organizations prohibit employee quotes entirely. |
Practical guidance:
- Build approval into the timeline. Do not finish the piece and then discover the client needs 4 weeks for legal review.
- When in doubt, over-anonymize. Change the industry, geography, company size, or time period. The insight is in the pattern.
- Some clients ban any reference to the engagement, anonymized or not. Check the contract for publication restrictions.
- If a client declines, accept it. Pushing back costs more than the content is worth.
Practice-Level Coordination
Multiple partners publishing on the same topic without coordination produces contradictory viewpoints under one firm's name. Embarrassing at best, brand-damaging at worst.
- Topic registry: a simple list of who is publishing what, when, and the core thesis. Review quarterly. Two partners can disagree, but they should know they are doing it.
- Thesis alignment check: before drafting, circulate the one-sentence thesis to practice leadership. Flag conflicts with published positions. Genuine disagreement is fine when handled deliberately (a "counterpoint" framing). Accidental contradiction is not.
- Retired positions: when the firm's view evolves, retire the old one explicitly. Update or remove outdated content. A client reading your 2024 and 2026 white papers should see evolution, not confusion.
- Cross-practice coordination: when a topic spans practices (for example, "AI in financial services" touches both the AI and FS practices), name a lead practice and require the other to review before publication.
This does not need to be bureaucratic. A shared spreadsheet and a quarterly 30-minute review covers most firms. The goal is awareness, not approval by committee.
Step 5: Review and Quality Check
Content Quality
- Thesis is clear and defensible.
- Evidence supports the argument, including evidence that cuts against it.
- Counterarguments are addressed, not ignored or strawmanned.
- Recommendations are actionable this quarter, not "adopt a culture of..."
- Examples are anonymized appropriately.
- Data is current and properly sourced. Illustrative figures are labeled and flagged for validation.
- No proprietary client information disclosed.
- The piece says something a competitor would not or could not say.
Writing Quality
- Opening hooks the reader inside two sentences.
- Structure is logical and easy to follow.
- Every paragraph earns its place. Cut anything that is "nice context" but does not advance the argument.
- Technical terms are defined on first use.
- Transitions are smooth.
- The close reinforces the key message and ends with a clear call to action.
The "So What?" Test
Read each section and ask: so what? If the answer is not obvious, the section is missing its synthesis. Every section should end with a sentence stating why the analysis matters for the reader's decisions.
Key Principles
- Strong thought leadership takes a clear position. A wishy-washy conclusion signals weak thinking.
- Use engagement experience as evidence, always anonymized.
- Quality over quantity. One excellent piece beats five mediocre ones.
- Timeliness matters. Connect to the current industry conversation.
- Involve practitioners. The best insights come from the people doing the work.
- Test the thesis with clients before publishing. Their reaction is the best validation.
- Update or retire assets when the market shifts. Stale thought leadership undermines credibility.
- The best thought leadership makes the reader slightly uncomfortable. If everyone already agrees, you have not said anything worth reading.