Architecture of Innovation

"How do I become more innovative at work?" I get this question a lot. I think it's because we've been conditioned to believe that innovation is a dramatic, lightning-strike moment.

But these days, my thinking about breakthroughs comes with a footnote: most real innovation isn't a giant leap. It's a relentless series of small, intentional steps.

Start with a Simple Question

Innovation starts with a simple, consistent question: "What more can I do to improve this?" It begins when you iterate on a workflow, a process, or a product and make it slightly better than it was yesterday. Over time, these refinements compound. Building the muscle to make big bets actually starts with refining how you communicate an idea or use a simple tool.

The Bedrock Requirement

However, there is a bedrock requirement: you cannot improve what you do not understand. Domain knowledge is the soil where innovation grows.

Innovation is not a moment. It is a discipline. And like every discipline, it rewards consistency over brilliance.

The people I've seen drive the most meaningful change in organizations are rarely the ones with the flashiest ideas. They are the ones who understood their domain deeply enough to see what others missed, and then had the patience to iterate until the improvement became undeniable.