Ideas in the Margins: What a Reading Habit Does for a Builder

Most of my best ideas for building ventures did not arrive in a meeting. They arrived in the margin of a book that had, on the surface, nothing to do with the problem I was trying to solve.

That's not an accident. It's the whole point of reading widely. A meeting can only give you what's already in the room. A book drops you into a mind that solved a different problem, in a different field, a different century — and the value isn't the answer it offers, but the angle. You read about how cities handle traffic and suddenly see how opportunity flows through a community. You read history and recognise the shape of a present-day failure. The ideas don't transfer. The patterns do.

I write in the margins for a reason too. A passively read book leaves almost nothing behind a week later. The argument I had with the author in pencil — the "yes, but," the "this is exactly like —" — is the part that stays, because I made it mine. Reading without a pen is consumption. Reading with one is thinking.

And it does something quieter that matters more over time. Building ventures is a daily exercise in certainty — you have to decide, commit, move. Reading is the opposite discipline. It puts you, repeatedly, inside a view that isn't yours and asks you to inhabit it before judging it. That's the same muscle inclusion needs: the willingness to see through eyes that aren't your own. I'm not sure you can build for people you refuse to understand. Books are the cheapest way I know to practise understanding.

So I don't read to escape the work. I read because it's where the work refuels.

The question I'd leave with any builder is small and stubborn:

When did you last let an idea in from somewhere completely outside your problem?