Modern Enterprise Portfolio Management
Blog: Brian's Blog - Enterprise Strategy, Architecture and Management
Added “mho” to interesting discussing on the Enterprise Architecture forum this morning. Below is the base premise I started with for creating a hierarchical portfolio which is acted upon in each enterprise from observation.
If, as presuppose IT is part of Enterprise, then asking IT or Enterprise Capability is moot. If however, once recognizes the context switch we often go through doing these discussing you’re left with the following:
- Information Management Capabilities are a Enterprise Capability; Database Management is a unique configuration of multiple assets (people, software, hardware, etc.) that create one instance that capability. This is where the Enterprise Portfolio Management R&D I’ve been doing is headed. imho a Capability is defined as the ability to achieve a desired result from an action. It is not the actual action itself (potential vs kinetic energy). The exercising the capability often entails employment of a unique configuration of assets (people, process, technology classes).
- There can be multiple configurations of assets that create such a capability
- Assets can be combined in different capabilities to create different capabilities
- Time, Money, and People are dynamic assets ( Time is a self perishable/consumable asset; Money is a mutable asset as well success measure in Western Culture, it is often used as the medium of exchange for other assets; People are assets with unique properties and competencies that can increase or decrease in value based upon the social-economic-technological ecosystem they operate within.
- Information, Knowledge, and Wisdom hierarchy of asset value is time/context dependent (e.g., the Knowledge of how to build buggy whips has depreciated over time and current social-economic-technological ecosystem they operate within).