There are many EA maturity models, This one is based on my empirical observation and is a little tongue-in-cheek

1. A Maturity Model for Enterprise Architecture
by Sally Bean
There are many different maturity models for EA, of
varying utility. This model reflects my practical
experience of working with organisations that are trying
to implement Enterprise Architecture. Note that these
are typically currently anchored somewhere in the IT
function, but don’t have to be.
1

2. EA maturity model
• EA activity seen as enabling not inhibiting other
Achieving activity
May progressively Value • EA Content is used, maintained and shared
• Positive outcomes being achieved
integrate different
EA domains (e.g. • Small focused EA competency centre in place with wider
technology, data, community involved as required
business) Implementing • EA content is appropriately structured and managed
• Relevance to other projects and activities understood.
May iterate or go
• Pilot (perhaps for a business unit) to establish potential value of EA
• Enthusiastic cross-functional team involved
backwards, especially if Experimenting • Skilled and experienced advisors available
key players disappear or • Learning orientation
an inappropriate • Luddites marginalized
approach is chosen
• Different people have different perceptions of what EA is
Confused • Enthusiasts want to rush off and try it
• Luddites say it’s just the same old stuff with a new name
• EA is competing for attention with other new ideas
• Business case is not understood
• Thinks there may be potential value in it
Aware/ • Receptive to pitches, conferences, etc
Interested • A few champions are keen to proceed
2
©Sally Bean 2009