Ask an executive for their corporate strategy, and you will often hear a number. They might say their strategy is to deliver a fifteen percent return on equity. Walk down the hall and ask a technology leader for their strategy, and you will likely hear the exact same mistake dressed in technical terms. They will tell you their strategy is to move eighty percent of their servers to the cloud by the end of the year, or to cut infrastructure costs by ten percent. However, targets are not strategy. A target is simply a wish with a deadline.
True strategy, whether in business or technology, is about understanding where you stand today, spotting the real threats in your market, deciding how to overcome them, and predicting how your competitors will react when you make your move. If your technology strategy is just a list of operational goals and software migration timelines, you do not have a strategy. You only have a to-do list. As Enterprise Architects, our job is not to draw endless diagrams. Our job is to design the technical advantages that help the business win. To do that, we need to stop thinking like internal support staff and start thinking like shrewd, long-term investors.
When Piyush Gupta led the digital transformation of DBS Bank in Singapore, he did not just hand out revenue targets or ask for a prettier mobile app. Instead, he forced leadership teams to confront the reality of their competitive environment with direct questions. Every Enterprise Architect should ask these same questions about their technology landscape. First, what does our regional and global competitive environment actually look like today? Second, what have our rivals built in the last three years to change the rules of the game, much like WeChat and Alipay did when they turned simple messaging and payments into massive digital ecosystems? Third, what have we built in that same period to disrupt them? Fourth, where are our current systems so slow and outdated that a fast-moving fintech or super-app could easily attack us? Finally, what bold technical bet are we making today to leapfrog the competition over the next three years? If your architecture plan cannot answer that final question, you are merely managing a slow decline.
Answering these questions honestly requires leaders to look outside their own walls. Many managers hate talking openly about competitors. Some worry about legal issues or revealing market dominance, while others are simply trapped in an inside view. They become so obsessed with their own internal project deadlines and team metrics that they completely ignore how rivals will respond. Yet in the investment world, one of the best signals occurs when a company admits a competitor is too strong to beat. For example, when the global ride-hailing giant Uber admitted it could not beat Grab in Southeast Asia and sold off its regional operations, it proved how powerful a deeply localized super-app ecosystem could be. Similarly, when traditional retail merchants across Asia openly admitted they could not match the logistics network and seamless payment flow of Shopee or Lazada, it showed those platforms had built a massive technical moat.
Enterprise Architects fall into this same inside view trap whenever they insist on building everything in-house. We often look at our engineering teams and convince ourselves we can build a custom payment gateway, a bespoke logistics engine, or an internal AI platform that will beat a dedicated regional leader. Intellectual honesty is a vital skill in architecture. When a competitor or a platform provider like Tencent, Alibaba Cloud, or Grab has already built an unbeatable advantage through scale and network effects, the smart move is not to waste engineering talent building a weak copy. The strategic choice is to partner with or integrate that commodity layer, and focus your best engineers on the unique problems where your company can become the undisputed leader.
Beyond understanding competitors, an architect must also understand company culture. Just as a healthy culture is a massive asset and a toxic culture is a fatal threat, the way people behave inside a company directly shapes the systems they build. You can learn a lot about a technology organization by looking at employee loyalty and true ownership. When DBS Bank shifted from massive external outsourcing to building strong internal engineering teams, or when companies like ByteDance and Sea Group empower small teams to own products from end to end, system resilience and speed skyrocket because developers believe in what they are building. You also have to look closely at incentives. If managers and architects get promoted for launching flashy, complex software rather than making things simpler and better for customers, the company is rewarding selfishness over real value.
Anyone can spot the warning signs of a broken technology culture if they know where to look. Outside investors read employee reviews on Glassdoor and look out for signs of executive greed and laziness, like lavish corporate perks or annual reports filled with dozens of photos of the CEO. In Enterprise Architecture, our version of executive extravagance is the over-engineered vanity project. When a technology leader spends millions of dollars building a massively complex system for a simple internal tool just to pad their resume, or buys five overlapping software products because they enjoy fancy dinners with sales vendors, the culture is broken. Similarly, when developers complain in internal chat rooms that it takes six weeks and four committee approvals to change a single line of code, that frustration is a clear sign of decay.
A target only tells you what you hope the scoreboard looks like at the end of the game, while a strategy tells you how to beat the other team on the field. The next time you review your organization’s technology strategy, cross out every numerical target pretending to be a plan. Strip away the ego-driven projects, be honest about where your competitors are winning, and look closely at the behaviors your company actually rewards. Great architecture is never about building the most complicated system in the room. It is about building a simple, resilient foundation that makes your business impossible to beat.
