I talk commonly to architects that are under pressure to create a cloud strategy. Or an SOA strategy. Or a BPM strategy. Or an XYZ strategy. Many will add up a few of these point strategies and call it an overall technology strategy. It’s good to know where we’re going, but is this the right way to do it? No. The problem is that this is technology-focused tech strategy. You can see it in the way we describe applications according to their dominant technology. We call them event-driven apps, or RFID apps, or whatever. Instead, to have a business-focused tech strategy, the starting point should be an understanding of what drives business outcomes. What would that look like?
Business architecture — an important and maturing domain of enterprise architecture — is changing the conversation between business people and technologists. Rather than centering on individual siloed applications, business architecture, at its best, centers conversation on the design of business outcomes and what it takes to achieve them. Within the realm of business architecture, models like business capability maps provide strong mechanisms for understanding and designing a business.