What is Business Architecture?
I was a contributor to the development of Microsoft’s "Business Architecture" offering in 2005. Since then Synaptus has been engaged in performing several Business Architecture Services engagements for Microsoft. so that means we do technical work, right? Or that Microsoft is selling some application in their Business Architecture Services offering? No and no.
In my conversations with business executives there is a lot of confusion about what Business Architecture is. Business Architecture provides the link between the strategy of a business and what a business actually does to accomplish its strategy. At the highest level, it isn’t about process, technology, or people. The whole point is that by describing what a business does and where there are gaps in ability to achieve the strategy in terms of capabilities, management can more easily decide where to focus its efforts.
Enterprise Business Architecture defines business architecture as:
"what the enterprise must produce to satisfy its customers, compete in a market, deal with its suppliers, sustain operations and care for its employees."
"Enterprise Business Architecture defines the formal link between the enterprise business strategy and the results predicted from supporting strategic initiatives. "
"A comprehensive framework used to manage and align an organization’s business processes, Information Technology (IT) software and hardware, local and wide area networks, people, operations and projects with the organization’s overall strategy."
"business architecture serves as the interface between the needs of the enterprise as reflected in its work and the IT solutions that facilitate that business. "
Nexient has the best definition I found, although it is applied specifically to government:
"Business Architecture provides a disciplined approach to the alignment of programs, services, and processes with the strategic goals of government. It is a formal, structured mechanism for evaluating the current state of programs, services and processes against the desired state, and for giving decision-makers the information they need in order to direct resources - human, financial, technical - to the best effect."
So its not about technology, its about the business. Here are some keys concepts to wrap your head around business architecture:
1. Strategy is difficult to execute unless you can clearly articulate what a business has to do to accomplish it and then align all the efforts of the business with that strategy. For example, increasing profitability is a complex thing to accomplish in a business. Business Architecture is a way of understanding this complexity in your business. It can overcome "silo-myopia" to help define what is the next most important place to focus process, technology, and people efforts to accomplish your strategy.
2. Business Architecture involves models of the business. Because people live at different levels in the organization, have different responsibilities, and may have very different areas of expertise, not everyone has the same perspective of what is important to the business. Without a way to model and gain agreement on what the business is about, strategy is difficult to execute and conflict will arise when prioritizing efforts.
3. It involves extending your view to articulate your strategy and customer capabilities.
4. Because it talks about what you do, not how you do it, it remains stable even when the implementation changes.
What is fascinating is that most Business Architecture projects are run by IT departments because they need this clarity in order to build systems that will concretely manifest themselves. However, when IT owns the Business Architecture you essentially have the technology people defining the strategic direction of the company.
One final quote from Enterprise Business Architecture:
"No one will ever consider building a complex structure such as a skyscraper, automobile, ship or airplane without blueprints based on a complete set of integrated architectures. However, we consistently build, merge, reorganize, and run enterprises without a set of equivalent blueprints or architectures. "
Who owns the blueprint for the future of your business?