The best books for consultants, by the skill each one builds

The best books for consultants sit on two shelves. The craft shelf, led by The Pyramid Principle, teaches the mechanics of the job: framing a problem and building pages that answer it. The judgment shelf covers what structure can't, such as noticing when the client's data is misleading you and knowing what to say when the answer is unwelcome. Read the craft books for structure and the books below for judgment.

This list is for analysts and associates in their first three years at a consulting firm, or about to start. Each section pairs a skill you'll use most weeks with the books that build it, then gives you an exercise to run on your current project on Monday. They also work as books for business consultants who run their own practice, because the judgment problems are the same.

The craft books every management consultant should read

Lists of books for consultants to read usually include these five, and they earn their place. Knotd doesn't carry them; a library or bookstore will.

• The Pyramid Principle (Barbara Minto). Put the answer first, then group the supporting arguments beneath it. Minto's own site presents it as a method for everyday business documents, from memos to presentations, alongside her SCQ (situation, complication, question) framework for openings. Read it before you write your first storyline.
• The McKinsey Way (Ethan Rasiel, 1999). A former McKinsey associate's account of how the firm frames problems and presents findings, in short chapters. Its sections on presentations and winning client buy-in explain habits you'll see at most firms.
• Flawless Consulting (Peter Block). Now in its fourth edition. Its core is contracting: agreeing with the client, early and out loud, on what each side wants. It's aimed at anyone who influences without direct authority, internal consultants included.
• Case Interview Secrets (Victor Cheng, 2012). Written by a former McKinsey consultant and case interviewer to help you get the offer. Read it before your interviews; its habit of testing a hypothesis with an issue tree carries over to the job.
• The Trusted Advisor (David Maister, Charles Green and Robert Galford). The book that introduced the trust equation: credibility, reliability and intimacy, divided by self-orientation. Read it when clients start calling you directly.

Spotting bias in the client's data

Thinking, Fast and Slow (Daniel Kahneman, 2011)

The problem it solves: you will believe a clean story built from whatever data the client handed you. In Thinking, Fast and Slow, Kahneman calls the fast, automatic mode of thinking System 1 and the slow, effortful mode System 2. His core argument is that the slow mode checks the fast one far less than we assume.

His 2002 Nobel Prize lecture shows it with an arithmetic puzzle the psychologist Shane Frederick gave to students. Half of the Princeton students tested (47 of 93) and 56% of University of Michigan students (164 of 293) gave the quick, wrong answer. They answered without checking, and Kahneman described that self-monitoring as normally "quite lax." His point is that many intelligent people skip the check.

Bring to work what Kahneman calls "what you see is all there is." The mind builds the most coherent story it can from the evidence in front of it and rarely asks what's missing. The client's data is the data the client chose to collect.

Skip it if you read it at university. The Nobel lecture makes the core argument in about 40 pages, free on the Nobel site. For what to read next, see our list of books like Thinking, Fast and Slow.

The Black Swan (Nassim Nicholas Taleb, 2007)

The problem it solves: risk that doesn't show up in the history. In The Black Swan, Taleb's idea of silent evidence is that the record keeps the survivors and loses the failures, so a benchmark of "top performers in the sector" is a list of companies that lasted. His turkey, fed every day for a thousand days, grows more confident in the farmer right up to the day before Thanksgiving. A client who says "that has never happened here" may be the turkey.

Skip it if you want a short, even-tempered read. Part One holds what a consultant needs: silent evidence and the narrative fallacy.

Use it on Monday: run a premortem on your current hypothesis. Gary Klein described the method in Performing a Project Premortem (Harvard Business Review, September 2007): the team assumes the project has just failed, then generates plausible reasons why. Klein's case for it is that it makes it safe for informed doubters to speak up, and Kahneman recommends the technique in Thinking, Fast and Slow. On a project:

1. Take the hypothesis on your storyline page.
2. Imagine the final steering committee rejected it. Write every reason down alone, before the team discusses it.
3. Mark the reasons that depend on data you don't have yet.
4. Turn the top two into analyses on this week's workplan.

Thinking with many models

Poor Charlie's Almanack (Charlie Munger, edited by Peter Kaufman)

The problem it solves: the one-framework habit. On a project you'll be handed a profit tree or an issue tree and asked to fill it in. Poor Charlie's Almanack collects eleven of Munger's talks, first published in 2005 and reissued by Stripe Press. A warning that runs through them is the man with a hammer: someone with one model sees every problem as a fit for it.

His fix is a latticework. Carry the big ideas from several fields, such as incentives from psychology, compounding from mathematics, redundancy from engineering and supply and demand from economics, and test an answer against more than one. Two of his tools suit consulting well. Inversion means working out what would guarantee failure, then avoiding it. On incentives, Munger thought people almost always underrate how much pay and reward explain behavior.

Skip it if you want a cover-to-cover read. Start with his talk on the psychology of human misjudgment.

Use it on Monday: invert the client's question. If the question is how to grow margin, list the ways to guarantee that margin falls, then check which of them the client is doing now. Then, for each recommendation in your draft, note who at the client is paid in a way that gives them a reason to resist it.

Reading the numbers

Financial Intelligence (Karen Berman and Joe Knight)

The problem it solves: you'll be asked to work on a client's P&L long before anyone teaches you to read one. Berman and Knight wrote Financial Intelligence for managers without finance training. Their first big idea is that finance is partly an art: reported profit rests on estimates and judgment calls, like when to count a sale as revenue and how fast to depreciate equipment. Their second is that profit and cash are different things, so a growing business can run short of cash while reporting a profit.

Skip it if you have an accounting or finance degree.

The Personal MBA (Josh Kaufman)

The problem it solves: your first week in a new industry, when every term is unfamiliar. Kaufman breaks any business into five parts: it creates something of value, markets it, sells it, delivers it, and pays for all of that. It's a quick map for placing a client's org chart and costs.

Skip it if you have an MBA. Keep the five parts as a checklist instead.

Use it on Monday: read the client's P&L and write three questions.

1. Put this year's and last year's P&L side by side and express every line as a percentage of revenue.
2. Circle each line that grew faster than revenue.
3. For each circle, write the question it raises. "Gross margin fell while revenue grew: is it price or product mix?" is a good shape.
4. Compare operating cash flow with net income. If cash is well below profit, add a question about why.
5. Keep the best three questions and take them to your manager before the client meeting.

Books for strategy consultants: the frameworks you'll hear at kickoff

Good to Great (Jim Collins, 2001)

The problem it solves: the vocabulary. Client executives use Collins's terms: the hedgehog concept, the flywheel, Level 5 leadership, "first who, then what." For Good to Great, Collins's team screened 1,435 companies for a jump from roughly average stock returns to at least three times the market over fifteen years. Eleven passed, and the book is about what they shared.

Read it with the debate attached. Two of the eleven had a hard 2008: Circuit City filed for bankruptcy, and Fannie Mae was placed into government conservatorship. Collins studied decline in How the Mighty Fall (2009), and his page for that book names both. Kahneman, in Thinking, Fast and Slow, uses Built to Last, which Collins wrote with Jerry Porras, to show how success stories underweight luck and regression to the mean. It's Taleb's silent-evidence problem again.

Skip it if you want evidence you can cite in a deck. Read it for the questions it teaches you to ask about a leadership team.

Blue Ocean Strategy (W. Chan Kim and Renée Mauborgne, 2005)

The problem it solves: a growth project in a market where every competitor offers the same things. Kim and Mauborgne, strategy professors at INSEAD, argue for creating new demand instead of fighting over share. Their two main tools are the strategy canvas, a chart of the factors an industry competes on, and the four actions framework, which asks which of those factors to eliminate, reduce, raise and create.

Skip it if your project is a cost program or an operations fix. For more on strategy and management, see our business books.

Use it on Monday: draw the strategy canvas from the kickoff deck. List the eight or so factors the client's industry competes on along the bottom of a page. Score the client and its two closest rivals from 1 to 5 on each and join the dots. Where the lines run together, apply the four actions to find what the client takes for granted.

Making the story land

Made to Stick (Chip Heath and Dan Heath, 2007)

The problem it solves: the curse of knowledge. After three weeks in the data you can't remember what it was like not to know it, so your slide titles assume context the client doesn't have. In Made to Stick, the Heaths name six traits of ideas that stick: simple, unexpected, concrete, credible, emotional, and told as stories. For a consultant, concrete does the most work. One named store with falling sales beats a regional average.

Skip it if you've written for a general audience before, say as a journalist.

Talk Like TED (Carmine Gallo, 2014)

The problem it solves: delivering the readout. Gallo broke down hundreds of TED talks and interviewed popular TED speakers, and much of his advice suits a steering committee: rehearse until it sounds like conversation, and teach the room one thing it didn't know.

Skip it if you rarely present. Made to Stick does more for the writing, which is most of the job early on.

Use it on Monday: rewrite your executive summary for someone who wasn't in the room. On the summary page, replace one abstract claim per headline with a concrete example the CFO could repeat to the board. Then say the summary out loud to a teammate, without slides, and cut whatever you stumble on.

Persuading a skeptical client

Influence (Robert Cialdini)

The problem it solves: a correct recommendation the client still won't accept. The principles in Influence (reciprocity, commitment and consistency, social proof, authority, liking and scarcity, plus unity in the new and expanded edition) describe why people say yes. Two matter most on a project. Commitment: people stay consistent with what they've already agreed to, so agree on the problem before you present the answer. Social proof: a skeptic moves more readily when similar companies have already made the change.

Use them honestly: cite real peers, never invented ones.

Skip it if you studied it in a marketing course. Reread the chapter on commitment and consistency.

Use it on Monday: pre-wire the skeptic. Before the steering committee, book a short one-on-one with its most skeptical member. Show them the problem statement, not the answer, and ask what you've missed. By the meeting they've helped shape it. Consultants call this a pre-wire.

The hard client conversation

Crucial Conversations (Kerry Patterson, Joseph Grenny, Ron McMillan and Al Switzler)

The problem it solves: the talk you're putting off, like telling a client manager their numbers are wrong or telling your engagement manager the workplan doesn't fit the hours. The authors define a crucial conversation as one where stakes are high, opinions differ and emotions run strong. Their main advice is to keep it safe enough that both sides keep talking, and their most practical tool is separating the facts from the story you've built on top of them.

Skip it if you've been through a training course built on it. Reread the chapter on stories instead. When you start running a team yourself, our list of books for first-time managers picks up from here.

Use it on Monday: write facts and story in two columns. Before the conversation, list on the left only what a camera would have recorded ("our model shows churn at 4%; their deck says 2%"). On the right, list the story you're telling yourself ("they're hiding the bad quarter"). Open with the left column, and ask for their view before you share anything from the right.

Your own career in consulting

Range (David Epstein, 2019)

The problem it solves: the worry that you're falling behind by not specializing. Epstein argues that breadth pays off in "wicked" settings, where feedback is slow and the rules are unclear, and that a sampling period of trying several fields often leads to a better long-term fit. The first years of consulting are a sampling period by design: a new industry and a new function every few months.

Skip it if you already know your specialty and joined a practice built around it.

Deep Work (Cal Newport, 2016)

The problem it solves: on a staffed project the day fills with calls and slide fixes, and the model never gets the focused hours it needs. Newport separates deep work, concentrated effort that creates new value and is hard to copy, from shallow work that is easy to copy and easy to interrupt. His fix is to schedule deep work on purpose instead of hoping a gap appears.

Skip it if most of your week is client time you don't control. Read only the chapters on scheduling.

Use it on Monday: start a project log and block one morning. At the end of each week, write two lines: what you learned and what you enjoyed. After a few projects, read the log back for a pattern; that's Epstein's sampling period with notes. Then book one morning of deep work as a calendar meeting named for the analysis it's for, so it survives rescheduling.

Skill map: the best books for consultants, by skill

The bias row is the easiest to practice away from a live project. Knotd, our app, has a format called Spot the Trap: you read a short case file, tap the line where the reasoning goes wrong, then name the trap. It's the same check you run when reviewing a deck.

If you start at a firm next month, read in this order:

1. The Pyramid Principle, because your first deliverable will be pages.
2. Financial Intelligence, because your first analysis will likely sit on a P&L.
3. Thinking, Fast and Slow, once you've seen enough client data to recognize its traps.
4. Crucial Conversations, before your first review or your first tense client meeting.

Pick one exercise from the table for this week, not four. For a method that turns any of these books into habits, see how to apply what you read.