This paper examines IT portfolio management systems as strategic frameworks for evaluating and optimizing technology investments. It explores the fundamental concepts of portfolio-based IT management, the business case driving adoption, and key components including investment valuation, cost analysis, and risk assessment. The paper discusses four investment categories—strategic systems, key operational systems, support systems, and high-potential projects—and analyzes implementation considerations across planning, feasibility studies, and project management. Critical evaluation reveals significant benefits in cost management and stakeholder alignment, alongside challenges including time overruns, risk identification difficulties, and maintenance costs. The analysis concludes that while portfolio management offers substantial organizational value when properly deployed, success depends on technical expertise, managerial discipline, and dynamic adaptation to organizational context.
Portfolio management in IT is a system that enables organizations to evaluate technology systems available at a point in time or planned for the future and leverage them for improvement in performance. There are different portfolio systems: application portfolio management, which deals with current IT resources, and project portfolio management, covering proposed IT investments. The IT portfolio management market is still in its early days, estimated to be worth US$15 million today. Since the concept is catching the attention of information technology specialists, the portfolio management tools market is projected to expand rapidly.
Forrester Research claims that the market will grow to over US$400 million by 2008, while others such as the Meta Group are even more optimistic, predicting growth to US$480 million by the end of 2005. Gartner Research has claimed that about 70 percent of its clients are working with some form of IT portfolio management system, especially in the last eighteen months (CIO Information Network, 2004).
One of the major reasons for the exponentially growing interest in the portfolio approach is technology advancement. The 1990s witnessed companies in many fields invest in and acquire technology at a rapid pace, leading to considerable gaps between investment and implementation. Companies found that it took substantial time for new IT investments to be installed and used regularly within the organization, by which time new technologies or upgrade versions had emerged, requiring further incremental investments. This led to wastage of resources and failure to achieve projected results.
The decline following the crash of IT markets across the world since 2000 forced top management at all companies, large and small, to cut budgets for IT spending and demand greater justification from IT managers for new investments (CIO Information Network, 2004). Consequently, IT managers began making centralized evaluations of resources on hand and determining their value before planning for new systems. IT portfolio management emerged as a powerful tool that enables Chief Information Officers to make informed decisions on investments and determine what could be done with past investments.
Increased productivity is perhaps the major factor drawing IT managers toward comprehensive portfolio systems. The IT department can aim to achieve more at lower costs, which directly contributes to company bottom lines. For example, British bank Abbey National achieved 20-30 percent higher programmer productivity by using portfolio management, as documented in a Forrester Research Report. An even more compelling driver is that portfolio systems demonstrate return on investment within months rather than years, which is typical for most investments (CIO Information Network, 2004).
The concept of IT portfolio management stems from the basic management principle that investment decisions should be based on perceived returns. In traditional businesses such as manufacturing, infrastructure, and trading, investments are made based on the value they provide to the firm. Real estate, financial instruments, equities, and commodities are managed in portfolios, allowing investors and managers to maximize returns by selecting from a range of investment options and providing flexibility to make discrete or comprehensive investments based on risk-return profiles.
The attributes of a rational IT investment stem from assessment of available resources and business requirements, both current and future. From the portfolio management perspective, a potential IT investment should have most of these attributes: functionality, interoperability, scalability, portability, reusability, availability, and serviceability. Above all is integration—the alignment of the new investment with existing systems. An investment idea, systems, and implementation may be excellent, but without proper integration, the expected value may not be realized. Fresh investments and modifications in existing resources may be essential to ensure integration of new projects.
When organizations evaluate proposals for IT investments, the first question typically concerns the value such investments will bring to the business. Therefore, the portfolio approach demands evidence of business value, requiring a good understanding of how the IT investment impacts current business dynamics. One basic step is to establish the relationship between the IT initiative and business requirements and processes, the criticality of the proposed system, creation or upgrading of IT infrastructure, and internal and external consequences. Total business value is the sum of benefits from these elements and can be supported by intangible benefits.
Another key measure is the financial value of the investment. This requires in-depth financial analysis involving computation of return on investment, internal rate of return, net present value, and cost-benefit analysis. If projected benefits meet or exceed professional financial norms, the project is more likely to be approved (Hochstrasser & Griffiths, 1990).
Several costs are incidental to IT systems, many of which must be incurred regardless of whether benefits are realized. Costs fall into tangible and intangible categories, or expected and hidden categories. IT expenditure is generally split into development and operational costs, with further subdivision into hardware, software, installation, operating and maintenance, networking, security, training, and environmental costs. The portfolio approach seeks to identify all costs in advance and monitor spending alongside returns. Cost control and reduction can improve profitability, making this area crucial in IT portfolio management.
Four investment categories have been identified within the portfolio approach, enabling measurement of every IT investment in terms of strategic value to the business (Sullivan, 1985).
Strategic systems provide innovation and irreversible changes in business conduct, ultimately giving competitive advantage to combat market forces. The high level of risk involved requires unstructured decision-making, making results difficult to predict or quantify.
By streamlining and leveraging existing processes, businesses can derive more value and justify investments already made. This triggers review of the need for fresh investments, and it may be possible to postpone or eliminate new investments. These systems have relatively straightforward decision-making requirements.
Designed to eliminate unnecessary business processes and simplify complex functions, these systems are generally continuously upgraded as benefits are immediately realized and investment levels are not significant. Risks are relatively lower, making decision-making simpler.
High-risk projects arising from considerable research in new areas and involving major investments and radical process changes fall in this category. While risk is high, so is future benefit, making these important elements in the IT portfolio. Decision-making typically takes considerable time as projects require review and approval by internal and external stakeholders.
Portfolio-based IT management can impact business at the national level. For instance, the United States has special provisions for portfolio-based IT management in its Information Technology Act, aimed at successful management of the entire spectrum of technology investments, covering the country's infrastructure and firm-specific IT portfolios. The approach concerns stewardship of the full range of IT investments and ensures greater response to changing needs of people and businesses. A typical portfolio-based IT management framework encompasses key factors relating to design, sourcing, implementation, and maintenance of IT systems.
The tendency to view IT as distinct from core business remains prevalent in many organizations, leading to misalignment between IT objectives and business objectives. When IT and business functions lack alignment, expected benefits from IT do not materialize. In fact, an incoherent approach can lead to cost escalation and lowered efficiency. IT portfolio management addresses this issue from the conceptual stage of projects, ensuring IT projects are implemented with shared commitment within the statutory framework. Strategic alignment involves collaborative decision-making for key projects, stakeholder commitment, internal accountability, resource allocation for project challenges, and alignment of project requirements with common IT infrastructure.
New IT investments present a double-edged sword—they can contribute significantly to organizational development or result in resource wastage. The portfolio approach provides a platform for identifying potential benefits and drawbacks. A comprehensive IT planning process ensures involvement of state authorities, business managers, and funding agencies before deciding on investment style and quantum. Decisions are more likely to succeed in the long run when new IT investments are approved after thorough baseline assessment of the agency's business requirements and existing IT portfolio.
Portfolio management emphasizes continuous assessment of computing power, network infrastructure, data management, applications, and deployment of emerging technologies for organizational improvement. This exercise provides insight into whether the organization is capable of implementing the investment program and deriving expected benefits. More importantly, it highlights the extent of internal and external defense mechanisms within the organization to overcome challenges likely to arise during implementation.
Since portfolio-based strategies are based on time-tested theories and practices, they allow organizations to rank IT projects based on required parameters. For instance, critical projects can be expedited without affecting overall investment balance or strategy. Organizations can avoid implementing projects in isolation, thus eliminating integration problems that could undermine investment purpose. This approach is ideal for meeting dynamic business demands and providing infrastructure to support service delivery to relevant markets.
As the portfolio principle is built on maximizing returns and value, it ensures that organizations undertake detailed feasibility studies before deciding on investments. A typical study identifies alternatives, allowing organizations to choose the best option after understanding risk-return profiles. A further step is developing prototypes resembling the initiative on smaller scales with short-term horizons. With prototypes, pilot studies can be conducted, and if results are satisfactory, investments can proceed with greater confidence. This helps correct pitfalls encountered during pilots, greatly increasing chances of achieving investment objectives (Tjan, 2001).
Review of the current portfolio of IT applications is important for formulating future strategies. Current applications such as human resources, financial management, and manufacturing may not be priority areas for future investments and will continue functioning as such. However, IT investments will always be part of future strategy as technology changes compel constant system upgrading. Thus, IT investment strategy can provide competitive edge that makes significant differences in today's competitive marketplace.
One key trend in IT is outsourcing of one or more functions to realize various benefits. Organizations contract external agencies to complete jobs in exchange for fees. Outsourcing widely believed to reduce costs and provide access to external expertise; even government agencies in advanced countries have adopted it, indicating tangible benefits. However, considerable controversy exists regarding whether organizations truly save costs through outsourcing. Research shows that outsourcing provides expected cost savings only under certain circumstances and can actually impose hidden cost burdens. Recent research demonstrates that large firms offering high-value outsourcing contracts actually delivered negative returns on investments over four-year periods (Strassmann, 2002). This uncertainty creates dilemmas about whether organizations should outsource and to what extent. The portfolio management approach supports this decision since its goals mirror outsourcing—cost reduction, quality enhancement, reduced project failure risk, and implementation of strategic objectives.
Research over several years on IT strategies across companies worldwide suggests that IT initiatives suffer from three major deficiencies: (a) failure to identify entire project risks at financing time; (b) failure to assess cumulative risk on the existing IT portfolio; and (c) overlooking that different IT projects require different managerial approaches (Applegate et al., 1999). Implementation risk addresses what portfolio changes would occur after project completion. The portfolio approach recognizes that project implementation risk underlies investment failure, requiring detailed risk analysis.
Three key dimensions confront new investment proposals. First is project size: higher investment levels carry greater risk, and large project failures have devastating effects on IT portfolios and entire businesses. Second is technology experience: organizations with multiple systems face invariant technology risks in new projects. Such risks often do not surface until after commitment and expenditure occur. For example, new software systems may be incompatible with internal applications, rendering them useless. Third is project structure: since IT projects span multiple departments, modifications at different stages create integration problems. Organizational changes during implementation can jeopardize projects.
In the United States, the Information Services Board (ISB) is responsible for ensuring that common-user state IT infrastructure is capable and flexible to meet ever-changing public needs, governmental initiatives, and technological change. The portfolio approach has resulted in steps helping governments upgrade and meet IT requirements consistently. The ISB and Department of Information Services, coordinating with the public IT sector, have evolved threshold limits for various risks to assist in decision-making and sanctioning new projects. Two defined criteria exist—risk and severity. Risk criteria classify projects based on organizational impact, development effort, technology, and organizational capability. Severity comprises four elements: impact on the public, transparency to citizens and law, impact on the state, and consequences of not making the investment.
Portfolio management recognizes the importance of project management in successful project development. Appropriate oversight levels are chosen based on investment risk analysis. Common project management practices include assessment of systems development life cycles, quality assurance and control, systemic audits at all investment stages, and post-delivery assessment. The portfolio approach recommends extensive use of standardized and validated tools and methodologies for smooth project implementation.
The portfolio framework requires modern tools for effective project management. Four broad categories are identified: external integration tools represent communication devices linking IT teams with other organizational groups; internal integration devices ensure the whole team functions as an integrated unit for producing desired results; formal planning tools enable sequencing key tasks in advance and assess required time and resources; and formal results-control mechanisms are deployed across organizational levels for troubleshooting and monitoring project progress.
Within the IT portfolio, projects are classified as high structure-low technology, high structure-high technology, low structure-high technology, and low structure-low technology. Project structuring falls within top management's purview, while technology rests with IT managers. High structure-low technology projects are relatively easier to manage and may not require specific internal IT expertise. Risk profiles are simple, and projects stand good chances of quick execution. High structure-high technology projects are inherently more complex, requiring IT and general management expertise combined. Since outputs are well-defined in advance, implementation presents few problems. However, after investment and implementation begin, sudden realization may occur that technology is inadequate or superficial, causing project failure.
Low structure-low technology products present lower risks but can fail due to lack of focus and direction. Managerial skills alone are insufficient; formal planning tools may be required for on-time completion. Low structure-high technology projects are driven by technical strengths but lack well-defined outputs, presenting difficulties. These projects generate many output options, and agreement among all users on a particular option is critical. Strong technical leadership and sound internal integration are vital for satisfactory progress.
"Six major obstacles and deployment considerations"
"Net benefits and forward-looking assessment"
You’re 71% through this paper. Sign up to read the remaining 2 sections.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.