Organizations invest significant time creating strategies, roadmaps, and target architectures. Yet many transformation initiatives fail to deliver the expected outcomes. The reason is rarely the strategy itself. More often, organizations lack an operating model for change.
Strategy defines where we’re going. An operating model for change defines how we get there.
Change Is a Capability
Many organizations treat change as a collection of projects. Projects begin. Projects end. The organization moves on. Successful organizations think differently. They treat change as a continuous organizational capability. Instead of asking:
Which project delivers this initiative? they ask: How does our organization continuously adapt?
One optimizes projects. The other optimizes change.
Architecture Is Necessary, But Not Sufficient
Enterprise architecture provides direction. It defines principles, target states, capabilities, and technology strategy. But architecture alone does not create change. Successful transformation also requires:
- Governance
- Funding
- Clear decision rights
- Product ownership
- Delivery capabilities
- Feedback loops
Without these elements, even the best architecture becomes shelfware.
An Operating Model for Change
A practical operating model answers questions such as:
- Who makes strategic decisions?
- Who owns business capabilities?
- Who prioritizes investments?
- Who funds change?
- Who governs architecture?
- Who measures outcomes?
If these questions remain unanswered, delivery teams will create their own operating model. That rarely scales.
Connecting Strategy to Delivery
One way to think about change is as a chain of connected decisions.
flowchart LR
Strategy --> Capabilities
Capabilities --> Investments
Investments --> Products
Products --> Delivery
Delivery --> Outcomes
Outcomes --> Strategy
Each stage influences the next. Most importantly, outcomes feed back into strategy, creating a continuous learning loop rather than a one-way roadmap.
Governance Enables Speed
Governance is often mistaken for bureaucracy. In reality, good governance reduces uncertainty. When decision rights are clear:
- Teams move faster.
- Dependencies become visible.
- Escalations decrease.
- Architectural consistency improves.
- Strategic priorities remain aligned.
The goal is not more governance. The goal is better governance.
Examples of Operating Models for Change
There is no universal operating model. Different organizations optimize for different types of change.
Project-Centric
Change is delivered through temporary projects. Characteristics:
- Annual planning
- Project managers
- Stage-gate governance
- Fixed budgets
- Defined start and end dates
Best suited for organizations with predictable, discrete initiatives.
Product-Centric
Long-lived product teams own products from idea through operation. Characteristics:
- Persistent teams
- Continuous funding
- Outcome-based planning
- Frequent releases
- Product ownership
Best suited for organizations delivering digital products and services.
Capability-Centric
Business capabilities become the primary organizing principle for investment. Characteristics:
- Capability ownership
- Strategy aligned to capabilities
- Cross-functional planning
- Long-term investment horizons
- Architecture-led decision support
Best suited for large enterprises undergoing strategic transformation.
Platform-Centric
Shared technology platforms provide reusable capabilities for delivery teams. Characteristics:
- Internal platforms
- Self-service engineering
- Shared services
- Standardized technology
- Reduced duplication
Best suited for organizations with many engineering teams.
Federated
Decision-making is distributed while governance remains consistent across the enterprise. Characteristics:
- Local autonomy
- Shared architecture principles
- Lightweight governance
- Clear decision rights
- Enterprise-wide standards
Best suited for large organizations balancing autonomy with consistency.
Most Organizations Use a Hybrid Model
Few organizations operate using a single model. A modern enterprise might:
- Organize delivery around products.
- Invest according to business capabilities.
- Build shared technology platforms.
- Govern through a federated architecture function.
The objective is not to copy another organization’s operating model. The objective is to create one that enables continuous change while remaining aligned with business strategy.
Architecture as Part of the Operating Model
Architecture should not exist outside delivery. Nor should it become a centralized approval function. Instead, architecture enables change by providing:
- Principles
- Guardrails
- Target architecture
- Decision support
- Long-term thinking Architecture becomes one capability within a broader operating model for change.
Final Thoughts
Organizations don’t transform because they produce better architecture diagrams. They transform because they establish an operating model that consistently turns strategy into outcomes.
Architecture is one part of that model. Governance is another. Delivery is another.
The most successful organizations connect them into a system that continuously learns and adapts. An operating model for change is not about controlling transformation. It’s about making continuous transformation possible.