How to Write a Thought Leadership Book: A Consultant's Guide

You have a method. You have explained it in pitch meetings and workshops for a decade and can draw it on a whiteboard without thinking. What you lack is a book that carries that thinking into rooms you are not in.

The obstacle is rarely writing ability. It is uncertainty about what kind of book this should be. You do not want a “10 tips” book any competent peer could have written, or a glossy brochure for your practice. You want something buyers and peers respect, and you are unsure how much of your method to put in it, or what you may say about the clients who shaped it.

What makes a thought leadership book different from a business book

Most business books explain a subject. A thought leadership book takes a position on it. That position separates it from a tips book, and from a brochure, which talks about the firm rather than the reader’s problem.

The bar is high. In the 2024 LinkedIn and Edelman B2B thought leadership research, fewer than half of decision-makers rated the thought leadership they read as good, and 55% named strong research and data as a top characteristic of high-quality work. Consultant David A. Fields makes the commercial point: your firm will not notice the difference between an okay book and a good one; only a great one moves it.

So the working definition used here is:

Thought leadership = a defensible point of view + evidence + a usable method.

Remove any one and the book slides into a category buyers ignore: a view with no evidence is an opinion piece, evidence with no view is a report, and a method with neither is a manual.

Whether a book is worth it for your practice, and how it fits your sales process, is covered in our main-site guide to the authority book for consultants. This article is about the writing decisions.

Step 1: Pass the point-of-view test before you outline anything

Josh Bernoff lists lack of differentiation among the main reasons business books fail, and suggests a blunt test: can you honestly finish the sentence “This is the first book that…”? If you cannot, he argues, you are just another book on a crowded shelf.

For consultants, a sharper version is: what do you believe about your field that respected peers would argue with? Not provocation for its own sake, but a claim you have seen hold across enough engagements to stake your reputation on.

The Challenger Sale shows the shape. Its publisher’s description centres on a claim that cuts against the classic advice: that “classic relationship building is a losing approach” in complex B2B sales. Whatever you think of it, you can disagree with it, which is why it is worth a book.

If you tick fewer than five, do not outline yet. Reread your proposals and post-engagement reviews for the sentence you keep repeating: “the usual approach gets this wrong because…”. That sentence is usually the book.

Step 2: Build an evidence inventory you are allowed to use

A point of view earns trust through evidence. Before drafting, make an inventory in three columns.

1. Engagement evidence. Patterns from client work: what you found, changed and saw happen. Note whether you have permission to use each, and at what level of disguise.
2. Evidence you own. Diagnostic scores, survey results, benchmarks or before-and-after measures you collected yourself across clients. Even a modest dataset, honestly described, is more persuasive than borrowed statistics.
3. Published research you can cite. Studies, official data and reputable reporting that support or challenge your claim. Open every source and record exactly what it says; a misattributed statistic is a credibility problem for anyone who sells judgement.

Some well-known strategy books rest mostly on the second and third columns. Blue Ocean Strategy is described as based on a study of 150 strategic moves spanning more than 100 years across 30 industries. You do not need that scale. You need each chapter’s claim to trace to something a sceptical buyer could check.

Confidentiality and client permission come first, not at the edit

The best stories in a consulting book partly belong to someone else. The IMC USA code of ethics commits members to treat non-public client information appropriately and not to use proprietary or privileged information without the client’s consent. Your engagement letters and NDAs may go further. This is not legal advice; if a contract is ambiguous, ask a lawyer before you write the chapter, not after.

In practice you have three options for each story:

• Named, with written permission. Strongest, slowest to secure. Ask early and show the client the passage.
• Anonymised. Remove names and change identifying details (industry, size, geography, numbers) until the client could not be recognised by a competitor or by their own staff.
• Composite. Combine several engagements into one illustrative case, and say so in the text.

Strip names and identifiers from documents before sharing them with an editor, a ghostwriter or any AI tool, and read the tool’s privacy terms. Our guide on using client stories in a business book covers telling them well once cleared.

Step 3: Turn your consulting methodology into a teachable framework

A method that lives in your head is not yet a framework. To turn a business framework into a book, it needs three things a reader can use without you in the room.

• Named stages. Three to six steps, each with a name that says what happens in it. Names make the method discussable inside a client’s organisation.
• Decision rules. The “if this, then that” judgements you make without thinking: when to skip a stage, when to stop, what to do when signals conflict. This is where your experience sits.
• Diagnostics. Questions, scores or warning signs that tell readers where they stand. A diagnostic turns a passive reader into someone assessing their own situation.

If your material is scattered across years of decks and notes, sort it before naming anything; our guide to organising years of experience into book chapters covers that step.

Decide what to give away and what to keep back

The fear of giving away the method stops many consulting books. A practical rule: the book teaches the what and the why; engagements deliver the how-for-you.

A reader can learn your stages, reasoning and diagnostics and still be unable to apply them to their own politics, data and deadlines. That application is what clients pay for. Traction sets out a full operating system: BenBella’s description says readers learn to strengthen the six key components of your business, and its author co-founded EOS Worldwide, which the publisher calls one of the largest business coaching companies in the world. The method is in the book; implementation support is sold separately.

Reasonable to keep back: delivery assets such as detailed templates, scoring models, facilitation scripts and pricing logic. Not reasonable: the reasoning. A book that hides its method behind “contact us” reads as a brochure.

Step 4: Choose the type of thought leadership book that fits your method

The same point of view can become very different books, and the type decides your chapter structure and the evidence you need.

Book type	What it does	Best when	Evidence it needs	Main risk
Manifesto	Argues that the field has something important wrong	Your claim is strongly contrarian and the “why” matters more than the steps	Clear examples of the old approach failing; some data	All argument, no method; readers agree and do nothing
Playbook	Teaches a complete, sequenced method	Your process is stable and you have run it many times	Engagement patterns at each stage; decision rules	Turns into a manual with no argument
Field guide	Helps readers diagnose and respond to specific situations	Your value is judgement across many scenarios	Many short anonymised cases; diagnostics	Feels fragmented; weak through-line
Research-led	Presents findings and their implications	You own a dataset or a structured study	Your own data, with method described honestly	Slow to produce; thin if the data is thin

The Challenger Sale and Blue Ocean Strategy both lean research-led; Traction reads as a playbook. Many strong consulting books are hybrids, such as a manifesto opening followed by a playbook, but pick one dominant type so the reader knows what kind of promise you are making.

Step 5: Build a chapter architecture around the argument

Stacy Ennis, writing on Jane Friedman’s site, recommends defining a core message of one to three sentences and a through-line that connects every part of the book. For a consulting methodology book, a simple three-part architecture keeps that through-line visible.

• Part 1: the argument. The problem as your buyer experiences it; why the conventional fix fails; your claim and an overview of the framework.
• Part 2: the method. One chapter per stage. Each chapter follows the same pattern: what this stage is, the decision rules, a diagnostic, an anonymised case, and the most common way it goes wrong.
• Part 3: application. Adapting the method to different contexts, measuring whether it is working, and a frank chapter on when to do this alone and when to get help.

Worked example (hypothetical): an operations consultant

Imagine an independent operations consultant who has spent twelve years with professional-services firms of 50 to 300 people. Her repeated observation: when delivery slips, leaders assume a capacity problem and hire, but the work is usually waiting for decisions, not people.

• Point of view: “Most delivery delays in growing service firms are decision delays, and hiring makes them worse.”
• Peers who would argue: recruiters, resourcing consultants, and the many operations advisers who start with utilisation.
• Evidence inventory: decision-wait timings she has collected in diagnostic sprints (her own data, anonymised and aggregated); three engagements she has written permission to describe in disguised form; published research on management decision-making that she has opened and checked.
• Framework: four named stages (Find the queue, Price the wait, Move the decision, Protect the change), each with decision rules and a one-page diagnostic.
• Book type: playbook with a short manifesto opening.
• Give-away line: the four stages, the reasoning and a simplified diagnostic go in the book; her full scoring model and workshop materials stay in engagements.
• Chapters: three for the argument, four for the stages, three for application. Ten chapters in total.

Notice what is absent: no outcome claims she cannot evidence, no named client without permission, no padding chapter on “the future of work”.

Step 6: Draft in your own voice, from your own material

With the argument, evidence and plan in place, drafting is the long part. You can write it yourself, hire a ghostwriter or use AI with care; we compare the trade-offs in writing a business book without a ghostwriter.

AI carries a specific risk for thought leadership. A general-purpose model asked to “write a chapter on operational delays” produces the consensus view, which is the one your book exists to challenge. That is why AI-written books so often sound generic. The fix is to make it work from your material and voice; see training AI on your writing style for a whole book.

Guided book software is one way to structure this. WritebookAI, for example, analyses your documents, notes and talk transcripts (PDF, Word or text files; decks can be exported to PDF) and shows what the material covers and what is missing. A verification interview resolves gaps and conflicts, then it builds a book strategy and chapter plan with beat sheets. Chapters are drafted from your material in your Writing DNA voice profile; when a client result or statistic is missing, the draft leaves it out and asks you rather than inventing it. You review and approve every chapter and still check every claim. It is not a done-for-you service, so if you want to hand the whole project to someone else, a ghostwriter is the better fit.

Common mistakes consultants make with thought leadership books

• Writing the capabilities deck at book length. If chapters describe your firm’s services rather than the reader’s problem, it is a brochure.
• A view so safe nobody could disagree. “Leaders should communicate clearly” is not a point of view.
• Citing statistics nobody opened. Every number needs a primary source, or it comes out.
• Leaving permissions until the edit. Finding your best case study is unusable after the chapter is written costs weeks.
• Being every book type at once. Manifesto, playbook and field guide in one volume usually ends up as none of them.
• Skipping real readers. Fields recommends beta readers who resemble your ideal clients, not friends, family or other consultants, and at least two per chapter.

What to do this week

Write your central claim in one sentence and run it through the point-of-view test. If it passes, start the evidence inventory: list ten engagements with the permission status of each, plus any data you own. Then sketch your method as named stages with one decision rule each, and pick a dominant book type from the table.

That is a few hours of work, and it will tell you more than months of thinking about it. If the claim fails the test, you have saved yourself a year. If it passes, you have the spine of the book.