Professional Documents
Culture Documents
EXECUT I V E S U M MA RY
CIOs have faced lean economic times with regularity over the past four decades, and they will inevitably
face lean times again — it isn’t a question of whether they will happen but when. Forrester advises
CIOs to base budget cuts on the impact to the business and to IT productivity, not on some misguided
perception of equitable cuts across all areas.
TABLE O F CO N T E N TS N OT E S & R E S O U R C E S
2 Evaluate Spending Categories To Identify Forrester draws on its experiences with IT
Potential Savings Opportunities management for this report.
3 Vary Your Cost-Reduction Techniques By
Budget Category And Impact Related Research Documents
7 Some Considerations Cut Across All Budget “Managing IT When Times Get Tough”
Categories March 25, 2008
© 2008, Forrester Research, Inc. All rights reserved. Forrester, Forrester Wave, RoleView, Technographics, TechRadar, and Total Economic Impact
are trademarks of Forrester Research, Inc. All other trademarks are the property of their respective companies. Forrester clients may make one
attributed copy or slide of each figure contained herein. Additional reproduction is strictly prohibited. For additional reproduction rights and
usage information, go to www.forrester.com. Information is based on best available resources. Opinions reflect judgment at the time and are
subject to change. To purchase reprints of this document, please email resourcecenter@forrester.com.
2 Budget Adjustments For CIOs In Lean Economic Times
For CIOs
· It is a jargon-free way to characterize the reason for spending. While the budget detail may
be unknown to business executives, the itemized costs roll up into categories that make sense to
any executive: new capabilities, efficiency measures, operational expenses, etc.
Average percentage
Budget category Considerations of IT budget
New IT investments:
Projects that deliver new business These projects were likely conceived
capabilities and approved before the lean times 20%
began.
IT MOOSE:
Maintenance and smaller Maintenance budgets are often
enhancement activity against based on previous year with little 15%
applications year to year scrutiny.
· Successful cost reduction techniques will vary by category. Some categories of cuts are cost-
avoidance — deferring projects that deliver new business capabilities, for example. Operational
cuts may hurt today’s revenues, while everything else is likely to fall somewhere between those
two ends of the spectrum.
· Halt projects. Suggest that the CEO or CFO halt projects that haven’t started or defer
acquisitions until a review of all planned projects is complete. This has the effect of canceling
nice-to-have projects, while crucial projects will resurface for appeal.
· Slow projects. Evaluate whether it is feasible to slow down in-flight projects that can’t be
canceled, based upon position within the project life cycle. Slowdown tactics may include
reducing staff (shift staff to accelerated projects), terminating contractors, and deferring
significant hardware and software purchases to later dates. Use the slower project pace
productively — refine the formal requirements definitions, model alternative (perhaps cheaper)
solutions, and improve the efficiency of other labor-intensive/high-impact activities such as
developing more complete test scripts, data, and processes; improving production turnover; and
writing more effective operational documentation.
· Prepare to advise. Prepare information that will enable intelligent decisions on active and
planned efforts — including projected financial impact (revenue/savings), timing (when
financial impact materializes), cost, and burn-rate of resources, etc. Act as an advisor to the
CFO and business management on the dependencies and synergies of coupling certain efforts
if they go forward, but defer the actual decisions to cut to business management. Propose
alternatives to more expensive approaches, such as software-as-a-service (SaaS) options in lieu
of purchasing packaged applications.
· Look beyond cuts. Don’t just use the information to focus on cuts — help the CFO and business
leaders to identify opportunities to accelerate new revenue opportunities, reduce business costs,
delay the burn-rate of long-term projects, and defer or halt projects that are not cost-focused.
· Reduce staff intelligently. When looking at the option to reduce project staff, consider retaining
project management generalists — a good project manager can switch between projects or
straddle multiple projects with the right combinations of staff. Prune positions carefully — you
may have put your most talented staff on an aggressive technology project that is now being
canceled — don’t penalize your best staff for taking a challenging assignment.
· Focus on near-term cost reduction or avoidance. Accelerate projects that will avoid near-term
expenses. For example, virtualization of smaller servers may enable you to avoid hardware
purchases, decrease licensing costs, or avoid hiring systems administrators. Migrating the last
application from a “burning” database engine could avoid software license maintenance fees for
the coming year.
· Identify labor-intensive areas. Theoretically at least, the largest efficiency improvements should
be possible in the areas that consume the most resources. For example, look at application-
testing processes — testing occurs on every project and enhancement, and test data generation,
test set-up, and test execution can be extremely resource-intensive.
· Scrutinize all proposals. Take a jaded view of all IT proposals — if they can’t pass internal IT
scrutiny for truth and conservative estimation of savings, they’ll never pass business scrutiny.
IT must get in line with its business peers and make the best business case possible using
conservative estimates, then take its place among business units for the budget ax.
· Stop the madness. Some maintenance queues are stuffed with enhancements to which users
have an emotional, rather than business-benefit attachment. To separate the wheat from the
chaff, consider cutting all application activity off to a bare minimum level or to the level that
internal staff or service-level-based contracts can cover. Make sure this action is supported by or
emanates from a mandate from senior business management.
· Spend to save. The early adopters of APM tools estimate an average of 20% increase in
productivity through the use of an application repository created and maintained through the
APM tool. But the tools require investment and implementation cycles that can span several
months, so consider how to measure and report the benefits of increased IT productivity to
satisfy any subsequent detractors of the technique.
Operational Costs Of Applications And Services Including Data Center And Networking
Data center costs aren’t very malleable — driven as they are by physical equipment and locations.
Similarly, networking costs can also be difficult to change as they are based on capacity and quality of
service (QoS). As targets for cost-cutting over the years and as an indication of the level of maturity,
operations groups tend to run fairly lean. However, software licenses and maintenance agreements
can proliferate due to the same lack of scrutiny as application maintenance budgets — it is easier to
just pay the bill than track down the number of people still actively using myriad software licenses.
Techniques to consider:
· Defer upgrades. Defer nonessential hardware and software upgrades unless they contain
specific features that are critical to newly re-approved business plans.
· Re-assess. Re-assess telecom service costs and contracts and outside services for data centers
such as off-site data storage.
· Cancel or defer upgrades. Cancel or defer upgrades until the economy improves.
· Upgrade selectively. Upgrade only those departments that require new equipment.
· Reduce service. People are creatures of habit, immediate gratification, and convenience. But how
much would the volume of help desk calls decrease if the callers are charged, or even tracked and
reported? How many of the calls are business-critical issues? End user support costs are closely
tied to services levels and the service-delivery approach, such as use of desk-side technicians
where users expect this. Use tough messages from the CFO to get business users to reconsider the
service levels they require. Balance the savings and impact carefully however — don’t let lower
levels of support impede revenue opportunities.
· Reassign the highly skilled. High-skill positions such as experienced enterprise architects
with long tenure in the company know both the business and technical environments. As such,
they will be costly to replace when the downturn ends. Instead of reductions in force, consider
reassigning highly skilled staff to more productive assignments on accelerated projects to retain
key staff while reducing the demand for resources on key projects. Since staff is retained, cost
savings materialize through deferred hiring on the accelerated projects.
· Create a SWAT team. The highly experienced staff can serve other functions, such as a special
weapons and tactics (SWAT) team member to lead expense-reduction hunting exercises in other
areas within IT and business areas.
· Get informal. Cut back the number of formal trainees and select candidates to institute a “train-
the-trainer” program in which attendees go to formal classes and then teach internal staff to
reduce tuition, travel, and expense costs.
· Bring it on. Bring instructors on-site to reduce the travel and expense costs of flying and
housing several students — the threshold for breakeven can be as low as several students.
· Get and stay competitive. Understand whether your wages are competitive — if they are, make
it public knowledge. People will look to greener pastures less if they believe they are fairly
paid. If your pay rates are on the high side, then publicize that fact to avoid unwanted attrition.
Consider reducing the average percentage of pay increase — while holding performance reviews
and salary increases on time.
· Calculate the true cost of attrition. Consider the full costs of unwanted attrition — recruiting
costs often run 20% or more of annual salary. Consider the cost of lost business and technical
familiarity and knowledge. Compare those costs plus salary increases to bring your wages up to
competitive wages on the open market before risking excessive levels of attrition.
· Reduce staff if you must. Thin productive staff as a last resort, and cut by function and value.
Staff salaries exceed 30% of the IT budget and are an obvious possible cost-cutting opportunity.
But cutting staff often translates to reduced IT capacity. When cutting, realize that not all staff
are created equally — generalists who can do many tasks may have more value in lean economic
times than specialists who often come with higher price tags.
R E C O M M E N D AT I O N S
· Timing is everything. Measure the “when” of budget cuts as fervently as you measure
the “how much.” Lean economic times today demand relief within weeks or months, not
years. Chart out when savings will really accrue — several small savings across the year may
prevent one large cut that occurs later in the year.
· Should your organization be a wolf among sheep? Should you and can you adopt a
contrarian position to budget cuts? In lean economic times, most of your competitors will
throttle back — is now the time for your firm to accelerate and grab market share?
ENDNOTES
1
To determine the average percentage breakdown of the IT budget, Forrester polled 317 technology decision-
makers in the May 2007 Global IT Governance And Steering Committee Online Survey.
2
Especially in the financial services industry, the early adopters of application portfolio techniques are
experiencing significant increases in productivity and reductions in the cost of existing applications. See the
January 7, 2008, “APM Trends: Board-Mandated Cuts To The IT Budget Spur Global Bank To Adopt APM”
report.
3
Just 24% of companies surveyed employ a zero-base budget strategy, which requires every expenditure to be
justified annually. See the March 30, 2007, “Application Maintenance Budgets” report.
45523