The McKinsey Way

Ethan Rasiel spent several years as a McKinsey consultant and used that experience to write a book explaining how professionals at one of the world's best-known consulting firms think and work. The promise is to turn what seems like an elite secret into tools anyone can try: solving problems, working on teams, and dealing with clients.

The book is organized around those three areas. First comes the approach to complex problems, then teamwork, and finally the relationship with the client company. Each chapter offers short rules illustrated by behind-the-scenes stories shared by former colleagues and consultants.

It's worth noting that the book dates to 1999. Its anecdotes come from a world before social media, and the text reflects the corporate confidence of that era. Even so, much of the method remains useful for anyone organizing ideas, writing reports, or leading projects.

The firm is often described as a meritocracy, where advancement depends on performance rather than family connections. In practice, recruiting from elite schools also filters who gets access, and American readers know how much someone's social background can affect which doors open.

To explain the method, Rasiel starts with the culture. The firm was shaped by Marvin Bower, who saw consulting as a profession with its own ethical standards, not just another business. The client's interests come before immediate profit, and confidentiality is treated as a sacred obligation.

The selection process is rigorous. The company recruits at leading business schools and values analytical intelligence, communication skills, and teamwork. It then provides intensive training, with its own rituals and language that create a sense of belonging.

The career system is known as up or out: anyone who doesn't advance within the expected timeframe is encouraged to leave the firm. That creates pressure, but it also keeps standards high and builds a network of alumni throughout the business world, often called the McKinsey mafia.

The method's first lesson is to structure the problem before looking for answers. A big, messy problem, such as a company losing money, needs to be broken into smaller pieces. Otherwise, the team gets lost in disconnected data and directionless discussions.

Rasiel introduces the idea of an issue tree, in which the main problem splits into branches, and each branch into more specific questions. For example, profit falls because revenue has declined or costs have risen. Revenue, in turn, depends on sales volume and price.

For the owner of a burger shop, that structure becomes a sheet of paper: did the decline come from fewer customers or a lower average transaction? From the cost of beef or from waste? Organizing the question alone can save weeks of guesswork.

One practical implication is that the initial question matters as much as the answer. If you ask how to sell more, the conversation becomes a jumble of ideas. If you ask which customers generate revenue and why some stopped coming back, the team knows what to investigate.