Professional Documents
Culture Documents
Justifying & Managing: IS/IT Investments
Justifying & Managing: IS/IT Investments
MSSI 2022S
Structure Demand-side Supply-side
3
Survey Findings of Current Practices in IS/IT
Investment Management
Average
• Relatively low levels of
Management Average satisfaction
Satisfaction –
more
Management
Satisfaction –
• Post-implementation
successful less successful investment evaluation and
Practice group group review is the factor that
Portfolio 49% 33% differentiates the two
management
groups most
Business case 44% 19%
development • Overall levels of satisfaction
with both business case
Identifying and 44% 20% development and benefit
quantifying benefits
identification are about
Identifying and 69% 46% 30% (~similar to the
quantifying costs
percentage of IS/IT projects
Evaluation and 36% 7% deemed successful)
review
5
Investment and Priority-setting Policies
• IS/IT investments have traditionally been evaluated like capital projects such as
plant and equipment assuming a fixed cost offset against net revenue over the
life of the application. However, many IS/IT investments are now more like ‘new
business ventures’ or business initiatives where the financial aspects of the
outcome can only be guessed and the technology is only one component of a
major change program …
• … in most cases not all demand can be satisfied and priorities must be set. If no
consistent justification approach is followed, the more beneficial applications
may well be deferred, allowing those that make a lesser contribution to proceed.
• … the same principles and practice should govern the ‘go–no go’ decisions for
individual applications ... The only additional factor, assuming that systems are
not sequentially dependent, is the amount of resource consumed. The limiting
factor is normally people, in quantity or quality (particular skills or knowledge),
… priority setting should enable maximum return from the use of that resource.
6
Justifying and Evaluating IS/IT Investments:
Problems in IS/IT Investments
• Research findings: >90% of large organizations required some form of business case to
justify the funding of IS/IT investments
– only 59% subjected to a formal investment appraisal
– 60% felt that they were valuable in gaining funding approval
– <40% were satisfied that the case identified the appropriate benefits, secured commitment to deliver the
stated benefits
• Grindley summed up the mistrust of conventional justification methods:
– 83% of IT directors admit that the cost–benefit analyses supporting IT investment proposals are a fiction;
– CEO: “It’s like there is a spontaneous conspiracy to exaggerate the benefits.”
• Most technology investments are justified on the back of applications:
– Infrastructure’s investment are generally carried out in advance and the return can only be counted based
on subsequent application’s benefit
– However, it is difficult to associate infrastructure’s investment with application’s benefit due to accounting
practices (~IT lifetime, etc.)
– The full costs of the investments are not included (costs incurred by business departments in specifying,
testing, and implementing the system; costs of making the business changes)
7
Justifying and Evaluating IS/IT Investments:
Financial Appraisal of IS/IT Investments
• Payback
• Accounting ROI
• Discounted Payback
• Discounted Cash Flow – IRR
• Discounted Cash Flow – NPV
• Discounted Cash Flow – Profitability Index
8
Classifying IS/IT Investments –
business case effectiveness
9
Classifying IS/IT Investments:
Types of Applications
12
Benefits Management
• Benefits Management: the process of organizing and managing such that
potential benefits arising from the use of IT are actually realized.
• Why ‘benefits management’?
– One of the factors that differentiates successful from less successful
companies in their deployment of IS/IT is the management resolve to
evaluate IS/IT investments before and after they occurred.
– Post-implementation review must be carried out on a high percentage
of projects to identify whether (i) they were carried out as well as
possible and (ii) whether the benefits claimed (or possibly different
benefits) were achieved or not.
13
The Context of Benefits Management
The Context Inputs to Benefits
Management Process
• Why is the investment being made—
what is causing the organization to
change and how critical to its future is
the successful management of the
changes? (the benefit drivers)
• What types of benefit is the
organization expecting from the
investment overall—to reduce costs,
improve operational performance,
gain new customers, create a new
capability, etc.?
• How will other activities, strategic
initiatives, business developments or
organizational issues affect the
particular investment either to
facilitate or inhibit its progress and
outcome? (the organizational context)
14
Benefits Management Process
1.Identifying the target benefits & who should
be responsible for its delivery
2.Determine the changes required for delivery
of each benefit and how the IS/IT
development will enable the changes and
benefits to occur
3.Carry it out and adjust it as necessary
4.Review what was/not achieved to maximize
benefit & learn for future investments
5.Further benefits often become apparent only
when the system has been running for some
time and the associated business changes
have been made
15
Justifying Business Apps Investments
Justification ‘rules’ should allow for differences in
the rationale for implementing apps in each
segment!
• Support
– Any allocation of the resources should be argued
primarily on economic, ROI
– Some discretion can be left to local management
via free-market strategy
• Key Operational
– The business unit should be the final arbiter
• Strategic
– The ‘go/no go’ decision is based on how directly it
relates to the business objectives
• High Potential
16
Justifying Infrastructure Investments
• The main aims of infrastructure’s investments
are:
– to enable the business apps to perform
successfully
– to create appropriate capabilities for the general-
purpose use of IT tools in the short/medium term
– to anticipate longer-term (uncertain) organization
& business needs
17
Assessing & Managing Investment Risks:
Check List
Technical risk factors Financial risk factors Business Change & Organizational
risk factors
Complexity of the system Size of the investment Senior mangement commitment to the
functionality project
Technical novelty – to the Project duration User commitment of resources and
organization & the supplier knowledge
The number of system interfaces Degree of confidence in all the Stability of the organization and key
and systems being replaced elements of project costs staff
Certainly & stability of the Confidence in the evidence for The extent of changes to business
business requirements the investment benefits processes and practices
Technical skills of the project Appropriateness of project The number of departments, functions
team cost control mechanisms and business staff involved and
affected
The extent of changes needed to Rate of change of the external The degree to which organizational &
the IT infrastructure environment role changes are needed to realize the
benefits
The degree to which the system The business criticality of the Existing change management capability
can be prototyped/piloted areas affected by the system & experience
18
Variations in Risk Patterns for Different Types of
Apps Investments
STRATEGIC HIGH POTENTIAL
Minimized by limited
scale/scope
ORGANIZATIONAL ORGANIZATIONAL
due to vested interests
Financial & technical risks are Low financial risks & technical
addressed by strict application risks minimized by use of
of methodologies proven technologies
24
This week’s material
• …
25
Next week’s material
• …
26