Situation
The business context
A large, multi-brand restaurant company had accumulated more than a decade of technical debt within a highly siloed IT environment and cloud consumption costs had grown to unsustainable levels. Technology, data, processes, and capabilities were often managed independently, resulting in redundant systems and work, unnecessary costs, significant technology risk, and investments that were not always aligned with business strategy. There was no enterprise-wide architecture discipline providing visibility across the technology landscape or a consistent mechanism for connecting technology decisions to business priorities.
Task
The leadership mandate
As a senior IT leader, I was responsible for establishing an Enterprise Architecture practice that would better align technology, data, processes, and capabilities with business strategy, expose and prioritize technical debt, strengthen governance and compliance, and create a repeatable mechanism for identifying and enabling enterprise transformation, all within a very lean organization.
Strategy
The strategic approach
My strategy was to establish Enterprise Architecture as a lean decision-enablement capability rather than a centralized approval body. The approach began with creating shared visibility into the technology landscape, then connecting that landscape to business capabilities and priorities. Governance would be embedded into existing delivery and change processes, while an Architecture Community of Practice would distribute ownership and encourage adoption without adding unnecessary bureaucracy. The resulting insight would be used to expose waste and risk, improve investment decisions, and sequence broader transformation initiatives, with cloud governance providing an immediate opportunity to demonstrate measurable value.
Action
How the work moved forward
- Created shared enterprise visibility: Mapped and documented the current-state architecture, including applications, infrastructure, data, integrations, dependencies, processes, and capabilities, and established a centralized EA repository in SharePoint as the enterprise source of architectural information.
- Connected architecture to business priorities: Partnered across business and technology teams to relate capability needs and strategic priorities to the enterprise technology landscape, using EA insight to identify gaps and inform investment and roadmap decisions.
- Embedded governance into the flow of work: Introduced architecture policies, standards, and controls, including cloud-governance measures, to improve consistency, accountability, cost management, and technology decision-making. Embedded architecture and security reviews into change management so concerns could be addressed before changes reached production.
- Distributed architectural ownership: Created an Architecture Community of Practice rather than a traditional Architecture Review Board, enabling cross-functional collaboration, knowledge sharing, and standards adoption within a lean organization.
- Converted insight into transformation priorities: Used the EA practice to expose technical debt, redundancy, waste, and risk, then shape and sequence subsequent platform, data, resilience, cloud, and operating-model transformations aligned with business strategy.
Result
The measurable difference
- Exposed previously hidden technology risks and opportunities: Uncovered and documented significant technical debt, redundant and poorly understood systems, unnecessary costs, architectural risks, and modernization opportunities obscured by years of siloed technology decisions.
- Created a centralized source of architectural truth: Consolidated previously fragmented or difficult-to-find architecture documentation into an accessible enterprise repository, improving transparency, institutional knowledge, and understanding of systems and dependencies across IT.
- Delivered more than $1M in recurring annual savings: Cloud governance policies and controls significantly reduced wasteful Azure consumption while creating greater accountability for cloud resources.
- Institutionalized stronger technology controls: Embedded architecture and security reviews into change management and established enterprise policies, standards & principles, and controls, creating a repeatable mechanism for identifying architectural, security, and compliance concerns before changes reached production.
- Shaped four enterprise transformation initiatives: EA findings identified and shaped coordinated initiatives for infrastructure and technology lifecycle modernization, data-platform modernization, enterprise BCDR, and cloud governance and cost optimization.
Leadership insight
Transformational leadership creates the conditions to turn strategy into action. Enterprise Architecture enables this by improving critical decisions, exposing waste and tradeoffs, and aligning teams around shared capabilities rather than isolated solutions.