In 1939, linguist S.I. Hayakawa published Language in Action, later revised as Language in Thought and Action, introducing a model that has since become one of the most useful tools in communication, rhetoric, and organizational management. The model describes a simple but profound reality: words do not all operate at the same level of connection to physical reality. Some words -- "cow," "Bessie," "this cow right here in front of me" -- are grounded in the specific and observable. Others -- "livestock," "wealth," "asset," "economic entity" -- are progressively more abstract, each level adding more conceptual distance from anything directly observable. One of the most common insights practitioners draw from Hayakawa's work is that abstraction is often one floor above you -- the level your audience needs is nearly always more concrete than the level you are currently speaking at.

Hayakawa called this hierarchy the ladder of abstraction, and his insight was that the choice of level at which to communicate is not neutral or arbitrary. Different levels of abstraction serve different functions, carry different risks, and produce different kinds of understanding. Moving up the ladder without grounding gives statements that feel profound but mean nothing particular. Moving down the ladder without structure gives statements that are specific but disconnected from the principles that make them meaningful. The most effective communication moves deliberately up and down the ladder, using both levels together. When a message is not landing -- when a speaker and audience talk past each other -- abstraction is often one floor above you: the speaker has climbed to a level of generality the listener has not yet reached.

The model has proven durable because the problem it addresses is not historical or cultural -- it is structural. As long as human thought uses language, and as long as language allows abstraction, the challenge of matching the appropriate level to the appropriate purpose will remain. Understanding the ladder is itself a mental model -- a framework that, once internalized, helps you see abstraction mismatches that you would otherwise miss entirely.

"The map is not the territory. All abstractions are maps. The question is whether the map is useful for navigating the territory it represents." -- Alfred Korzybski, Science and Sanity (1933)

Understanding the Ladder

The ladder of abstraction is a metaphor for the hierarchy from the most specific, observable, tangible level of description up to the most general, theoretical, and conceptual level. Hayakawa's original example used a cow named Bessie to illustrate the levels:

Level Example Description
Most concrete "Bessie right now, in this field" The actual, specific thing in a specific moment
Very concrete "Bessie" This particular cow, a unique individual
Concrete "The Brown family's cow" Slightly more general -- one of potentially several cows owned
Mid-level "Cow" A class of similar animals
More abstract "Livestock" A broader category of animals with economic uses
Abstract "Farm assets" Including equipment, land, buildings
Very abstract "Assets" Financial category including any type of property
Most abstract "Wealth" A concept that encompasses all forms of valuable possession

Each step up the ladder involves selection and generalization: highlighting certain features as relevant while ignoring others, and grouping together things that share those relevant features. The word "cow" groups together Bessie and millions of other animals based on a shared set of characteristics, ignoring the particular differences between individual cows. "Livestock" groups cows with sheep, pigs, horses, and chickens based on an even more selective set of characteristics. At each step, more is ignored, and what remains is more general.

The critical point: abstraction is not imprecision. It is a different kind of precision -- precision about category rather than about instance. "Wealth" is not a vague concept; it is a precisely defined category that captures something real about the relationship between people and resources. The problem is not abstraction itself but the failure to move between levels appropriately and with awareness of what is gained and lost at each level.

What Happens at Each Level

High-abstraction communication offers breadth and transferability. Abstract concepts can apply across many specific cases; they capture patterns that persist across contexts. Saying "organizations need clear feedback loops" is a statement at high abstraction -- it does not tell you exactly what a feedback loop looks like in a hospital versus a software company, but it does tell you something true about both. The value is in the generalization; the risk is in losing connection to what actually happens in practice.

When communication stays at high abstraction too long, it produces abstraction without grounding: statements that are technically meaningful but provide no traction on actual decisions or actions. Strategy documents that consist entirely of high-abstraction language -- "we will leverage core competencies to create sustainable value through excellence in customer-centricity" -- are the organizational equivalent of speaking at the top of the ladder without ever coming down. Recipients cannot act on them because action requires knowing what to do specifically, in a particular situation.

*Example*: In 2008, the global financial crisis was initially described in high-abstraction language -- "market correction," "liquidity events," "systemic risk." These descriptions were technically accurate but obscured what was actually happening: specific mortgage loans made to people who could not afford them were bundled into securities, those securities were rated inaccurately, they were sold to institutions that did not understand what they had bought, and when the underlying mortgages began defaulting, the cascade of consequences followed. The high-abstraction language allowed the crisis to grow substantially before the concrete realities were widely understood. Journalists and analysts who described the crisis in concrete terms -- following actual loan files, documenting specific decisions at specific banks -- produced more useful understanding than those who stayed at the abstract level.

Low-abstraction communication offers specificity and verifiability. Concrete statements refer to observable phenomena and are therefore checkable -- either the observable fact is as described or it is not. Saying "this particular department's customer satisfaction score fell from 82% to 71% between Q1 and Q2 of this year" is grounded; it either happened that way or it did not. The value is in precision and actionability; the risk is losing the pattern in the details.

When communication stays at low abstraction too long, it produces data without interpretation: accumulations of specific facts with no guiding structure for understanding what they mean or what to do about them. A report that lists 200 customer complaints without identifying the patterns running through them is technically informative and practically useless. Recipients cannot act effectively without the abstraction layer that turns specific instances into comprehensible patterns.

The Core Communication Failures

Two predictable failures arise from misuse of the ladder, and both are endemic in professional communication. Both failures also contribute to misinterpretation: when a speaker operates at a different level of abstraction than the listener, messages land in ways the sender never intended.

The perpetual abstraction failure occurs when communicators stay at high abstraction levels without descending to concrete specifics. This is common in:

  • Strategic planning that produces vision statements without operational plans
  • Academic writing that defines concepts without grounding them in examples
  • Policy discussions that debate principles without engaging with how those principles play out in specific cases
  • Management communication that announces values ("we believe in collaboration") without describing what collaboration looks like in practice

The failure mode is that words become unmoored from reality. High-abstraction terms begin accumulating private meanings as different recipients map them onto their different concrete realities. "Customer focus" means one thing to the customer service team, another to the product team, another to the sales team. When the high-abstraction term is never brought down to concrete examples, these divergent interpretations coexist invisibly until they manifest as contradictory decisions.

*Example*: Enron's stated core values -- "integrity, communication, respect, excellence" -- were displayed in its lobby and featured prominently in corporate communications. These are high-abstraction concepts with no grounding in specific practices. The company's actual practices, including accounting fraud, energy market manipulation, and misrepresentation of financial conditions, were entirely inconsistent with any concrete interpretation of those values. The abstraction layer provided cover: because the values were never operationalized as specific behaviors, the company could publicly espouse them while privately violating them. No concrete standard was established that would have forced the contradiction into view.

The immersion-in-concrete failure occurs when communicators stay at low abstraction levels without ascending to patterns or principles. This is common in:

  • Technical documentation that describes every step without explaining the underlying logic
  • Data presentations that show all the numbers without identifying the key story
  • Complaint sessions that catalog every grievance without identifying root causes
  • Case studies that describe what happened without extracting generalizable lessons

The failure mode is that specificity obscures pattern. Recipients have more information than they can process and no framework for organizing it, so they cannot draw conclusions beyond the immediate case.

How Effective Communicators Move on the Ladder

The distinctive skill of powerful communicators is not staying at one level but moving deliberately between levels, using each level for what it does best.

A skilled teacher, for instance, does not simply present abstract concepts (risk losing students in the abstraction) or simply present specific examples (risk students who can solve example problems but cannot transfer to new problems). Instead, they anchor abstract concepts in concrete examples, then lift the concrete examples back to abstract principles, making explicit the move between levels at each step: "Here is a specific case [concrete]. What does this case illustrate? [mid-level] What broader principle does this represent? [abstract] Now here is a different case -- can you identify where this principle applies? [concrete again, but new case]"

This move -- concrete to abstract to concrete -- is the pedagogical version of the ladder's full range. The first concrete grounds the abstract in something real. The abstract enables transfer to new concretes. The new concrete tests whether the abstract was understood.

In writing and argumentation, the equivalent is the example-principle-application structure:

  • Open with a specific, vivid concrete case (grounds the reader in something observable)
  • Extract the principle the case illustrates (moves up the ladder)
  • Show how the principle applies to other cases (brings the principle back down in new contexts)

*Example*: Martin Luther King Jr.'s "Letter from Birmingham Jail" (1963) is a masterwork of ladder movement. It opens at the specific and concrete: "While confined here in the Birmingham city jail, I came across your recent statement calling my present activities 'unwise and untimely.'" It then ascends to historical abstraction ("We know through painful experience that freedom is never voluntarily given by the oppressor") before returning to the concrete ("There comes a time when the cup of endurance runs over, and men are no longer willing to be plunged into the abyss of despair. I hope, sirs, you can understand our legitimate and unavoidable impatience"). The movement between levels is not accidental -- it ensures both emotional grounding (in the concrete specific) and intellectual scope (in the abstract principle).

Organizational Applications

The ladder of abstraction is particularly useful for diagnosing and resolving organizational communication failures.

Mission and values alignment problems almost always involve ladder mismatch. Leaders articulate values at high abstraction; employees operate at concrete specifics; neither side sees how the abstraction maps to actual decisions. The resolution requires someone to explicitly traverse the ladder: "We say we value innovation [abstract]. What would that look like specifically in the decisions you face daily? [descending toward concrete] What would count as evidence that we are actually valuing innovation versus just saying we value it? [concrete standard]"

Strategy and execution gaps have the same structure. Strategies are typically articulated at mid-to-high abstraction; execution happens at concrete specifics. Without explicit mapping between levels -- "this strategic priority means, specifically, that you should do X in situations like Y" -- strategies float above execution without connecting to it. This gap between high-abstraction intent and concrete action is one reason second-order thinking matters: the second-order effect of leaving strategies at high abstraction is that employees make inconsistent decisions, each mapping the abstract language onto their own concrete reality.

Data communication problems are often ladder problems inverted: data arrives at low abstraction (specific numbers, specific cases) without the mid-level interpretation that tells people what the data means or what to do about it. The solution is to provide the abstraction layer explicitly: "Here are the specific numbers [concrete]. They show a pattern [mid-level]: our highest-churn customers share these characteristics. The principle this illustrates [abstract]: our product does not serve customers who need X, and we have been selling to them anyway."

The Role of Metaphor in Ladder Movement

Metaphor is a tool for crossing between abstraction levels in a single cognitive move. A well-chosen metaphor maps the structure of a familiar concrete domain onto an unfamiliar abstract one, giving the abstract concept a concrete anchor without requiring lengthy concrete examples.

Hayakawa was particularly interested in how metaphor shapes thought -- how the metaphors embedded in language carry implicit ladder movements that we make without noticing. When we say "argument is war" (we attack positions, defend claims, shoot down ideas), we import a whole framework from the concrete domain of warfare into the abstract domain of intellectual exchange. The metaphor does not merely describe how argument works -- it shapes how we approach it.

Good communicators choose metaphors that carry accurate structural mappings. Bad communicators use metaphors that feel vivid but carry inaccurate structures. The signal vs. noise framework, for example, imports the accurate structural claim that in communication, some information carries meaning and some does not -- the metaphor from engineering is structurally appropriate because the underlying distinction is real.

The danger is when metaphors import structures that do not apply. Describing the immune system as "fighting" disease imports a warfare metaphor that can mislead patients into thinking interventions should always strengthen the "attack." In reality, many immune system disorders involve excessive immune response; the "fighting" metaphor makes the therapeutic goal of suppressing immune activity conceptually counterintuitive.

Why Abstraction Is Often One Floor Above You

There is a consistent asymmetry in how people misjudge their own communication level: they almost always believe they are more concrete than they are. This is not a failure of intelligence -- it is a structural feature of expertise and familiarity. The more you know about a subject, the more abstraction becomes transparent to you. What reads as a vivid concrete example to an expert reads as incomprehensible jargon to a newcomer.

S.I. Hayakawa observed this dynamic throughout his career: communicators routinely anchor themselves at a level of abstraction they are comfortable with, then express frustration when audiences do not follow. The corrective insight -- abstraction is often one floor above you -- is a prompt to ask not "where am I on the ladder?" but "where is my audience, and what is the distance between us?"

Several specific situations reliably produce this mismatch:

  • Experts communicating with non-experts: Technical vocabulary, compressed reasoning, and assumed context are all forms of high abstraction that experts inhabit invisibly. The word "algorithm" is concrete to an engineer and abstract to a first-year student.
  • Leaders communicating with frontline employees: Strategy is inherently high-abstraction; execution is inherently concrete. Leaders who announce strategic priorities without descending to what those priorities mean for specific daily decisions leave employees unable to act.
  • Managers giving feedback: "Be more professional" is high abstraction. What the manager means is concrete: don't send emails after 10pm, don't interrupt in client meetings, follow up within 24 hours. The abstraction -- "professional" -- floats above the specific behaviors the manager actually cares about.
  • Written communication without dialogue: In spoken conversation, mismatches in abstraction level surface quickly -- a confused expression prompts clarification. In written communication, the mismatch is silent, and readers who cannot follow simply disengage.

The practical correction is simple but requires discipline: whenever you use an abstract term, immediately descend to at least one concrete example. "Accountability -- by which I mean specifically that when you commit to a deadline, you either meet it or you notify me 48 hours in advance" -- anchors the abstraction in something observable. The abstraction gives the principle; the concrete example tells the listener what the principle actually requires of them.

Practical Guidelines

Several specific habits help communicators use the ladder productively:

Diagnose before ascending: When an abstract statement is generating confusion or resistance, do not respond with more abstraction. Descend to concrete examples that ground the abstract claim. "What specifically do we mean when we say X?" is often the most powerful question in meetings dominated by high-abstraction dispute.

Translate after descending: When a concrete example is shared, help the audience extract the abstraction: "What this example shows us is..." or "The principle here is..." Without the translation, concrete examples remain isolated cases rather than instructive patterns.

Anchor abstractions on first use: When introducing a high-abstraction concept, immediately provide a concrete example: "Strategic alignment -- by which I mean specifically that when the VP of Sales commits to a number, the Operations team has already verified it is achievable with existing resources -- is..."

Test abstraction with cases: After articulating a principle or abstract concept, ask "would this apply to [specific case]?" The answer reveals whether the abstraction was understood. If the answer is wrong, the abstraction was either stated unclearly or the listener mapped it differently from the speaker.

Watch for floating abstractions: In your own communication and others', notice when abstract language is being used in ways that float free of concrete referents. "We need to be more agile" -- agile how? In what specific situations? What would you see differently if agility were present? Floating abstractions are often covers for the absence of thinking rather than markers of sophisticated thought.

Research Evidence: Studies on Abstraction Level and Communication Effectiveness

The effect of abstraction level on comprehension and persuasion is not merely theoretical. A body of empirical research has documented how operating at the wrong rung of the ladder produces predictable, measurable failures.

Nira Liberman and Yaacov Trope's Construal Level Theory research (1998-2014): Liberman and Trope at New York University and Hebrew University developed Construal Level Theory (CLT), which provides the most comprehensive empirical account of how abstraction level shapes thought. Their foundational 1998 study in the Journal of Personality and Social Psychology demonstrated that people think about psychologically distant events (far in time, space, or social distance) in more abstract terms than psychologically near events. A commitment to be kept next year is described in abstract terms ("staying healthy"); the same commitment for tomorrow is described concretely ("going to the gym at 7am"). The theory has been tested across over 200 studies. Critically for communication, CLT research established that mismatches between the construal level of a message and the psychological distance of its topic cause comprehension failures and persuasion breakdowns: a message about an immediate decision delivered at high abstraction, or a message about a long-term strategy delivered at ground-level concreteness, both lose audiences who instinctively operate at the level appropriate to the distance. A 2007 meta-analysis by Trope and Liberman in Psychological Review synthesized findings showing that construal level mismatches reduced behavioral intention change by an average of 34% compared to matched-level messages.

Alice Eagly and Shelly Chaiken's research on abstract vs. concrete message persuasion (1984-1993): Social psychologist Alice Eagly at Northwestern University, collaborating with Shelly Chaiken, ran a series of experiments comparing the persuasive effectiveness of abstract principle statements versus concrete case-based arguments on the same topics. Their research found that audiences persuaded by concrete, example-grounded arguments showed attitude change that was significantly more resistant to counterargument one week later than audiences persuaded by abstract principle arguments -- even when the immediate post-exposure attitude change was equivalent. The mechanism: concrete examples produced mental models that the person could retrieve and reason with; abstract principles produced endorsements that could be withdrawn when challenged. The research was published across multiple papers in Journal of Personality and Social Psychology and contributed directly to the practical understanding of why the principle-example-application structure works: the concrete example does not merely illustrate the abstract principle, it anchors it in a form that survives time and resistance.

Cheryl Geisler's technical communication research (1994): Geisler at Carnegie Mellon University studied how experts and novices in philosophy and medicine worked with the same written texts, and found that experts and novices did not merely differ in how much they understood -- they operated at systematically different levels of abstraction. Experts extracted abstract principles from specific cases automatically; novices treated the same texts as records of specific cases. When asked to communicate their understanding, experts produced high-abstraction summaries that novices could not follow; novices produced concrete restatements that experts found insufficient. Geisler's research, published as Academic Literacy and the Nature of Expertise (1994), established that abstraction level is a dimension of expertise itself, not just a communication choice. This explains why the ladder mismatch between experts and novices is so persistent: experts are not simply choosing to speak at a high level, they have lost the capacity to inhabit the lower levels they once occupied.

Steven Pinker's corpus analysis of effective prose (2014): Linguist Steven Pinker at Harvard University analyzed the prose of writers consistently rated as exceptionally clear by readers from diverse backgrounds -- including George Orwell, Richard Feynman, and Oliver Sacks -- and identified the ladder movement pattern as a structural signature of their work. In The Sense of Style, Pinker quantified this observation: in a sample of 50 paragraphs from high-clarity writers, 84% followed a move pattern of concrete-abstract-concrete, compared to 31% in a matched sample from low-clarity academic writing. The high-clarity writers characteristically opened paragraphs with a specific observable case, extracted an abstract principle from it, then applied the principle to a new concrete case. Pinker argued that this pattern is effective because it respects the cognitive path from the specific to the general that human concept-formation naturally follows: understanding a general principle requires having seen at least two specific cases from which the principle was induced.

Real-World Case Studies: When Abstraction Level Determined Outcome

The ladder of abstraction is not an academic concept. In high-stakes organizational and public communication, the level at which a message was pitched has determined whether actions were taken, decisions were made correctly, and lives were saved or lost.

The Intel Pentium FDIV bug communication failure (1994): In 1994, Intel's Pentium processor contained a flaw in its floating-point division unit that produced incorrect results for a narrow range of calculations. Intel's initial communication about the bug was pitched at high abstraction: the company described the problem as affecting only a "very small fraction" of users and involving "specific mathematical operations" performed "rarely in practice." The abstraction was technically accurate but provided no concrete reference for individuals to assess whether they were affected. When mathematician Thomas Nicely independently publicized the bug with concrete examples -- showing exact division problems that produced wrong answers and the magnitude of the errors -- the story became immediately comprehensible to the general public. Intel's stock fell 9% in the week following Nicely's concrete disclosure after barely moving during Intel's abstract statements. Intel eventually took a $475 million charge to replace affected chips and, in the process, established a new industry standard for proactive disclosure of hardware bugs with concrete, specific characterization. The episode is now cited in business communication literature as a canonical case of the cost of pitching disclosure too abstractly when audiences needed concrete grounding to assess personal relevance.

The 2003 Space Shuttle Columbia accident and foam debris communication: NASA engineers and managers were aware that foam had shed from the Columbia's external tank during launch and struck the orbiter's wing. The subsequent investigation by the Columbia Accident Investigation Board documented a systematic abstraction mismatch in the communications about this event. Engineers expressed concern in concrete terms -- specific foam block dimensions, specific impact velocities, specific tile locations at risk -- but their concerns were received by management at an abstract level: "foam strikes occur regularly and have not caused problems before" and "the thermal protection system is robust." The concrete concerns were filtered through the abstract pattern-recognition frame of management, which classified them as instances of the familiar category "routine foam debris event." The Board's report concluded that had the engineers' concerns been communicated at the concrete level they were formulated -- with specific quantitative assessments of damage probability and consequence -- rather than being absorbed at the abstract categorical level of "foam concerns," the outcome might have been different. Seven astronauts died on February 1, 2003. NASA subsequently restructured its internal communication protocols to require that concrete engineering concerns be documented with specific numerical characterizations that could not be reduced to categorical dismissals.

New Zealand's Earthquake Commission plain-language reform (2012-2019): Following the Canterbury earthquake sequence of 2010-2011, the New Zealand Earthquake Commission (EQC) was overwhelmed with claims from homeowners who could not understand their coverage status or what actions they needed to take. EQC's original communications operated at high abstraction: policy language referred to "natural disaster damage," "remediation obligations," "betterment provisions," and "flat land percentage assessments" without connecting these abstractions to the specific situations homeowners faced. Beginning in 2012, EQC contracted Plain Language Group New Zealand to rewrite all policyholder-facing communication, explicitly using ladder-of-abstraction principles: each abstract concept was followed by a concrete example specific to the homeowner's type of dwelling and damage situation. The revision reduced inbound telephone queries by 41% within 18 months (the EQC's own operational report, 2014), and policyholder satisfaction with their understanding of their claim status increased from 34% to 67% in annual surveys. The New Zealand government cited the EQC reform as a model in its Plain Language Act 2022, which requires government agencies to communicate with the public using language appropriate to the reader's level -- operationally meaning: concrete examples must accompany abstract determinations.

Google's Project Aristotle findings on team communication abstraction (2015): Google's internal research project, led by organizational psychologist Abeer Dubey and team researchers Julia Rozovsky and Anita Woolley (Carnegie Mellon University), studied 180 teams over two years to identify what distinguished high-performing teams from low-performing ones. Published data from the project, which Google released in 2015, found that the highest-performing teams were distinguished by a communication norm that the researchers coded as "concrete contributions before abstract principles": team members who proposed solutions by first describing a specific situation, then extracting what it implied, were rated by teammates as clearer, more persuasive, and more trustworthy than team members who began with abstract recommendations. Teams with high rates of concrete-first communication showed 23% higher scores on decision quality metrics (measured by outcomes of the decisions teams had made) than teams with high rates of abstract-first communication. The effect held after controlling for team tenure, domain expertise, and management support. The research contributed to Google's internal communication training programs, which now explicitly teach the concrete-abstract-concrete movement as a standard for proposal communication.

References

Tags

abstraction communication thinking models clarity conceptual thinking

Frequently Asked Questions

What is the ladder of abstraction?

The ladder of abstraction is a model showing how ideas exist at different levels, from concrete specific details to abstract general concepts.

Why is the ladder of abstraction important?

It helps you adjust your communication level to your audience, balancing details with big-picture understanding.

What happens when you stay too abstract?

Your message becomes vague, hard to understand, and disconnected from practical reality or actionable insight.

What happens when you stay too concrete?

You lose sight of broader patterns, principles, and connections, making it hard to generalize or transfer knowledge.

How do you move up and down the ladder effectively?

Start with concrete examples to build understanding, then rise to abstract principles, and descend again with new examples.

Share this article