Business Architecture is never as critical as during times of great change. Great change shifts the very enterprise structures on which we usually rely to manage most other change. It can alter organizational structures, such as during mergers, acquisitions, joint ventures, and restructurings. It can alter process structures, such as during major system implementations, corporate initiatives, and regulatory imperatives. While times of sweeping change are unavoidable, the quality and speed with which we manage change determines our success.

A business capability defines “what” a business does at its core. This differs from “how” things are done or where they are done. Business capabilities are the core of the business architecture(i). Before I go further, let me say that this is not an article on the importance of the business capability or capability mapping. If you have doubts about this, read some of the other posted articles or white papers on the topic to build your familiarity. This article is for those of you who already understand the value of business capability mapping and need to go to the next stage.

Many companies are considering or beginning a Business Architecture (BA) initiative. Most likely in the early stages of the initiative, it is treated as “exploratory” in nature or perhaps as a “pilot” project. Various BA approaches are analyzed, articles and books are reviewed and training classes are attended. After some serious examination of the available information, it is necessary to put forward a business case for the “strategic” BA initiative. At the BrainStorm conferences, many attendees are asking “How do you build a business case for Business Architecture (BA)?