By Neil Rerup
On Friday, I posted an interesting article from Jason Bloomberg entitled “Is Enterprise Architecture Completely Broken?” that was published in Forbes. I thought it was a really well written article (no pandering here, Jason) and thought it accurately portrayed the current state of Enterprise Architecture. It asks questions that I’ve posted before – what does it mean to architect an Enterprise? What do we need to do to fix the practice of EA?
And the article finishes with the statement –
“Let’s put down the red stapler, stick that framework in a filing cabinet, and focus on practical steps to achieving the long-term transformation goals of your organization”
But here’s the thing that we have to remember – we are Architects and, as a result, to come to a solution we need to first understand the current state. To create a strategy on how to get to the TO BE state, we have to have the AS IS situation understood.
Read the entire article at https://www.linkedin.com/pulse/why-ea-broken-neil-rerup?trk=hp-feed-article-title-publish.
The EA’s focus on “as is” as well as “to be” are both problematic. The “to be” or final state is particularly counterproductive. See http://insights.wired.com/profiles/blogs/what-we-really-mean-by-digital-transformation#axzz3pC6Zg1CY for a discussion of these points.
