Part I — Discovering Flow
A Digital Awakening
“Is our IT future-proof?”
Our CEO asked it in a company meeting, the way you ask something you already suspect the answer to. I didn’t have a good answer. Worse, I realized I didn’t actually know what a good answer would sound like.
That question sent me looking for people who did. Through a fortunate chain of introductions, I ended up in conversation with Adrian Cockcroft, then at Netflix and AWS, and Rodrigue Schaefer, Head of Engineering at Zalando. Neither of them said anything I could have found in a textbook. They said the same thing, in different words: IT should not be a separate function. It should be the engine of innovation.
That sentence rearranged something in how I saw my own twenty years of work. I had spent two decades getting steadily better at running the engine — and no time at all questioning why it had been built as a separate room from the rest of the business in the first place.
Once I started looking, I saw the same pattern everywhere, including in my own organization: “digital transformation” as a rebrand, not a rebuild. New tools, new vocabulary, the same operating model underneath. Digitalization isn’t a technology purchase — it’s a cultural and strategic shift, and it has to start at the top, because nobody below the top has the authority to move it there.
The organizations that actually change are the ones where business and technology reinforce each other instead of negotiating a truce. When systems, data, and leadership point the same direction, innovation stops being an initiative and starts being a byproduct.
Years later, working across media, telecom, and insurance, I keep seeing the same tell: the companies still struggling are the ones treating architecture as a technical concern instead of an organizational one. Architecture was never just about systems. It’s about how everything connects — teams, decisions, incentives, and yes, technology, all at once.
I still think about that meeting sometimes — not because the question was clever, but because it was honest. Most transformation efforts start with an answer already decided. This one started with someone admitting they didn’t have one.
The future belongs to organizations that treat technology not as a cost center, but as a catalyst for creativity, capability, and change. I didn’t invent that idea. I just finally recognized it, at forty, in a conference room, from a CEO who had the sense to ask a question he couldn’t answer himself.