Enterprise architecture in and of itself has no real value. The value of enterprise architecture is in supporting and enabling the business activities of an organization. This may seem obvious but, over the years I have seen countless enterprise architects fail to get budget for their initiatives or tools. In some cases, teams are disbanded or are perceived as a discipline for the IT teams only.
To change that perception you need to change the way you present the value of enterprise architecture to the business, executives, and colleagues. You need to be able to help them connect the dots between what you do and why they can’t possibly achieve their business objectives without the knowledge and expertise you bring to the table. Watch the video where suggest how starting with what the business wants to achieve is typically a great first step.
To do this, you need to be able to provide some concrete information. It doesn’t have to be purely quantitative. You can share info like days saved, risk averted, shorter timescales, or better quality – usually others in the business can then convert them to meaningful numbers for themselves.
Three actions to build a case:
- Connect enterprise architecture to business drivers. For example, if the company wants to launch new products, enter new markets, or acquire companies, it must understand how enterprise architecture is going to help, and you as an enterprise architect need to demonstrate how what you do supports those goals.
- Relate cost to value. For example, a $500k investment in tooling for EA would not be considered expensive if the business understood the company could save an additional $5m over the next 12-24 months.
- Use past failures to illustrate. It may not always be easy to quantify the future, but the past can also help. Use examples of project overrun, regulatory fines, late deliveries, or customer complaints. Where you can, identify quantifiable costs and illustrate how enterprise architecture could have helped prevent or reduce risks/costs.
If you really can’t quantify what enterprise architecture brings to the party, then it is quite likely that you will not get budget approval.
Remember, purchasing without a known return is not an investment; it is a gamble. Often the reason why enterprise architects choose cheap tools rather than premium professional tools is because their organization is only willing to gamble a small amount of money. In reality those organizations would be best saving that money until they understood the value, and then invest wisely in the right tools, technologies, and teams.
What do you think of the recommendations? Share by leaving a comment below.