Why Enterprise Architecture Matters More Than Ever: Resilience, Supply‑Chain, Talent, and Delivery
The article explains how modern enterprise architecture helps organizations tackle three critical challenges—enhancing resilience and adaptability, planning for supply‑chain disruptions, and improving employee recruitment, retention, and product delivery—by mapping technology, processes, and dependencies across the enterprise.
Enterprises are using enterprise architecture to improve product delivery, risk management, employee retention, and other critical business purposes.
The EA discipline is often criticized for forcing business users to choose technology or producing software analyses that no one uses.
However, today EA practice is booming, and any architect described is hard to find and "very expensive," says Gartner research VP Marcus Blosch.
Forrester Research has identified more than 20 EA roles used by its customers, ranging from organizational architects defining business and operating models to project, platform, and digital architects. Forrester chief analyst Gordon Barnett says: "The list is growing, shifting from EA focused only on applications and infrastructure to true enterprise. You need an ecosystem of subject‑matter experts. You may not call them architects, but they still play architect roles."
Below are three pressing business challenges where savvy EA practitioners help enterprises.
Resilience and Adaptability
As companies move from COVID shutdowns to economic sanctions disrupting operations and supply chains, they turn to EA insights to predict and respond to problems faster and more effectively.
Barnett says that while resilience has always been a focus of EA, "the focus now is proactive resilience" to better forecast future risks. He suggests expanding EA to map not only the enterprise’s technology assets but also all processes that depend on suppliers, as well as part‑time and contract workers who may become unavailable due to pandemics, sanctions, natural disasters, or other disruptions.
Barnett adds that enterprises also want EA to predict problems and plan functions such as workload balancing or on‑demand computing to handle demand spikes or system outages. This requires architects to work more closely with risk‑management and security staff to understand component dependencies, assess interruption likelihood and severity, and enable response planning.
For example, EA can help describe which cloud providers share the same network connections or which carriers rely on the same ports, ensuring a "backup" provider does not suffer the same interruption as the primary.
Planning Supply‑Chain Disruptions
Mike Small, head of North America for engineering and digital solutions firm AKKA & Modis (soon to become Akkodis), says EA helps companies such as automotive manufacturers understand whether and how they can deliver products without a complete bill of materials—e.g., sourcing semiconductors.
Some of his clients bring together enterprise architects with product, analytics, and supply‑chain experts to ask, "Can I still safely sell the product without a 100 % bill of materials? If yes, what do I do when my system is designed for zero deviation from product specs?" This may require analyzing ERP systems to understand all dependencies and functions that reference the bill of materials.
Radicle Science provides online services to measure health and wellness product efficacy and uses EA to track API and data format usage of its data suppliers, so changes do not break the business, says CTO Sheldon Borkin. "The deeper we model third‑party logistics providers, the more we realize we need to map not only each provider’s API but also the format of the data they store for us. We need to write an adapter for each API and build the demand for such adapters and tracking capability into EA," he says.
Employee Recruitment and Retention
With talent shortages hampering industries worldwide, improving employee experience to retain key talent has become a strategic priority. Companies use EA not only to deliver better applications and services but also to create work experiences that attract and retain staff.
In recent years, AKKA & Modis has re‑engineered everything from its network to identity tools "to provide the same experience in physical offices or remote locations," says Small. "Remote work has forced our clients to reconfigure their EA plans and strategies. EA is critical to ensure these remote work and collaboration tools are scalable and secure," he adds. "This is a key differentiator we see in hiring and retaining talent."
Small says EA also plays a key role in understanding which applications and services new hires need on day one and ensuring they have access, "to enable new employees to onboard quickly and easily," which is crucial for retention.
Barnett says "people architecture" is an evolving EA form that aims to understand how outsourcing, layoffs, and automation affect staff and how to help them adapt. For example, much of a network engineer’s work has been automated. Understanding how these changes affect them and how to use their skills in new areas is vital for retaining employees and maximizing productivity.
Improved Product and Service Delivery
Across industries, agile companies need to focus IT work on the products and services customers need most, rather than implementing technology for its own sake.
Small sees a trend of redeploying employees who previously worked on cloud or data‑analysis technologies in independent teams into project‑based pods that address urgent needs. EA is the glue that binds these units, looks at overall business demand, and ensures the products or services they develop work well.
At Wells Fargo, EA provides a cloud reference architecture that supports the financial‑services giant’s migration to the cloud, agile software development, and new "products" such as guiding first‑time job seekers to create bank accounts and obtain their first credit card, says chief enterprise architect Manish Vipani.
EA also helps Wells Fargo integrate front‑end and back‑end applications to create a more consistent cross‑channel experience (in‑person, web, phone, mobile). Vipani says its EA practice is helping move from a point‑to‑point "spaghetti" architecture to a more layered "lasagna" style with clearer API connections.
For example, hundreds of EA initiatives help Wells Fargo modernize its online mortgage application by pre‑filling data, reducing the process from an average of 25 minutes to 4 minutes. If the integrated system can tell the credit‑card application that the customer has a direct deposit, it can pre‑qualify them and process the application with a click.
"We usually want to launch a product quickly, and if it succeeds, scale it up," says Vipani. "That requires understanding all systems exposed via APIs, whether core banking platforms or wealth‑management."
Tracking Data and APIs
As Radicle strives to complete virtual trials of more health products faster and demonstrate results to customers, "our software platform needs to orchestrate people, participants, and supplies to be scalable," says Borkin.
To achieve this, it is redefining its EA components to understand, for example, which data must be stored in what format for future research. "It’s critical that the tech team and the research team communicate," he says. "As a company we agree on the key data and how it should be organized."
Radicle also uses EA insights to determine how many databases to maintain and when to exchange data via point‑to‑point APIs, usually between internally developed services or one‑off integrations rather than a public service layer intended to scale over time.
"Because we are building a multi‑year research data repository, simply saying we have an API is not enough," he says. "You may not know all the APIs needed to connect to a new data source or service, such as the data normalization required to interact with the research repository." Radicle uses EA to "ensure we build this critical data asset to expand in breadth and depth while remaining easy to access to discover new health insights."
Architects Research Society
A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.