Architecture as a Capability: Why Architecture Is Not a Function
Architecture creates the most value when it is treated as an organizational capability rather than a centralized function.
Architecture enables continuous change.
This site explores how organizations connect strategy, capabilities, operating models, governance, and technology to turn intent into execution.
I’m David Pettersson, an enterprise architect with experience across telecom, finance, insurance, and retail.
My writing combines practical experience with frameworks such as EDGY by Intersection, TM Forum ODA, and TOGAF, focusing on how organizations move from vision and target architecture to measurable outcomes.
If you’re short on time, start with the curated reading path below.
Architecture is not a document.
It is a capability that enables continuous change.
If you’re new to this site, this path explains how to approach enterprise architecture as a system for continuous change — from purpose, to direction, to execution.
Why architecture creates value when treated as an organizational capability rather than a centralized function.
How strategy becomes a navigational instrument for multi-year transformation.
How EDGY and ADM enable continuous enterprise design.
An end-to-end model for translating intent into execution.
Why capability maps fail — and how to make them matter.
A practical toolkit for architecture reviews, system onboarding, governance, and technology decision-making.
How strategy, architecture, and experience come together.
How to govern transformation using predictive signals.
Selected posts that explore architecture, capabilities, governance, and transformation in depth.
If you’d like to continue the conversation, connect with me on LinkedIn.
Architecture creates the most value when it is treated as an organizational capability rather than a centralized function.
A practical architecture review and governance toolkit for evaluating systems, guiding technology decisions, and enabling continuous change.
From edge control to protected domain logic in modern enterprise platforms.
A Modern Approach to System Design
How to use EDGY and an ADM-inspired cycle to translate strategy into real execution.
Most organizations have a capability map. Few use it to change priorities, funding, or decisions. Here’s why — and how to turn it into real leverage.
A practical Level 2 capability decomposition for financial institutions, bridging strategy, regulation, and execution.
A Level 1 enterprise capability map for financial institutions – enabling strategy execution, risk management, and regulatory compliance.
Why every transformation needs an Architecture North Star — and how capabilities provide the compass to guide change.
Why architects and leaders should look beyond lagging metrics when guiding transformation.
Lagging indicators show the past, but leading indicators give you the early signals that predict if change will succeed. Here’s how to spot and use them.
Exploring how EDGY service design thinking and capability mapping shape the next generation of retail products.
A concrete application of TOGAF ADM, enriched with the EDGY enterprise design language — using Capabilities, Assets, and Processes to make architecture trans...
In this final post of the series, I explore how to turn a finance target architecture and design blueprint into reality. What does it take to move from visio...
In my previous post, I outlined a modern finance target architecture with ERP, reporting, a finance data hub, and BI/analytics. This follow-up goes one step ...
Modern finance functions are expected to deliver far more than accurate bookkeeping. Today’s CFOs, controllers, and analysts must ensure compliance, enable a...
Finance systems are evolving. In this new series, I’ll explore how target architectures can bring together ERP, reporting, data hubs, and analytics to create...
A Modern Approach to System Design
A Modern Approach to System Design
CI/CD — continuous integration and continuous delivery as enablers of autonomy and transformation.
An overview of common integration styles — APIs, events, and information hubs — with their principles, rationale, and risks.