Situation Analysis: The complexities of the current economic climate demand sophisticated, flexible management of information technology (IT) investments. The key is to treat IT investments as part of a portfolio and adopt the methodologies of financial portfolio management.
One main benefit of this approach is that it can be applied at varying levels from very basic to extremely sophisticated. Individual organizations can apply portfolio management at the level of sophistication appropriate to their situations. Small organizations, or those in relatively stable situations, can remain at a fairly basic level, while Fortune 50 companies often become very detailed, leveraging complex financial models and management techniques.
In many cases, organizations vary the level of portfolio management sophistication depending on the type of investments under consideration. For example, the “core” investments in a portfolio may not be analyzed in the same depth as “venture” investments.
A second key benefit of IT portfolio management is its introduction of the concept of a management life cycle – with a beginning, a middle, and an end – for each portfolio investment. Great financial managers often know what will drive them to exit an investment even before they buy into it. In contrast, all too often, IT managers do not recognize that software and processes have a life cycle. The result is that, although hardware is refreshed and replaced on a regular schedule in many organizations, software and processes often long outlive their usefulness.
A third important benefit is that portfolio management encourages a regular review of investments. Currently, many IT organizations (ITOs) conduct a single annual review of their investments as part of the annual budget process. The sudden market decline that marked the US economy’s entry into the new millennium forced many CIOs to revise their budgets midyear.
|Other Recent META Reports|
The Hidden Costs of Handheld Devices
Order Your IT Investment Portfolio Lean, Well Done
Tackling The Instant Messaging Tiger
We believe this experience will become the norm in the future. Economic conditions will change too quickly to allow CIOs the luxury of a single annual review of their IT investments. Although events of the magnitude of the 4Q00 capital market slowdown are not likely to happen often, other smaller but still significant events happen almost constantly in markets – and reacting adequately to them requires a much more flexible approach than traditional management and budgeting enables. Companies that wait for the next fiscal year to plan and budget a new IT project to take advantage of a sudden market opening – or to cancel a project when a market suddenly closes – are likely to miss important opportunities and be outmaneuvered by more agile competitors that seize the competitive advantage.
However, shifting investments without planning – by simply reacting to every market blip – is equally wasteful. What the ITO needs is a more flexible method of planning and management that continues throughout the year, rather than being concentrated on a month or two at the end of the summer.
The CIO needs to review various IT investments based on the appropriate cycles per investment class, keeping in mind external drivers, such as changing economic and technical conditions. For projects, portfolio reviews should be tied to project milestones and reasonable points in time to balance across projects and programs. For various IT assets, portfolio rebalancing should be dictated by a combination of asset life cycles, technology evolution, changes in the business, and normal audit/budgeting cycles. However, portfolio review must be balanced with other important business activities – CIOs cannot spend all their time reviewing investments and budgets.
Triggers can help maintain this balance. In the stock market, an investor may set a high and low trigger on a stock – when it drops below the low trigger, the investor may consider buying, and when it reaches the high trigger, the investor will sell. Similarly, the ITO can use both financial and technology triggers to alert the CIO of changing conditions that have a direct impact on IT assets and planned projects.
For instance, many organizations have been slow to move to Windows 2000, in part because of slowing economies balanced against the significant cost of the desktop hardware upgrades they need to make. The CIO and senior business management can set a trigger in the form of a benchmark price for a PC class. When that PC market price falls below that benchmark, it is a sign that the CIO may want to revisit the issue of the Win2000 upgrade and possibly start a full-scale rollout. This, of course, is oversimplified – a decision on accelerating the Win2000 rollout would actually be based on numerous triggering events. Part of the value of using triggers is that once senior IT and business management defines them for each IT asset, a lower-level person can be assigned to constantly monitor them, reporting to the CIO when triggers are reached. When enough of the Win2000 triggers are reached, the CIO knows it is time to revisit the issue.