Metaphors We Live By
Source: https://press.uchicago.edu/ucp/books/book/chicago/M/bo3637992.html ↗
The argument that metaphor is not a literary ornament but the fundamental structure of human thought.
We think in metaphors — argument is war, time is money, organisations are machines — and these frames shape what we can see and what we cannot.
For product people who write strategy documents, name features, and frame problems for teams: the tools of framing are the tools of thinking.
Lakoff and Johnson demonstrate that choosing a metaphor is never a neutral act; it determines which aspects of a problem become visible and which disappear.
This book explains why the language a team uses is not decoration but infrastructure.
Central argument
Lakoff and Johnson argue that metaphor is not a rhetorical flourish but the primary cognitive mechanism through which humans understand and act in the world. Conceptual metaphors — such as 'argument is war' or 'time is money' — are not descriptions of reality but structures that selectively highlight certain features of a domain while hiding others. The book's central claim is that these metaphorical framings are embodied and cultural, meaning they are largely invisible to those operating inside them, yet they determine what solutions, conflicts, and possibilities people can even perceive.
Critique
The framework is more diagnostic than prescriptive: Lakoff and Johnson excel at revealing how existing metaphors constrain thought, but they offer limited guidance on how to deliberately construct or replace a dominant conceptual metaphor within a community that has already internalized it. There is also a tension in the argument's scope — if all thought is metaphorical and metaphors are culturally embodied, it becomes difficult to explain how people ever successfully challenge or escape a prevailing frame, which risks a soft determinism the authors never fully resolve.
Why it matters for product
When a product team describes their roadmap as a 'pipeline,' their users as 'traffic,' or their organisation as a 'machine,' they are not choosing neutral vocabulary — they are importing a set of assumptions about flow, fungibility, and interchangeable parts that will quietly govern which trade-offs feel acceptable and which problems get named at all. A CPO who understands this can treat language audits as a strategic tool: the metaphors embedded in a product strategy document or an OKR template are often the clearest signal of what the organisation is structurally unable to see about its users.