Enterprise architecture needs to get better at architecture strategy
I’ve been reading a lot of strategy books these last weeks 1 (also two James Bond books, but that is probably not related to this post), and I’ve been trying to tie it to my everyday work of enterprise architecture.
Most of these posts are just me finding an excuse to put my thoughts to paper to see if they make sense, so why not write a new post about what I’ve learned? It’s also a perfect time, with the end of the year approaching, to maybe reflect on the next year and how we can tackle it.
Let’s start with taking a step back and looking at where you currently are. And with that I mean, truly take a look at where you are.
In terms of architecture, this partly means data quality/quantity and governance. Do you have your entire application landscape mapped out? Are we talking about all application components being connected? What is the current information you have about your applications? When was the last time it was updated? Is everything mapped to the same level of depth?
What about your capabilities? When was the last time you updated those? Do you have enough levels to them (or too many)? Do they have owners? Do these owners know they are owners?
