Designing the Conditions Where Value Can Move

Preface

For years, I introduced myself as an Enterprise Architect.

Now I introduce myself differently — through this book. Not because the title changed, but because what I was actually doing became clear.

This began as scattered writing across a decade of consulting work: notes on architecture, on teams, on the strange gap between what organizations say they value and what their systems actually optimize for. Read one post at a time, it looked like a blog. Read together, it was making the same argument over and over, in different rooms, for different clients, in different words.

That argument is what this book is now.

Organizational Flow is not a methodology. It is not a framework you adopt on a Monday and report on by Friday. It is the name I’ve given to something I kept noticing: that organizations create value by moving — information, decisions, execution — through capabilities that endure longer than any tool used to run them. When that movement is easy, everything downstream gets easier too. When it isn’t, no amount of technology fixes it.

I am not building a consulting company. I am an independent consultant, and this book is the other half of that practice — the half where the experience gets turned into something worth keeping. Practice creates insight. Insight develops perspective. Perspective improves practice. This book is where that cycle becomes visible.

It is organized in four parts. Discovering Flow is personal — how I arrived at this way of seeing. Understanding Flow is the vocabulary — purpose, capabilities, ownership, people, information, decisions, execution, learning — the enduring parts of any organization, regardless of what’s fashionable in tooling this year. Designing Organizations is where that vocabulary becomes structure — leadership, architecture, technology, artificial intelligence, friction. Applying Organizational Flow is where it leaves the page.

Along the way you’ll find short essays in the margins — Insights, tagged to whichever chapter they belong to — and, occasionally, a model: never a diagram of boxes and arrows, always something closer to a forest, because that’s the closest metaphor I’ve found for how these things actually behave. Roots you can’t see. Growth that takes seasons, not sprints. A canopy that’s really just the visible result of everything underneath it working.

This book will keep growing. It is not finished, and it isn’t meant to be — that’s rather the point.