intrapreneurship

Metaphors We Live By

Also known as:

Conceptual metaphors (time is money, love is journey, argument is war) shape how we think and act; changing metaphors opens new possibility. Commons experiment with alternative metaphors for relationship, work, and change.

Conceptual metaphors—the hidden frames we use to think about time, work, relationships, and change—shape what we notice, what seems possible, and what we do, so deliberately shifting metaphors opens new possibility spaces.

[!NOTE] Confidence Rating: ★★★ (Established) This pattern draws on Lakoff & Johnson’s Metaphors We Live By (1980) and subsequent cognitive linguistics research on how metaphor structures thought and action.

Section 1: Context

Intrapreneurs inside organizations, movements, and institutions often sense that the dominant language constrains their thinking before it constrains their action. A tech startup frames product adoption as “conquest”; a government agency thinks of citizens as “customers”; an activist coalition describes their work as “fighting the system.” These are not neutral descriptions—they are live metaphors that generate entirely different strategies, metrics, and relationships.

The system is fragmenting between the metaphors we inherited (inherited from industrial, military, and economic traditions) and the metaphors we need (for regenerative, distributed, and adaptive work). When metaphors stay invisible and unexamined, they calcify into assumptions. Teams optimize for speed in a “time is money” frame without noticing they’re sacrificing depth. Organizations deploy “command and control” language in flatter structures, creating cognitive dissonance. Movements speak of “winning” while trying to build long-term culture change.

The intrapreneurial opening is that groups can deliberately experiment with alternative metaphors—and when they do, new behaviors, metrics, and relationships emerge without needing formal restructuring. A commons stewarding this pattern learns to surface hidden metaphors, test new ones, and harvest the competence that comes from conscious choice.

Section 2: Problem

The core conflict is Metaphors vs. By.

We do not choose our metaphors; we live by them. This is the tension.

Metaphors operate below conscious attention. “Time is money” does not feel like a metaphor—it feels like reality. We say “spend time,” “invest in relationships,” “budget our hours.” The metaphor has disappeared into language so completely that we forget it is a choice. The consequence: we optimize our commons for speed and scarcity (matching the metaphor’s logic) while remaining blind to what we are sacrificing—presence, emergence, depth.

On one side sits the Metaphor—the abstraction we inherit or unconsciously adopt. On the other side sits the By—the lived reality we create through acting as if that metaphor were true. When metaphors go unexamined, the By becomes invisible. We stop noticing that we are living by a choice; instead, we experience it as constraint.

This breaks three ways:

First, homogeneity of thought. A commons saturated in a single metaphor loses adaptive capacity. Everyone is asking “How do we win faster?” Nobody asks “What emerges if we tend this system?” The system becomes brittle.

Second, inherited toxicity. War metaphors bring competitive zero-sum logic into domains (collaboration, learning, healing) where they generate harm. Money metaphors bring scarcity logic into domains of abundance. The metaphor’s hidden values contaminate the work.

Third, missed possibility. If “love is a journey” opens different relational behaviors than “love is a container,” then changing the metaphor is not linguistic whimsy—it is strategic leverage. But we cannot access that leverage if we do not notice we are living by a metaphor at all.

Section 3: Solution

Therefore, a commons deliberately names the hidden metaphors shaping its work, experiments with alternative metaphors rooted in the system’s actual values, and harvests the new capacities and relationships that emerge.

The mechanism is simple but requires cultivation: when a group makes metaphors visible and fungible, they recover agency. They move from “time is money, so we must hustle” to “time is soil, so we must tend.” The shift is not semantic; it cascades.

Under “time is money,” a meeting that “wastes time” feels like a loss. You measure its success by outputs per hour. Under “time is soil,” a meeting that appears slow might be composting—breaking down assumptions, letting nutrients redistribute. You measure differently: has the ground become more alive?

This works because Lakoff & Johnson demonstrated that metaphor is not ornamental—it is structural. A metaphor maps the logic of one domain (source) onto another (target). “Argument is war” maps the logic of combat (victory, defeat, territory, weapons) onto discourse. It makes winning the argument feel like the point, rather than understanding together or creating new knowledge. Change the metaphor to “argument is dance” and the entire point shifts: you care about rhythm, responsiveness, the quality of the interaction itself.

In commons work, this shift dissolves false urgencies. “Organization is organism” invites care for health, resilience, and regeneration—not just throughput. “Change is emergence” (vs. “change is construction”) means you stop trying to engineer predetermined outcomes and start creating conditions for new capacities to self-organize.

The pattern works at the level of living systems because metaphors are how meaning propagates. When you change the root metaphor, you change what each actor notices, values, and does. Ownership emerges when people stop seeing themselves as “resources” (metaphor: organization is machine) and see themselves as “stewards” (metaphor: organization is living commons).

Section 4: Implementation

For corporate contexts: Name the metaphors governing your unit. Ask: “What metaphor are we living by for success? For work? For time? For people?” Likely answers: “winning market share,” “hitting targets,” “people as resources,” “time is money.” Make a list. Then, identify the costs these metaphors extract—what matters that they obscure? Burnout? Attrition? Short-term thinking? Design a counter-metaphor rooted in what you actually value: “We grow market presence through deep relationships” (vs. “winning”). “We create impact through sustainable pace” (vs. “targets”). Name the shift explicitly in your planning language. When someone says “we need to move fast,” respond: “Under what metaphor? If time is rhythm, not money, what tempo serves?” Insert the new metaphor into planning docs, retros, and strategy language.

For government contexts: Public service is drowning in “customer service” framing—borrowed from commerce. Experiment with “stewardship of the commons” or “trusteeship of the public good” as live metaphors. These reshape accountability (you serve the whole system, not just satisfaction scores) and time horizons (you think in generations). Have policy teams diagnose which metaphors currently govern: “beating targets,” “managing taxpayers,” “delivering services.” Then redesign language. A government program reframes from “managing homelessness” (metaphor: problem to solve) to “weaving belonging” (metaphor: relationship to restore). Measure differently. Create small working groups to prototype the new metaphor’s consequences before scaling.

For activist and movement contexts: Notice “fighting the system,” “winning,” “enemies.” These metaphors generate attrition and burnout. Experiment with alternatives: “weaving resilience,” “tending emergence,” “composting old patterns.” The metaphor “change is composting” invites different practices: you stay in place, break down what is broken, create conditions for what wants to grow—rather than “fighting” (which assumes you are separate and opposed). Have your coalition map the metaphors they are living by in one session. Notice which ones create vitality and which create exhaustion. Write the new metaphors into your strategy documents and use them in internal communication. Watch what shifts in your tactics and relationships.

For tech and product contexts: Products are drowning in conquest metaphors: “user acquisition,” “market penetration,” “domination,” “scaling.” Experiment with “cultivating gardens,” “tending ecosystems,” or “composing with communities.” These metaphors reshape product thinking. Under “growth is cultivation,” you care about soil health (user wellbeing, sustainable engagement, regenerative value). Your metrics change. You measure not “DAU” but “health of the user’s digital life with this product in it.” You ask: “Does using this product leave people more alive?” Prototype a product roadmap under the new metaphor. What features disappear? What emerge?

Across all contexts, the implementation sequence:

  1. Surface the hidden metaphors (workshop, list, name them openly).
  2. Diagnose which metaphors extract costs or limit possibility.
  3. Design alternatives rooted in your actual values.
  4. Embed the new metaphors in language, documents, and metrics.
  5. Watch what new behaviors, relationships, and capacities emerge.
  6. Iterate as you learn what the new metaphor actually generates.

Section 5: Consequences

What flourishes:

New adaptive capacity emerges because metaphors are the deep grammar of possibility. When “change is construction” shifts to “change is emergence,” teams stop trying to predict and engineer; they start creating conditions and sensing what wants to be born. This generates faster adaptation, not slower.

Ownership deepens. When people move from “I am a resource to be deployed” to “I am a steward of this commons,” accountability becomes intrinsic. They care because they own it, not because they are measured.

Relationships shift. War metaphors create zero-sum thinking even in collaborative contexts. When teams experiment with “collective thinking is music” instead of “argument is war,” psychological safety increases. People propose ideas more freely because they are not risking territory.

What risks emerge:

Rigidity of the new metaphor. The pattern’s vitality reasoning warns: this sustains ongoing functioning but does not necessarily generate new adaptive capacity. If a commons fixes on the new metaphor—”We are a living system, so we never plan”—it can become as brittle as the old one. The antidote: keep metaphors as tools, not truths. Rotate them. “We are an organism AND a jazz ensemble AND a garden AND a learning community.” Rigidity kills this pattern faster than any other failure mode.

Metaphor fatigue. If leadership keeps introducing new metaphors without sitting long enough with one to harvest its lessons, the practice becomes “flavor of the month.” This hollows the pattern. Implement one new metaphor deeply for 6–12 months before considering another.

Collapse into poetry. The pattern can become abstract workshop talk disconnected from metrics and accountability. To keep it alive, always connect the metaphor to concrete changes: new meetings, new measures, new roles, new decision-making. If the metaphor does not change what you actually do, it is not alive—it is decoration.

Assess score warning: Resilience (3.0) and ownership (3.0) are below the vitality threshold. This means the pattern itself needs tending. A commons relying on this pattern alone, without also building diverse feedback systems and distributed decision-making, can become fragile. Pair it with other patterns that build structural resilience.

Section 6: Known Uses

Example 1: Lakoff & Johnson’s “Argument is Dance” (Cognitive Science Foundation) Lakoff and Johnson documented how academic discourse shifted when researchers in certain communities began experimenting with “argument is dance” rather than “argument is war.” In collaborative research labs, this metaphor reframed peer review. Instead of “defending your thesis against attack,” you were “learning to move together with your peers’ insights.” The consequence: researchers proposed more speculative ideas earlier, cross-disciplinary collaboration increased, and the pace of innovation accelerated—not despite the slower, more responsive framing, but because people were not protecting territory. This is the founding example of how metaphor shapes thought and action at scale.

Example 2: Patagonia’s “Business is Activism” (Corporate Context) Patagonia operates under a counter-metaphor to mainstream business. Rather than “business is competition for market share,” Yvon Chouinard and the company’s culture team embedded “business is activism”—a way to scale environmental and social change. This metaphor cascaded through hiring (they hire activists), metrics (they measure environmental impact as seriously as profit), decision-making (they fund causes even when it costs market share), and pace (they move at the speed that allows regeneration, not extraction). The metaphor did not require structural revolution; it required consistent language and decision-making aligned with it. Patagonia’s ownership structure and employee loyalty are unusually high—directly traceable to people living by a metaphor that honors what they actually value.

Example 3: Highlander Folk School’s “Education is Liberation” (Activist Context) Myles Horton’s Highlander Folk School (active since 1932, still operating) was built on the metaphor “education is liberation,” not “education is information transfer.” This shaped everything: the pedagogy (dialogue, not lecturing), the physical space (circles, not rows), the role of educators (facilitators, not experts), and the communities served (those organizing for justice). The metaphor generated entire new practices—popular education, participatory action research, democratic deliberation. Thousands of social movement leaders trained at Highlander lived by this alternative metaphor and carried it into their work. The metaphor was not incidental to the organization’s impact; it was structural.

Section 7: Cognitive Era

In an age of distributed AI systems and algorithmic framing, metaphors become even more consequential and even more invisible.

The new danger: Large language models and recommendation algorithms are trained on metaphors embedded in text. When an LLM learns from a dataset saturated in “time is money,” it replicates that metaphor in its outputs. When a product algorithm optimizes for “engagement as conquest,” it models that logic into its suggestions. Metaphors are no longer just human cultural artifacts—they are baked into the intelligence systems we delegate decisions to. A commons that does not actively work with metaphors is surrendering its possibility to systems designed under someone else’s metaphors.

The new leverage: Conversely, a commons that names and experiments with metaphors can teach its AI systems differently. If a product team decides “user health is cultivation,” they can prompt their models with that framing. They can design training data that honors the metaphor. They can measure success by whether the AI amplifies the metaphor’s logic or undermines it. This is not metaphor as decoration—it is metaphor as infrastructure for human-AI alignment.

The tech context translation becomes urgent: For Products means deliberately choosing: Is this product trained under “engagement as addiction,” “attention as resource,” “user as data source”? Or “user as flourishing agent,” “attention as sacred,” “relationship as mutual?” The metaphor that governs your training data governance and your reward signals will show up in user experience. You cannot hide from this choice anymore.

New risk: Metaphors generated by AI systems operating at scale can colonize human thinking faster and more deeply than before. If millions of people use a product designed under “community as engagement metrics,” that metaphor will rewire how they think about belonging. The commons working with this pattern must become meta—not just choosing its own metaphors, but noticing and resisting metaphors embedded in the systems it uses.

Section 8: Vitality

Signs of life:

  • Explicit metaphor language in daily speech. When team members say “we are tending emergence” or “this is composting time” and others understand without explanation, the metaphor is alive. It has moved from workshop to practice.
  • Changed decision-making. Watch for decisions that would not have happened under the old metaphor. A product team refuses a “growth hack” because it violates their “user as steward” metaphor. A government program shifts timeline from quarterly to seasonal. These are metaphors working.
  • New metrics and measures. The metaphor is alive when measurement systems change. “Time is soil” means you measure seasons of growth, not hours of output. You can see it.
  • Discomfort and creative conflict. When the new metaphor bumps against the old one, you get productive tension: “But we said we were tending emergence—why are we rushing this?” This friction means the metaphor is shaping actual choices.

Signs of decay:

  • The metaphor becomes a slogan. “We are a living system” shows up in mission statements but not in how budget decisions are made. The metaphor is decoration, not structure.
  • Reversion to old language under pressure. When deadline pressure hits, teams revert: “We need to move fast, just get it done.” The alternative metaphor has not taken root; it is still fragile.
  • No visible consequences. If the metaphor changed nothing about how work happens, metrics used, or relationships built, it is not alive. It is ambient but inert.
  • Metaphor stagnation. The same metaphor is repeated year after year without rotation, iteration, or deepening. It has calcified into a new orthodoxy.

When to replant: If you detect decay, the right moment to restart is when the system experiences enough friction that the old metaphor’s costs become visible. A team burning out under “time is money” becomes open to “time is rhythm.” A product’s toxic engagement metrics create opening to ask “what if we lived by a different metaphor?” The pattern works best when it is responsive to actual system pain, not imposed as best practice. Replant by surfacing the hidden metaphor again, asking what it is costing, and designing together. Do not impose a new metaphor—grow it from the system’s own values.