MIT CISR's three paths (improve, wrap, sell) and the five capabilities that decide whether you can actually monetize data — grounded in nearly three decades of research, but written to be read across the organization, not just by the data team.

The practical complement to Rumelt — a simple question framework (where to play, how to win) built on one of the most-cited turnarounds in American business.

Rumelt's follow-up to Good Strategy/Bad Strategy — less about what a strategy is, more about how to actually find the right diagnosis when reality is messy.

The book behind the whole idea of a strategy kernel — uncomfortably simple, and uncomfortably good at revealing when a document is only pretending to be a strategy.

Ett konkret ramverk — fem pelare: ansvar, risk, incident, leverantör och uppföljning — för att omsätta NIS2-kraven i praktisk bolagsstyrning. Mer handfast och mindre juridiskt än de flesta NIS2-texter jag stött på, skriven direkt för styrelserummet snarare än för compliance-avdelningen.

A shorter, more practical text on the art of asking instead of assuming — especially valuable for anyone (like me, sometimes) who's quicker to offer an answer than to ask a real question. Schein calls it "humble inquiry": building relationships by genuinely wanting to know, not by demonstrating that you already do.

Berger shows how companies like Google, Nike, and Airbnb were built on the ability to ask fundamental, game-changing questions — and offers a simple "why / what if / how" structure for getting there yourself. A good complement to Gregersen: more toolbox, less research depth.

Gregersen spent years studying what makes breakthrough ideas emerge — among entrepreneurs, researchers, leaders. The conclusion is as simple as it is uncomfortable: what separates a breakthrough from a standstill is rarely a better answer, but a better question. The book I think of most often when I feel stuck at the wrong level of a problem.

Barry Smith's best-known standalone book on ontology (2015, MIT Press) — more practical and less philosophically dense than the Blackwell chapter, focused on how to actually build ontologies that work in real information systems.

The book that put words to something I'd suspected for a long time: that speaking isn't just describing the world, it's doing something in it. Promising, naming, or warning aren't statements about an action — they ARE the action. Sounds like a philosophical nicety until you realize it's exactly why an AI that only “describes” can never quite act on your behalf — it's missing the performative part.

Demanding but central — the work that, more than any other, made “meaning is created through use” self-evident within philosophy. Wittgenstein's idea of language games is the simplest explanation I know for why a word can mean different things in different contexts without being vague or wrong. Read it in small pieces, not in one sitting — that's how it's written.

Not an easy read — not by a long shot — but the book where the idea that “the map is not the territory” was first properly formulated. I recommend it mostly so you know the origin, not so you necessarily plow through all eight hundred pages. Read a summary first, and go to the original if the thesis grabs you.

A practical counterweight to the more academic books on this list — concrete tools for not being fooled by your own words. Hayakawa's point about confusing the map (the word) with the territory (reality) is easy to understand and surprisingly hard to remember in the moment, especially in meetings where the language has already decided the outcome before the discussion even starts.

Pinker at his best: accessible, funny, and still deeply scientific about how much meaning hides in simple words. He shows how even a swear word or a politeness formula reveals whole mental models of space, time, and social relationships — and suddenly you see the same patterns in how people talk to AI assistants. If you only read one book about language and thought from this list, make it this one.

The book that made me realize how much of our “logical” thinking actually rests on metaphors we never question. “Time is money,” “argument is war” — Lakoff and Johnson show that phrases like these aren't figures of speech but conceptual structures that actually shape how we reason. After this book you stop seeing metaphors as decoration and start seeing them as infrastructure.

The book I return to most often when explaining why both humans and AI models fall for the same psychological tricks. Kahneman's System 1 and System 2 have become such common knowledge that it's easy to forget how radical it was to prove that our “rational” thinking is full of systematic shortcuts — framing, anchoring, availability. If you only read one book on decision-making, make it this one.