McKinsey Culture

How the strongest professional culture in business was built one word at a time. By an alum who lived it, taught it, and finally left it.

The Real Story

McKinsey never ran a cul​ture program. It chose a language, policed it for ninety years, and let the language build the firm. I spent five years inside it. This is how it actually works, what it creates, and what it costs.

The Words Came First

In 1933, a young lawyer named Marvin Bower left one of the most prestigious law firms in America to join a small accounting-and-engineering outfit in Chicago. What he did next is the most underrated act of culture building in business history: he chose the words. McKinsey would be a firm, never a company. It would run a practice, not a business. Client work would be an engagement, not a job. The people would be consultants and colleagues, never employees, serving clients, never customers. Bower had watched what a professional lexicon did to lawyers, how it made them carry obligations instead of contracts, and he installed that vocabulary in a firm that had not yet earned it. Then he spent the next sixty years policing the usage, down to selling his own equity back at book value to prove the words meant what they said.

The culture everyone studies came later. The language came first, and the firm grew into it.

Most companies build a culture and hope a language emerges. McKinsey chose a language and let it build the firm.

And it was not one borrowed language. It was two, fused. From the law firm came the professional lexicon: the Firm, the practice, the engagement, the client. From the laboratory came the other half, because the founders took the scientific method and translated it into business: the problem statement, the hypotheses, MECE, the analyses that prove or disprove. One language installed obligation. The other installed rigor. Every McKinsey consultant who ever lived was shaped in the collision of those two vocabularies, and almost none of them noticed it happening.

The McKinsey terms: the language that built McKinsey's culture, organized across the work, the engagement, the team, the career, and the firm, from problem statement and MECE to obligation to dissent and up or out.

A Summer in Boston: Learning a Culture One “What’s That?” at a Time

I noticed it happening, because I lived it. I spent the summer between my first and second year at Tuck as a summer associate in the Boston office, and the language started immediately. Here is the thing about walking into a firm like that: you start hearing the terms and you cannot just nod along. I needed the definitions, because the definitions were what would mold me. So every time a term surfaced that meant nothing to me, I asked the same two words: what’s that?

I was asked to pre-syndicate my deck. What’s that? My EM did not hand me a definition. He handed me a worldview: it is our way to get everyone aligned and get final feedback before the final presentation. Go spend one-on-one time with everyone who will be in the meeting. Get their feedback. Understand their perspective and their potential blockers.

Read that answer again. It is an entire philosophy of influence in four sentences: decisions happen before meetings, alignment is built one conversation at a time, nobody gets surprised in the room, and other people’s objections are information you go get, not obstacles you hope to survive. I walked out of that conversation thinking differently about every meeting I would ever run, and I was a summer associate.

A few weeks in, I was put in charge of the ghost deck. What’s that? The final presentation, built before the work: every page laid out, every action title written, the whole argument standing there as empty slides waiting for the analyses to fill them in. Sit with that one, because it rewires how you think about work itself. The argument comes first and the evidence is fetched to test it, the scientific method smuggled into a slide deck. And notice who they handed it to: a summer associate between his first and second year of business school. When the thinking lives in a shared structure, even the newest person in the building can hold the skeleton of the whole study.

That was the whole summer, and then the whole five years: a journey of learning the culture through the language. Each term installed a way of thinking. The thinking drove the behaviors. The behaviors, repeated by everyone around me, were the culture, and the culture produced the performance clients paid millions for. Language, thinking, behavior, culture, performance. I did not have words for that chain yet. I was living it. Nobody ever sat me down and taught me the McKinsey culture. There was no course. The lexicon was the course.

I know that for certain, because later I helped teach it. I was on the McKinsey mini-MBA team that taught incoming PhDs, MDs, and JDs, brilliant people who could run a lab or argue a case but had never framed a business problem in their lives. We were not teaching them business, exactly. We were teaching them the language, and I watched it rewire them in weeks. The surgeon learns to ask so what, and suddenly she synthesizes instead of describes. That is when I understood that enculturation at McKinsey was not an event. It was vocabulary acquisition.

The Lexicon: An Operating System in Words

Here is the language itself, organized the way I actually lived it: the words of the work, the words of the firm’s character, and the words of your career. Watch what each one installs.

The Language of the Work

The five questions. Every project on earth started identically: what is the problem statement, what are the hypotheses, are they MECE, what analyses prove or disprove them, and storyboard the answer before you build a single page. I have written elsewhere about how this shared cognitive framework let the firm staff anyone onto anything, anywhere, and have them functional in days. It is the scientific method wearing a suit.

So what?. Two words that convert analysis into implication. You could feel the question coming before you finished a sentence, so you learned to finish the thinking before you started the sentence.

Answer first. Lead with the conclusion, then support it. Day one answer: form your best hypothesis before the comfort of research, then attack it. Together they installed a bias that never left any of us.

Synthesize. Not summarize. Synthesis was the job: many analyses in, one meaning out. A summary tells people what you found. A synthesis tells them what it means and what to do about it, and the question came at you constantly: what is the synthesis? Entire documents lived or died on whether the writer knew the difference.

80/20. Used constantly, and used as a verb. Which 20 percent of the analysis gives 80 percent of the answer? Eighty-twenty the workplan. It was permission, granted by the firm’s own vocabulary, to skip the exhaustive thing and attack the vital few, and it is a large part of why a McKinsey team moved at the speed it did. Most organizations have no word that grants that permission, so their people polish everything equally.

Leverage. A whole theory of multiplication in one word, and it ran in every direction. You leveraged a followership, people who wanted to work with you again, so more hands were working on your program. You leveraged the knowledge centers in India to build slides and run analyses overnight. You leveraged the client team to own workstreams, which developed them and freed you. Notice the terms locking together: followership feeds leverage, leverage feeds your program. The word taught you to never be the bottleneck of your own impact. I did not fully appreciate until later that the same word was quietly describing what the firm was doing with all of us. Hold that thought.

Pre-syndication. You already know this one. It was my first what’s-that, and it remains the single most useful working practice I have ever stolen from anywhere.

The Language of Character

Obligation to dissent. Not a right. An obligation. If you believed the team was wrong, staying quiet was the violation, regardless of your rank. And it was not wall art. I watched a director stop a meeting, turn to us, and say it out loud:

So what do you think? You have the obligation to dissent. Let me hear it now.

That is a commitment being invoked, live, as a tool to pull truth into a room. A value can be admired. An obligation gets used on you. It is the direct ancestor of the commitment I now build cultures around, Speak the Truth with Respect, and the family resemblance is not an accident.

Meritocracy. The best idea wins regardless of who said it, which is the only condition under which an obligation to dissent is survivable. The two terms need each other.

Followership. The firm named, and evaluated, the half of teamwork every other company pretends does not exist: how well you support, strengthen, and are trusted by the people around you when you are not the one leading. More on where that question showed up in a moment.

Mentorship. Apprenticeship was the teaching model, and the roles had names: your EM, your DGL, your Development Growth Leader, your mentors. When roles have names, the relationships they describe actually happen, because a named role can be asked about, staffed, and held accountable.

The Language of Your Career

Your program. Ownership of your own trajectory, compressed into two words, and given teeth in reviews, which asked directly: what is your program? Meaning: which client service teams, which CSTs, are you really part of? What is your expertise, function and industry, tech sales and marketing, industrial operations, financial services strategy? The word defined the shape a McKinsey career was supposed to take: a deepening spike. The profile it produced even had its own admiring adjective: spikey.

Here is mine, honestly. I started in the Seattle office and spent five years ranging as widely as the firm would let me: high tech, industrial, and financial services, across sales and marketing, strategy, org, and operations. I helped stand up the Management Innovation Lab with Gary Hamel, who with C.K. Prahalad gave business the language of core competencies. I taught in the mini-MBA. I won the firm’s knowledge competition, on collaboration complexity of all things, the contest being one more way the firm pushed everyone to radiate their knowledge into the practice. I loved the variety, and I was good because of it. And when the review asked what is your program, the honest answer was that I did not have much of one. I was a generalist in a lexicon built for spikes. So I left.

The language was not describing my career. It was deciding it.

Up or out. Advance on schedule or be counseled to leave, the humane-sounding twin. It was harsh, and it built a hamster wheel: when I was there the average tenure was about 2.5 years, and twenty years later it is still roughly 2.7. The wheel spins at the same speed today. That is not an era. That is the design.

Shares and one firm. Even the money spoke the language. Partners held shares in the profit pool of a single global partnership, one firm, no office P&L fiefdoms, which is why any consultant anywhere would answer any consultant’s call. Bower sold his own shares back at book value on the way out. The compensation vocabulary said stewardship, and for a long time the behavior matched.

The Field Guide: The McKinsey Terms

The entries above are the terms with my stories attached. But the scale is the point, because this is what a complete language looks like. Here is the fuller field guide, and it is nowhere near exhaustive. These are simply the terms one alum still carries, every one of them alive in daily use during my five years. Read the sheer mass of it and then ask how much of your organization’s working vocabulary was chosen on purpose.

The Work

Problem statement. The question, written and agreed before any work begins.

Hypotheses. Answers proposed before evidence, then attacked.

Hypothesis tree. The problem disaggregated into branches until every branch is testable.

MECE. Mutually exclusive, collectively exhaustive: the full solution space, no overlap.

Analyses. Built to prove or disprove a hypothesis, never to explore.

Storyboard. Map the argument before building a single page.

Ghost deck. The storyboard as empty slides, titles first, evidence later.

Action titles. Every slide headline is a claim, so the deck reads as an argument.

So what?. Analysis converted to implication, on demand.

Answer first. Conclusion leads, support follows.

Day one answer. Your best hypothesis before the comfort of research.

Synthesize. Many analyses in, one meaning out.

80/20. The vital few over the trivial many, used as a verb.

Elevator test. If the answer takes more than thirty seconds, it is not the answer yet.

The Engagement

The Firm. Never the company.

Practice. Never a business.

Engagement. Never a job.

The study. The work itself, spoken like scholarship.

Client. Never a customer.

Client impact. The unit of worth. Not deliverables, impact.

Counterpart. Your mirror on the client side, developed as you go.

Client hands. The craft of handling a client, and real praise when earned: she has great client hands.

Client counsel. The Bower posture: trusted counsel to leadership, not a vendor.

CST. Client service team: the enduring team around a client, across engagements.

Top team. The client’s executive team.

On the beach. Between engagements, and slightly nervous about it.

The Team

EM. Engagement manager: the working leader of the study, and your daily teacher.

DGL. Development Growth Leader: the named owner of your growth.

Followership. The evaluated other half of leadership.

Inspirational leader. The bar the firm set for leading: teams should follow you out of inspiration, and your SAR asked whether they did.

Mentorship. Apprenticeship, with named roles so it actually happens.

Feedback is a gift. Said before the hard conversation, and meant.

Team norms. Every new team writes its own working agreements at kickoff.

PS session. Problem solving session: a meeting type so central it earned its own name.

The Career

Your program. Your spike: your CSTs, your expertise, your trajectory, owned by you.

Spikey. The highest compliment a profile could earn: exceptional at something specific.

Leverage. Multiply yourself: through a followership, the knowledge centers, the client team.

Pre-syndication. Alignment built one conversation at a time, before the meeting.

Up or out. Advance on the clock or leave.

Counseled to leave. The humane twin: a managed, supported exit.

Meritocracy. The best idea outranks the rank.

Distinctive. The top of the ladder, and the word everyone was chasing.

Very strong. One rung down. Still applause.

Strong. Solid and respected, and not enough forever.

Meets. The quiet middle of the scale.

Issues. The rating that started a clock. Counseling out began here.

Professional development. Growth run as a named process with a whole team behind it: PD reviews, PD days, staffing, your development treated like client work.

SAR. Semi-Annual Review: your DGL gathers feedback from everyone you worked with, twice a year.

Calibrate. Raters align their scores side by side, so distinctive means the same thing in every mouth.

The Firm

Serve clients, build leaders. The dual mission, compact enough to filter decisions.

Obligation to dissent. Silence is the violation.

One firm. A single global partnership. No fiefdoms, no office P&Ls to defend.

Radiate. What you learned on one study was never yours to keep. The standing instruction: radiate your knowledge.

Shares. The profit pool, held as stewards of the one firm.

Values day. One day a year, the whole firm stops to debate what it believes.

Colleagues. Never employees.

Dozens of terms, and this is only what one alum remembers. Each one installs a way of thinking, and the chain runs from there. That is not jargon. Jargon names things. This is a lexicon, and a lexicon shapes how people see.

The Loop: When the Language Is the Review

Here is the detail that separates McKinsey from every company with values on a wall. The lexicon showed up twice: in the daily work, and then again in the reviews, which naturally had their own name: PD, professional development, and not just a name, a whole team, people whose entire job was running consultants’ growth and staffing the way the firm ran client work. Most companies leave development to whatever time is left over. McKinsey gave it a name and a headcount. Do you have a followership? What is your program? The firm evaluated people in the culture’s own vocabulary.

The machinery had its own vocabulary all the way down. Your SAR, the Semi-Annual Review, gathered feedback from everyone you had worked with and scored you on three dimensions: Client Leadership, your impact, Thought Leadership, and People Leadership. And the score came back in a word from the house ladder: distinctive at the top, then very strong, strong, meets, and the quiet one that started a clock, issues. Even the bad news had a house term, sitting gently on top of a countdown. And the loop started before anyone was hired. I ran Tuck recruiting and was part of recruiting for all five of my years, interviewing hundreds of candidates against the firm’s dimensions, and after every pair of interviews came another term: calibrate. We would sit down and align our scores, dimension by dimension, so that a hard grader and a generous one meant the same thing by the same word. The firm did not just choose its language. It tuned it, rater by rater, year after year. It still does: in 2025, McKinsey renamed its four assessment dimensions to Leadership, Connection, Drive, and Growth. Ninety years in, someone is still gardening the words.

Language shaped the thinking, the thinking drove the behavior, and the behavior was measured in the same words that shaped it. No company on earth asks in a performance review whether you sufficiently lived “Integrity.” McKinsey asked about your followership with a straight face, and everyone knew exactly what was meant, because the word had been doing work in every team room for decades. That is what a commitment does that a value cannot: precise enough to be lived, precise enough to be measured.

Auditing the language your organization actually runs on, and building the lexicon it needs, is the work I do with CEOs and leadership teams. See how Joe works with clients or email him directly at joe@stratechi.com.

The One Import: A Language for People

For a firm that generated its own vocabulary for everything, McKinsey embraced exactly one external language in my five years: Myers-Briggs. And I lived the reason why on my first project in the Seattle office. My EM wanted me to take him through how I would approach the analysis, and I gave him the honest answer: I do not know, I am just going to start building the model.

Ahh, you must be an N. I am an S, and I like details. Let’s touch base every day on how you are coming along, so I get the details as you develop them.

Look at what happened in those three sentences. A wiring difference got named. Nobody was wrong. And a working arrangement got designed on the spot, thirty seconds from friction to system. In most companies that exchange is a performance problem, a frustrated manager, and an analyst who learns to fake project plans. At McKinsey it was just another conversation, because the firm had imported the one language that gave teams words for their own friction. The firm that built a language for problems was smart enough to import one for people.

The Honest Bill

So did it work? Completely. The language built the strongest professional culture in business, a firm that turns twenty-six-year-olds into trusted counselors to CEOs and stamps its alumni into leadership seats across the world economy. I admired it then and I admire it now, especially the problem solving culture, the audacity of taking the scientific method and the law firm and fusing them into a way of being.

And here is the honest bill, because I did not like the totality of the culture I found. Strip away the admiration and what remains is a highly tuned machine built to extract the most from smart, ambitious, often insecure overachievers. Remember leverage, the word that taught everyone to multiply themselves? Point that word at people and you get the other McKinsey. The machine converted rocket-ship hunger into hundred-plus-hour weeks and total dedication, and the same lexicon that installed the rigor ran the extraction. In places, my office among them, what it produced was cultish, transactional, and a bit toxic.

The economics underneath were pyramid-shaped, and I will say what I eventually concluded: it was a bit of a pyramid scheme. Directors at the top made millions. The analysts and associates actually doing the work made a fraction of that, and at one point I ran the numbers on my own projects. The team doing the work was earning roughly 4 to 5 percent of what the client was paying for the study. A 95 percent gross margin on human capital. Seen from that angle, up or out was not just a performance philosophy. It was the pyramid’s maintenance system, keeping the base young, cheap, hungry, and constantly replaced. The hamster wheel was never a bug in the meritocracy. It was the meritocracy, running exactly as worded, and the unchanged 2.5-year tenure two decades later says the machine still runs as designed.

The same language that built the firm leveraged its people, at a 95 percent gross margin on human capital. The vocabulary is theirs. The math was mine.

I am not settling a score. I am reporting a mechanism. Because if language can build the best professional culture on earth and an extraction machine simultaneously, with the same words, then the mechanism itself is neutral, and everything depends on the intent of the people choosing the words. That is the most important sentence on this page for any leader reading it.

The Other Direction: A Language Factory

One more thing hides in plain sight, and it took me years after leaving to see it. The firm’s internal language built its own culture. But the product we sold was the same craft pointed outward. Our job, engagement after engagement, was to create frameworks for companies: their true north, their vision, their strategy, their operating model. And how we defined the problem statement and disaggregated the levers and hypotheses did not just describe the client’s business. Sometimes it became the actual operating model of a function or a team. The framework did not explain the company. The company reorganized itself around the framework. Language, becoming thinking, becoming behavior, becoming the way things work around here, on the client’s side of the table this time.

McKinsey was a language factory running in both directions, and almost nobody inside it would describe it that way. I spent five years learning that craft on clients’ strategies and operating models. Culture by Commitment is that same craft with a different client: the culture itself.

The Lesson for Leaders

The lesson is simple. McKinsey proves what deliberate language can build: a shared way of thinking, at scale, that survives decades of turnover. If you want a strong culture, be intentional about your language. Choose the words, define them, use them in the daily work, and use them in your reviews, because the chain McKinsey proves runs in one direction:

Language Thinking Behavior Culture Performance

And be just as intentional about what you point it at. The same intentionality that built McKinsey’s rigor also ran the hundred-hour weeks and the 95 percent margin. The language will build whatever culture you design it to build. That part is on you.

And take the deepest lesson of all, the one this entire page has been circling. McKinsey has been intentional about its language for more than ninety years, and it always will be, because at this point no partner and no director can change it. People cycle through every two or three years. Leaders retire. Bower himself is gone. The lexicon persists, and the lexicon runs the firm. That is the final proof of everything on this page:

The language is the culture.

Read next: Southwest Airlines Culture, the other definitive proof that language builds culture, and the case study in what happens when the living stops. Or see the full methodology this page has been pointing at all along: Culture by Commitment.

Work with Joe

What language is your organization running on?

Every organization is already running on a lexicon. Almost none chose it. McKinsey proved what deliberately chosen language can build, and what it can cost when the intent behind it goes unexamined. I help CEOs and leader​ship teams do what Bower did, with better intent: choose the words, install the thinking, and build a culture that grows people instead of spending them.

Bower chose his words in 1933 and they are still running the firm. Yours can run yours.

See How Joe Works with Clients

Or email Joe directly at joe@stratechi.com

And follow Joe on LinkedIn for new content and insights.

Joe Newsum: McKinsey alum, former CEO, COO, CFO, and CMO, and creator of Culture by Commitment, working directly with Fortune 500 CEOs and executive teams to build cultures that hold.

Enjoying the ideas? Stay connected.
Get Joe’s latest thinking on strategy, leadership, and culture in your inbox. No noise, just the good stuff.

Frequently Asked Questions

What is McKinsey’s culture actually like?

McKinsey’s culture is a language-built culture: a deliberately chosen lexicon, from the obligation to dissent to your program to up or out, that shapes how consultants think, work, and are evaluated. It produces extraordinary problem solving rigor, fast development, and deep professional standards, alongside very long hours, constant evaluation, and an average tenure of roughly 2.5 to 3 years. Both sides come from the same mechanism: precise shared language, driven into daily work and reviews, at full intensity.

What is McKinsey’s obligation to dissent?

The obligation to dissent is a McKinsey core value stating that every consultant, regardless of seniority, has a duty, not merely a right, to voice disagreement when they believe the team or client is wrong. Framing dissent as an obligation makes silence the violation, and the term is actively invoked in meetings: a leader can turn to the most junior person in the room and ask for their dissent by name. It is one of the clearest examples of a value written as a usable commitment rather than an aspiration.

What does up or out mean at McKinsey?

Up or out is McKinsey’s promotion model: consultants are expected to advance to the next level on a roughly two-to-three-year clock, and those who do not are counseled to leave, the firm’s term for a managed, supported exit. It keeps performance standards high and creates constant turnover; combined with demanding hours, it produces average tenures of roughly 2.5 to 3 years, a figure that has stayed essentially unchanged for decades.

Why is the average tenure at McKinsey so short?

Average tenure at McKinsey is roughly 2.5 to 3 years because the model is built for throughput: up-or-out promotion clocks, very heavy workloads, sponsored MBA departures, and exceptional exit opportunities all pull people out on a short cycle. The firm develops people intensely and then most of them leave, which is partly by design: the alumni network in senior roles across the world economy is itself a strategic asset for the firm.

What language and terms does McKinsey use?

McKinsey runs on a rich internal lexicon. Working terms include the problem statement, hypotheses, hypothesis trees, MECE, so what, answer first, day one answer, synthesize, storyboarding, leverage, and pre-syndication. Character and career terms include the obligation to dissent, meritocracy, followership, mentorship, your program, CSTs (client service teams), DGL (Development Growth Leader), professional development (PD), SAR (Semi-Annual Review), calibration, up or out, counseled to leave, and one firm. The vocabulary is deliberate: each term installs a specific way of thinking, and the terms appear in performance reviews as well as daily work.

What can leaders learn from McKinsey’s culture?

Four things. Choose your organization’s language deliberately, the way Marvin Bower did in 1933, rather than letting a lexicon accumulate by accident. Write cultural non-negotiables as invocable obligations and commitments, not wall values. Close the loop by evaluating people in the culture’s own vocabulary, so the culture you talk is the culture you grade. And examine intent: the same language mechanism that builds rigor and standards can run extraction and burnout, so what you load into it matters as much as how well it runs.