Enterprise Architecture (EA) organizations across the country have been hammered. As if the severe recession wasn’t enough, there are other reasons to account for this. Here are a few:
- EA organizations are notoriously unable to prove value.
- EA frameworks do not yet help EA organizations to prove value.
- EA tool vendors generally don’t help EA organizations to prove value.
Unfortunately the climate in the EA community is still inwardly focused on IT issues and not outwardly towards client concerns. That’s another reason EA doesn’t receive funding.
As we’ve seen lately in our review of TROUX, value for capabilities is missing but costs aren’t. How can you show value in such a situation? And that’s not rhetorical. With or without a tool, if your EA organization itemizes costs without linking them to value provided, then the only thing they can show is that EA activities are a drain on the corporate treasury. That’s not to say that there is no value to EA – and probably not what the EA team wants to communicate.
EA’s and EA leaders need to focus on a cost benefit analysis (CBA) of their capabilities. A CBA is part of your critical path – all the more so if your CIO reports to the CFO.
All is not lost if you haven’t come to this conclusion already. But start now to improve your EA image on a value basis.