Eight years inside a bank teaches you the mechanics of money. These five books reshaped the mental models underneath — how systems behave under stress, why well-intentioned institutions still produce bad outcomes, and what rigorous financial design actually looks like. None of them are textbooks. All of them changed how I work.
The single most useful book I’ve read for understanding why complex organisations behave the way they do. Meadows explains feedback loops, delays, and system archetypes with extraordinary clarity. After reading it, I could not look at a payment network, a reconciliation process, or a regulatory framework without asking: where are the reinforcing loops? Where is the delay creating instability? Essential for anyone who manages infrastructure that other systems depend on.
View on Amazon ↗Christensen’s framework for disruptive innovation is misquoted constantly and understood rarely. Reading the original changed how I interpret the neobank threat to traditional banking — it is not that neobanks are better at the core product; it is that they are good enough at the low end while incumbents are busy over-serving their most profitable customers. The pattern is identical in Bangladesh’s MFS story.
View on Amazon ↗A forensic account of how latency arbitrage hollowed out trust in equity markets. I read it as a case study in what happens when financial infrastructure optimises for the wrong participants. The parallels to payment system design — who benefits from settlement delay, who profits from opacity in interchange, how infrastructure can be captured by the most sophisticated users — are direct and uncomfortable.
View on Amazon ↗I was sceptical of this book for years because of how it’s been cargo-culted in corporate innovation theatres. Reading it properly, the validated learning loop is genuinely useful for scoping digital banking product pilots — particularly for agent banking rollouts where the cost of a wrong assumption is measured in months of field staff retraining. The build-measure-learn cycle applies cleanly to payment product UAT.
View on Amazon ↗The operational one. Every system — including a bank’s daily settlement process — is the output of accumulated habits, not grand strategies. Clear’s framework for identity-based habit change is the most useful management tool I’ve applied to building reliable team processes. If you are trying to reduce reconciliation errors or build a culture of proactive exception reporting, the marginal gains argument in this book is the right mental model.
View on Amazon ↗