Books That Changed My Thinking
Not a reading list. A list of the specific books that actually changed something in how I think — what the change was, and why it happened then rather than earlier or later.
Founder, Majhi Group & Majhi OS
Reading lists are easy to produce and usually not very useful. What is rarer — and more honest — is accounting for what a specific book actually changed in how you think, and when it landed. The same book read at different stages of life produces different effects. What I list here are books that landed at the right moment and updated something real.
Thinking in Systems — Donella Meadows
This is the book that gave me language for something I had been observing for years without the vocabulary to name. The concept of the feedback loop — particularly the observation that in most failing systems, everyone is behaving rationally and the problem is not any individual actor but the structure of the system they're in — reorganised how I understand both the businesses I work in and the places I think about.
What it changed: I stopped trying to identify who was at fault when something wasn't working and started asking what about the structure was producing the outcome. This is a different and harder question, but it is usually the right one. I apply this framework constantly — in hiring, in thinking about development in Kalahandi and Odisha, in diagnosing why organisations behave in ways that seem irrational from the outside.
The Remains of the Day — Kazuo Ishiguro
Not a business book, obviously. A novel about a butler who spent his life serving an employer who turned out to be on the wrong side of history — and who, in the process, sacrificed the personal life he might have had, telling himself the sacrifice was duty.
What it changed: a specific kind of clarity about self-deception. The central character is not stupid or dishonest in any obvious sense. He is simply very good at finding justifications for the choices he is making for other reasons. Reading it early in my career made me more attentive to the versions of this I was doing in my own life — the framing I was using to make a choice feel principled that was actually about something less comfortable.
I have reread it once and both times it was uncomfortable in a useful way.
The Outsider — Albert Camus
Read this before I had the professional vocabulary to articulate what it was doing to me. The argument — that most of the social performances we engage in are performances rather than felt experiences, and that the honest alternative is alienating but also clarifying — landed at a moment when I was navigating multiple contexts and performing differently in each.
What it changed: a willingness to be simpler. Not less sophisticated — less performed. To say what I actually thought in situations where the performed version would have been more socially comfortable. This is a choice I make imperfectly and have to keep remaking. But Camus named something that I recognised and gave me permission to value the recognition.
Zero to One — Peter Thiel
I am ambivalent about how the ideas in this book have circulated since its publication. But when I read it early, what it changed was specific: the distinction between horizontal progress (doing more of what already exists) and vertical progress (doing something that has not been done before), and the argument that genuine value creation requires the latter.
This challenged a way of thinking about business that I had absorbed — that success was about executing better on an existing model. The book's argument that the most important businesses create new categories rather than winning existing ones made me think differently about what I was building.
The specific change in practice: I became much more attentive to whether I was defining Majhi OS as "executive search but better" or as something categorically different. The difference in how you define what you're building determines the strategic choices you make at every subsequent decision point.
The Dhammapada
I came to this not through Buddhism as religion but through a period when I was reading across philosophical traditions looking for frameworks that were honest about difficulty and didn't resolve it with reassurance.
What it changed: a functional framework for the relationship between thought and action — specifically, the observation that most suffering is self-generated through the stories we build around events rather than the events themselves. This is not a new insight and is shared across traditions. But reading it in this text, at that time, gave it a specificity that more culturally familiar framings hadn't.
Practically: a habit of asking, when something is bothering me, whether the disturbance is coming from the situation or from my story about the situation. Often the story is the larger contribution to the disturbance, and the story is more modifiable than the situation.
What to notice about this list
The books that changed my thinking were not uniformly the ones most people would list as important. They were the ones that arrived at moments when my model of something was brittle enough to break — when I had enough experience with a domain to know that my current explanation was inadequate, and the book provided a better one.
This is probably true for most people. The same book read too early produces nothing; read at the right moment it reorganises something. The reading list that is useful for someone else is the list of books that will arrive at the right moment for them — and I can't know when that is for anyone but myself.
What I can say: the books that have mattered to me most have been ones that were precise about something real, that named things I had observed but not articulated, and that were willing to be uncomfortable in the service of being accurate. Those are the qualities I look for when I pick up something new.
Continue Reading
Related writing
How I Think About Learning
Learning is not a passive accumulation of information. It is an active process of updating models — and the models you hold determine which new information you can absorb and which you can't. Understanding this changes how you learn.
What Was I Wrong About?
The question is more useful than it is comfortable. Which is probably why most people avoid it.
How I Think About Systems
A system is any set of components that interact to produce an output. The output is almost never what any individual component intended. This is why fixing individual components rarely fixes the output — and why thinking in systems is a different kind of intelligence than thinking about things in isolation.