A recently published article entitled “Business Capability Architecture Is the Tie that Binds All” discussed how to use business capabilities to tie business strategy, enterprise change, and project portfolio prioritization. We concur that strategy, enterprise change, and portfolio management are managed more effectively using business architecture, and agree that capabilities are a component of business architecture. However, we view the article’s notion of “business capability architecture” as being incomplete. We will discuss why this concept is incomplete and how it can be extended through value mapping.

By William Ulrich & Jim Rhyne

A recently published article entitled “Business Capability Architecture Is the Tie that Binds All” discussed how to use business capabilities to tie business strategy, enterprise change, and project portfolio prioritization.[i] We concur that strategy, enterprise change, and portfolio management are managed more effectively using business architecture, and agree that capabilities are a component of business architecture However we view the article’s notion of “business capability architecture” as being incomplete. We will discuss why this concept is incomplete and how it can be extended through value mapping.

Technology has produced many wonderful and useful things and has changed the way we work and play. It has also produced a good many solutions for problems that nobody thinks are important. Or, the technology based solution to the problem has a greater cost than the value that would be realized from the solution.