20 Book Ideas for Management Consultants, by Practice Area and Buyer

Search for book ideas as a management consultant and you mostly get reading lists: The Pyramid Principle, The McKinsey Way. None of them says what you should write.

The ideas that do circulate are too broad. “Write about leadership.” “Share your framework.” A framework with no evidence behind it is a slide, not a book.

So this list works the other way round. Each idea starts from a practice area you might actually work in, names the executive it would bring to your door, and says what evidence you would need before it could carry 50,000 words. The titles are working titles we made up for illustration, not existing books.

Five book types, and what each demands of you

Decide first what kind of book you can credibly write. Each type needs a different kind of proof.

Book type	What it does	Published example (verified on the publisher’s page)	What you need
Research-led	Makes a claim from data across many companies	Strategy Beyond the Hockey Stick (Wiley, 2018) by three McKinsey partners, built on analysis of “thousands of global companies”	A dataset, and ideally help analysing it
Contrarian argument	Overturns a belief the buyer holds	The Challenger Sale (Portfolio, 2011), whose authors at Corporate Executive Board argue that classic relationship building is a losing approach in complex B2B sales	A clear opposing view and enough cases to defend it
Field guide	Teaches a repeatable process step by step	ReOrg (HBR Press, 2016), a five-step method from two former leaders of McKinsey’s Organization Practice	A method you have run many times
Playbook distilled from project volume	Turns a firm’s accumulated practice into a sequence	Monetizing Innovation (Wiley, 2016) by two Simon-Kucher partners, which condenses more than 10,000 projects into a nine-step approach	Repeated engagements on one problem
Diagnostic or casebook	Lets readers test themselves, or learn from disguised cases	Not named here; we did not verify one for this article	A tool you have used with many clients, or 8 to 12 cases you are allowed to tell

Notice where the examples come from: large firms with research functions. Wiley describes Rewired (2023), by the leaders of McKinsey Digital, as “a road-tested, how-to manual their own consultants use.”

If you are independent, do not compete on research; the firm with the data team wins. Field guides, diagnostics and casebooks are where a sole practitioner with fifteen good engagements can write something a large firm would not bother to.

The 20 ideas, sorted by practice area

Treat each evidence line as a gate: if you do not have it, the idea belongs to someone else.

Strategy and growth

1. The Plan Nobody Funded (contrarian argument). Strategy fails in the budget round, not in the offsite. Buyer: CEO, CFO, head of strategy. Evidence: a comparison, across your engagements, of stated priorities against where capital and headcount actually went.

2. Fewer Bets (field guide). How a mid-sized company kills two-thirds of its initiatives and funds the rest properly. Buyer: CEO of a mid-market or PE-backed company. Evidence: anonymised initiative inventories, the cut criteria you used, and what happened to the freed capacity.

Operations

3. Run It Without Us (field guide). Designing improvements that survive after the consultants leave. Buyer: COO, operations director. Evidence: measurements from returning clients six to twelve months after the engagement ended.

4. The Hidden Factory in the Back Office (diagnostic). Finding rework in finance, HR and customer service processes. Buyer: COO, CFO, head of shared services. Evidence: process maps and rework counts from many clients, plus a self-assessment readers can run on their own team.

Transformation and change

5. Change Fatigue Is a Sequencing Problem (contrarian argument). People are not resistant; they are running five programmes at once. Buyer: CHRO, chief transformation officer. Evidence: programme calendars from engagements showing overlap and any pulse-survey data you collected.

6. The Transformation Office Handbook (field guide). The first 90 days for someone just appointed to run a transformation. Buyer: newly appointed transformation leads, and the CEOs who hire them. Evidence: governance cadences and templates you created (not your former firm’s), and the failure points you have seen repeat.

Pricing and commercial

7. The Discount Leak (diagnostic). Where B2B margin disappears between list price and invoice. Buyer: CFO, chief commercial officer. Evidence: price-waterfall analyses across clients, reported as ranges so no single client is identifiable.

8. Raising Prices Without Losing the Customers You Want (casebook). Ten disguised price increases, including one that went badly. Buyer: owner-CEO of a mid-sized firm, PE operating partner. Evidence: engagement records and agreed permission levels for each case.

M&A and integration

9. Day 100 Is the Wrong Deadline (contrarian argument). Most integration value arrives later than the plan assumes, so the plan should be built for it. Buyer: head of corporate development, PE deal partner. Evidence: synergy-tracking data from integrations you supported past the first 100 days.

10. Integration for Acquirers Who Buy Small (field guide). A lighter playbook for buy-and-build platforms doing several bolt-ons a year. Buyer: CEO or CFO of a platform company, PE operating partner. Evidence: repeated bolt-on integrations and the checklist you refined across them.

Organisation design

11. Spans, Layers and the Meetings in Between (diagnostic). Reading an organisation’s health from its structure data. Buyer: CEO, CHRO. Evidence: org data analyses you have run on many clients, and the thresholds you use to flag a problem.

12. Decision Rights Before Org Charts (contrarian argument). For founder-led companies between 200 and 2,000 staff, redrawing reporting lines without moving decisions changes nothing. Buyer: founder-CEO, COO. Evidence: restructures where reporting changed and decisions did not, with what happened next. ReOrg already covers reorganisation in general, so the founder-led focus is the point.

Procurement

13. The Supplier You Cannot Fire (field guide). Managing single-source dependency in mid-sized manufacturers. Buyer: chief procurement officer, COO. Evidence: supplier-risk assessments across clients and the mitigation steps that held up.

14. Procurement for Companies Without a Procurement Team (field guide). The CFO’s version of category management. Buyer: CFO of a company with 50 to 500 staff. Evidence: spend analyses you have built and the savings ranges you have seen by category, stated cautiously.

Digital, data and AI adoption

15. Why Pilots Stay Pilots (casebook). What stops AI and automation pilots reaching day-to-day use. Buyer: COO, CIO, CEO. Evidence: a count of the pilots you have seen, what stopped each one, and interviews with the people who ran them.

16. Process First, Software Second (contrarian argument). ERP and CRM replacements fail on process decisions made too late. Buyer: CFO and COO facing a system replacement. Evidence: implementation reviews from engagements, with the decision that went wrong in each.

Risk and resilience

17. The Risk Register Nobody Reads (diagnostic). Making risk reporting change decisions at board level. Buyer: audit or risk committee chair, CFO. Evidence: registers you have reviewed, anonymised, and how their scoring compared with what later happened.

18. Continuity Plans Meet a Real Outage (casebook). What actually happened when plans were tested by events. Buyer: COO, CIO, chief risk officer. Evidence: post-incident reviews you led, used only with written permission.

Sector specialisms

19. Patient Flow Is a Scheduling Problem (diagnostic). Hospital capacity treated as a scheduling question rather than a bed count. Buyer: hospital COO, health-system executive. Evidence: patient-flow analyses across sites and the scheduling changes you tested.

20. The Partnership Problem (field guide). Strategy for firms owned by the people who do the work: law, accounting, engineering, architecture. Buyer: managing partner, executive committee. Evidence: engagements with partnerships and the governance patterns you saw repeat.

Coaches need a different list because their buyers are different; see business book ideas for coaches. If your practice is mostly strategy work, see also a book for business strategists.

Choosing one: the three-question filter

You need one idea, not twenty. Score each candidate against three questions and drop anything that fails two.

Question	Strong answer	Weak answer
Do I have evidence nobody else has?	Ten or more similar engagements, or data you collected yourself	Two memorable clients and a lot of reading
Would a respected peer argue with the thesis?	Yes, and you can name who and why	Everyone would nod
Does the buyer have budget for the next step?	The reader signs six-figure work, or advises someone who does	The reader is a middle manager with no spending authority

The second question is the one consultants skip. A book that says “integrations need clear governance” is true and useless. Josh Bernoff’s write-up of the 2024 Business Book ROI study lists lack of differentiation among the four main causes of business books failing, and challenges authors to finish the sentence “This is the first book that…”. In the same study 31% of authors reported higher consulting revenue, while 34% had no gross profit. Bernoff adds that survivor bias probably flatters the results, so treat those figures as an upper bound.

Our blunt rule: if the idea comes from your reading rather than your engagements, it is not your book.

Repeated engagements but no strong view usually means a field guide. A strong view with thin evidence is an article series, which is a fine place to start. Our guide to writing a thought leadership book covers how to sharpen a point of view into a thesis.

A worked example (hypothetical): narrowing three ideas to one

Imagine an independent operations consultant with nine years of practice and about 30 engagements, mostly with mid-sized manufacturers. She likes three ideas from the list: Run It Without Us (3), The Hidden Factory in the Back Office (4) and The Supplier You Cannot Fire (13).

She counts. Only four clients brought her back after the work ended, so idea 3 lacks follow-up evidence and fails the first question. Back-office rework appears in eleven engagements, but her view on it is conventional, and she cannot name a peer who would disagree. Single-source supplier risk appears in fourteen engagements, she holds a view most procurement advisors would dispute (that dual-sourcing is often the wrong fix for a mid-sized firm), and the buyer, a COO, signs the kind of work she sells.

Idea 13 passes all three. Idea 4 becomes a chapter inside it, and idea 3 waits until she has follow-up data.

Validate the idea in two weeks, before you outline

The buyer conversations matter most, and polite interest means nothing. A COO who asks whether the problem applies to her plant in Ohio is telling you the idea works. Our main-site guide to validating an authority book idea goes further on testing the reader, the problem and the argument.

Counting your evidence is the slow part. You can do it by hand with a spreadsheet, as we describe in how to write a book as a consultant. Guided software is another route. WritebookAI runs a source analysis on the PDF, Word and text files you upload and shows what the material covers and what is missing, then a verification interview resolves gaps before it builds a chapter plan. That shows whether an idea has enough material behind it, not whether it is commercially right; only buyers tell you that. Strip client identifiers and read the privacy policy before uploading.

Mistakes we see in consulting book ideas

Writing for other consultants. Peers flatter; they rarely hire.

Choosing the broadest version of the idea. “Operational excellence” competes with every operations book. “Single-source supplier risk in mid-sized manufacturers” competes with very few.

Using a former firm’s method. A framework built while you were employed may not be yours to publish.

Picking the casebook without permission levels. Cases you cannot tell become vague anecdotes. Sort them into named, disguised or pattern-only first, as in our guide to client stories and case studies in a book.

What to do next

Pick three ideas that match your practice, or adapt them, and run each through the three-question filter this week. Count your engagements honestly.

Then take the survivor to three buyers. If two lean in, you have a book. When you are ready to turn the evidence into chapters, organising years of experience into book chapters is the next step.