EA Tool Patterns
If you are using, or thinking of using, an enterprise architecture tool, then we have got some tips on how to create and maintain EA repository success.
EA tools typically have one of two patterns.
Pattern one is great enthusiasm for the first 3 to 6 months and then ongoing success as the tool becomes more embedded in the organisations processes, with lots of value drops. The tool becomes an inherent part of the organisations processes and is used to support decision making.
Pattern two is great enthusiasm for the first 3 to 6 months, then surprise as no one is using the tool, then it withers on the vine as people stop using it.
We see this from time to time with our tool and other tools. We explained to someone recently, who wanted to move from another tool to Essential, that the problem wasn’t the tool, it was their approach, and they would see the same result with Essential unless they changed tack.
Our 5 Tips for EA Repository Success
So, what do you need to be successful? Based on what we see with our successful clients here are some tips:
-
Keep your value drops small and achievable
Have a clear view on value, agree it with a stakeholder and ensure you have data required to deliver it. Successful teams will, almost invariably, tell you they asked their stakeholder what they wanted and explain how they addressed quickly
-
You drive the tool, don’t let the tool drive you.
Don’t look at the tool and see a nice-looking view or report then say, ‘I’ll get that working’. Instead, look at the challenges the organisation is facing and work out how the tool can help address those. Don’t go looking to justify delivering a pretty view by solving problems that don’t exist
-
Don’t be driven just by data
Successful teams focus on value and then look at the data available and focus on that. They don’t throw data at the EA tool because they have it. If you take the latter approach then you typically end up with a half-baked EA tool with some data complete, some not, some out of date. Users question the value as they get half answers to questions, and at this point you are on the path to failure. Our CEO often talks about seeing your EA tool as a palace, you don’t try to decorate every room at once, you pick a room and focus on getting that one done before you move on
-
Make the tool an inherent part of what you do
Successful teams make EA a step in their process and engage with other teams to maintain data. They keep data requirements tight and, again, focused on value. Initially, the EA are likely to manage the step but over time they devolve maintenance out as they demonstrate value and teams engage.
We sometimes hear people say we won’t have time to maintain a repository, we’re too busy on projects. This is actually the prime opportunity for EAs to get their repository in shape, the key is to identify what role EA is going to play in supporting the organisation, and what data is needed. At one organisation, this meant documenting the system interfaces in Essential, rather than spreadsheets, so future projects (and support) could leverage the information going forward. -
Communicate
Successful EA teams communicate wins and opportunities from the EA tool. They engage teams and ask, ‘how can we help you better’, they tell stories of how EA and the tool can help others be more successful through faster impact analysis, quicker decisions, earlier resolution of issues, etc
Follow the tips above to ensure that you follow pattern 1, with a successful EA repository to support your decision making.