Enterprise Architecture has never had more influence over the future of organizations. Architects shape technology investments worth millions, design operating models that redefine how work is performed, and guide transformations that span years. Yet amid discussions about artificial intelligence, cloud modernization, platform engineering, and governance, one question is surprisingly easy to overlook.

Enterprise Architecture is often associated with technology roadmaps, reference architectures, and governance frameworks. Yet its greatest contribution to an organization lies elsewhere. At its core, Enterprise Architecture is the discipline of making high-quality decisions amid uncertainty. Every significant transformation—whether migrating to the cloud, modernizing legacy systems, adopting artificial intelligence, or redesigning business capabilities—is ultimately shaped by a series of choices. The quality of those choices determines whether an enterprise gains resilience and competitive advantage or accumulates technical debt and strategic regret.

Every organization talks about strategy. Boardrooms discuss it, executives present it, consultants document it, and employees are asked to align with it. Yet despite the attention strategy receives, surprisingly few organizations have one.

Enterprise Architecture has never been about technology alone. At its core, it is about enabling organizations to solve meaningful business problems and create sustainable value. Yet many architecture teams spend far more time discussing cloud platforms, AI models, integration patterns, and application modernization than understanding the people and business challenges these technologies are meant to address. The most effective Enterprise Architects think less like technology specialists and more like entrepreneurs. They observe before they design, communicate before they convince, and solve problems before they showcase technology. This entrepreneurial mindset is captured in the simple but powerful framework of See, Solve, Scale, and it offers valuable lessons for every architect leading digital transformation.

When people think about Enterprise Architecture, they often imagine technology roadmaps, target-state architectures, governance committees, and transformation programs. Rarely do they think about negotiation.

Recently, I’ve been carrying the quiet sadness of losing someone deeply important in life. Not the kind of sadness that announces itself loudly, but the kind that lingers beneath ordinary moments. It appears in silence, in familiar places, in routines that suddenly feel incomplete. Grief has a strange way of revealing how much of our lives are intertwined with the presence of another person. We think we understand how much someone matters to us while they are here, but often it is only through absence that we fully comprehend the weight of their existence in our lives.

There are two kinds of Enterprise Architects. The first kind reads a chapter of an industry framework, finds a reference architecture on a vendor blog, redraws it in their tool of choice, and presents it as their own thinking. They are useful. They are also, on a long enough timeline, automatable. The second kind treats every engagement as a small piece of original research. They produce frameworks, not slides. They get paid for what only they could have written. I’ve been thinking a lot about which one I’m becoming, and a passage I read recently sharpened the question in a way I want to share.

Corporate finance and enterprise architecture seem like entirely different disciplines. One deals with capital allocation and shareholder value; the other with systems, capabilities, and technology strategy. But peel back the surface, and they share the same underlying logic: how do you make good decisions when resources are scarce, uncertainty is high, and the people making decisions don’t always have the same interests as the people bearing the consequences? Here are four ideas from corporate finance that I think every enterprise architect should internalise.

Leaving Hong Kong to work in Singapore, nearly five years have passed in the blink of an eye. Every time I return to Changi Airport and walk up to the automated immigration gate, two words appear on the screen: “Welcome Home.” Politics aside, let’s keep things light. As a Permanent Resident, this has become my second home. But the word “home” wasn’t always so certain.

Studying how the world’s top executives make decisions, you start to notice patterns that have very little to do with industry, company size, or technology stack. What stands out is the rigour they apply to their own decision-making, the same rigour most enterprise architects reserve exclusively for the systems they design. EA work sits at a strange intersection. We’re technical enough to understand the systems, commercial enough to translate them into business value, and senior enough to influence strategy, yet the craft of deciding well rarely gets the same attention as the craft of designing well. Here’s what we can borrow from the executives who’ve made it their discipline.