Book a Demo!
CoCalc Logo Icon
StoreFeaturesDocsShareSupportNewsAboutPoliciesSign UpSign In
Download
29547 views
1
2
3
4
5
United States General Accounting Office
6
Executive Guide
7
GAO
8
9
February 2001
10
11
12
13
Maximizing the Success of Chief Information Officers
14
15
Learning From Leading Organizations
16
17
18
GAO-01-376G
19
20
21
Preface
22
Information technology (IT) has become integral to providing
23
government services, and the management of information in the
24
federal government has moved out of the back office and off the
25
mainframe into the home and office and onto the Internet. As the
26
federal government fully embraces e-commerce and other leading-edge
27
implementations of IT that benefit citizens, leadership in managing
28
the government«s information resources becomes of paramount
29
importance. The development of new service approaches and the
30
enhancement of old ones in this new information era require the
31
active participation of information management organizations from
32
the beginning.
33
The efficient, effective, and innovative use of information
34
technology requires a level of leadership and focus that goes
35
beyond what would be provided in a technical support function.
36
Congress recognized the need for greater leadership in information
37
management and technology in the Clinger-Cohen Act of 1996, which
38
mandated the position of chief information officer (CIO) for
39
executive departments and agencies. This act and other laws define
40
the general responsibilities of the CIO and many of the processes
41
required to manage information in the federal government.
42
Virtually all of the major executive agencies have appointed
43
CIOs, and many have taken positive steps toward the implementation
44
of important information management processes specified by law. To
45
reap the full benefits of information management reform, federal
46
agencies must utilize the full potential of CIOs as information
47
management leaders and active participants in the development of
48
agency strategic plans and policies. The CIOs themselves must meet
49
the challenges of building credible organizations, and developing
50
and organizing information management capabilities to meet agency
51
mission needs.
52
This guide is intended to assist federal agencies in maximizing
53
the success of CIOs. Principles and practices gleaned from the case
54
studies presented in our guide offer concrete suggestions on what
55
agency executives can do to ensure the effectiveness of their CIO
56
organizations. The guide does not address all of the
57
responsibilities which fall to federal agency CIOs - only those
58
which have parallels in the private sector. Moreover, we find that
59
practices used by federal agency CIOs tend to differ from those
60
used by leading organizations. We did not study the reasons for
61
these deviations specifically, but they likely result from the
62
context in which federal CIOs operate. Both operational and
63
structural aspects of the CIO«s environment can vary significantly
64
in the federal sector versus the private sector. Rather than dwell
65
on differences, our study shows that there is much common ground
66
between public and private CIO organizations on which to build
67
efforts for improvement. The specific key conditions and strategies
68
described in this guide can be used as suggestions for federal CIOs
69
to apply or adapt to their environments, where appropriate.
70
We would like to thank the Private Sector Council and the
71
leading practice organizations we selected for our study, which are
72
listed on page 59, for providing us with the information about
73
their practices and assisting us in producing this executive guide.
74
We would like to thank members of GAO«s Executive Council on
75
Information Management and Technology for their comments and
76
suggestions in the development of this guide. We would also like to
77
thank the individuals who provided helpful comments on the exposure
78
draft of this guide.1
79
This guide was prepared under the direction of Lester Diamond,
80
Assistant Director, Information Technology Management Issues, who
81
can be reached at (202) 512-7957 or [email protected]. Key
82
contributors were Tamra Goldstein, Sondra F. McCauley, and Tomas
83
Ramirez.
84
85
David L. McClure Director, Information Technology Management
86
Issues
87
1 Executive Guide: Maximizing the Success of Chief Information
88
Officers (Exposure Draft) (GAO/AIMD-00-83, March 31, 2000).
89
Contents
90
Page
91
92
93
94
Federal Information Management Reform
95
The rapid pace of technological change and innovation in the
96
current information age poses wide-ranging opportunities for
97
improved information management2 and enhanced performance in
98
achieving agency missions and goals. At the same time, however, the
99
proliferation of technology has brought with it a range of thorny
100
issues surrounding managing and integrating complex processes,
101
computer equipment, and telecommunications networks. In its
102
oversight role, Congress has established a series of laws to define
103
the role of information management in government and to mandate
104
basic processes to manage the government information technology
105
(IT) investment. This section provides a brief overview of that
106
legislative history.
107
The federal government«s management of its information resources
108
to date has produced mixed results. Consistent with reform
109
legislation, agencies have taken constructive steps to implement
110
modern IT strategies, systems, and management practices and
111
policies directed toward achieving cost savings, increasing
112
productivity, and improving the timeliness and quality of federal
113
service delivery. To the extent that the nearly $27 billion in
114
annual planned obligations for information technology can be
115
invested and managed more wisely, federal programs will operate
116
more effectively and at less cost.
117
For years, Congress has been working to increase the
118
effectiveness of information and technology management in the
119
federal government. An early effort was the Brooks Act, enacted in
120
1965, which called for centralized oversight of federal information
121
technology acquisitions by the General Services Administration
122
(GSA). The Paperwork Reduction Act of 1980 (PRA) applied life cycle
123
management principles to information management and focused on
124
reducing the government«s information-collection burden. To help
125
accomplish this, PRA designated senior information resources
126
manager positions in the major departments and agencies with
127
responsibility for a wide range of functions including information
128
resource planning, budgeting, organizing, controlling, training,
129
and ensuring the absence of duplication in information systems. PRA
130
also created the Office of Information and Regulatory Affairs
131
within the Office of Management and Budget (OMB) to provide central
132
oversight of information management activities across the federal
133
government.
134
In the 1990s, Congress enacted additional laws holding agencies
135
accountable for effective management of public information
136
resources. In particular, the Chief Financial Officers (CFO) Act of
137
1990 and the Government Management Reform Act of 1994 spelled out
138
an ambitious agenda to remedy the government«s lack of useful,
139
relevant, timely, and reliable financial information. For the
140
government«s major departments and agencies, these laws
141
(1) established senior-level CFO positions, (2) required annual
142
financial statement audits, and (3) set expectations for more
143
modern systems to support integrated management of budget,
144
accounting, and program information. The Government Performance and
145
Results Act of 1993√ commonly known as GPRA or the Results Act
146
√required that agencies set strategic goals, measure performance
147
toward those goals, and report on their progress. Effective
148
implementation of the Results Act hinges on agencies« ability to
149
produce meaningfully integrated information to manage performance
150
and measure results.
151
In this guide, information management refers to all aspects of
152
the management of all information resources, including technology,
153
funds, human capital, and management processes, as well as the
154
underlying information. IT refers to technology used to support the
155
management of information.
156
Further, amendments to the PRA in 1995 required that agencies
157
indicate in strategic information resources management plans how
158
they are applying information resources to improve the
159
productivity, efficiency, and effectiveness of government programs,
160
including improvements in the delivery of services to the
161
public.
162
With this increased focus on agency accountability also came
163
recognition of the need to elevate the agencies« information
164
management positions to more strategic, executive, levels,
165
comparable to the CFO positions created in 1990. The Clinger-Cohen
166
Act of 1996 amended the PRA, renaming and elevating former
167
information resources manager positions to executive-level CIOs who
168
report directly to the agency head and have information management
169
as a primary responsibility. The new information management leaders
170
are accountable for not only the range of information management
171
activities outlined in the PRA, but also for more strategic IT
172
functions such as developing architectures, managing portfolios,
173
and measuring the performance of information technology
174
investments. Among other things, the Clinger-Cohen Act also (1)
175
required senior executive involvement in IT decision-making, (2)
176
imposed much-needed discipline in acquiring and managing technology
177
resources, (3) called for the redesign of inefficient work
178
processes before investing in technology, and (4) repealed the
179
Brooks Act, eliminating GSA«s central acquisition authority.
180
Primary procurement responsibility now rests directly with federal
181
agencies.
182
Together with a number of other laws enacted over the past
183
several years to foster improvements in such areas as financial
184
management, acquisition, and computer security, this legislation
185
discussed above composes a statutory framework for achieving
186
performance-based management and accountability in not just
187
information management, but overall federal management.3 (Appendix
188
I provides a list of these key federal laws affecting information
189
management.) As the executive leaders for information and
190
technology management, federal CIOs have a key role in helping
191
their agencies fulfill many of the provisions embodied in this
192
management reform framework.
193
Even with the guidance provided by OMB for establishing the new
194
information technology management leadership positions, agencies
195
face distinct challenges in effectively positioning federal CIOs
196
and supporting organizations to ensure that information management
197
adds value in their business/mission performance .4 CIOs in the
198
federal sector face structural and cultural hurdles generally not
199
found elsewhere. Some of these additional challenges are described
200
in the final section of this guide.
201
3
202
Managing for Results: The Statutory Framework for
203
Performance-Based Management and Accountability
204
(GAO/GGD/AIMD-98-52, January 28, 1998) and Managing for Results:
205
The Statutory Framework for Improving Federal Management and
206
Effectiveness (GAO/T-GGD/AIMD-97-144, June 24, 1997).
207
4
208
OMB guidance on implementing federal CIO positions includes
209
Memorandum for the Heads of Executive Departments and
210
Establishments, ƒImplementation of the Information Technology
211
Management Reform Act of 1996,≈ M-96-20, April 4, 1996; and
212
Memorandum for the President«s Management Council, ƒWhat Makes a
213
Good CIO?,≈ June 28, 1996.
214
215
216
Overview of Fundamental Principles
217
The basis for this guide is the belief that federal agencies
218
could benefit from examples set by a few leading organizations
219
whose CIO organizations have gained a reputation for outstanding
220
information management in their enterprises. This work is intended
221
to provide pragmatic guidance that federal agencies can consider in
222
determining how best to integrate CIO functions into their
223
respective organizations. Our target audience includes senior
224
federal executives and managers, although our observations can also
225
provide insights for senior information management officials
226
throughout the public and private sectors. (Appendix II provides
227
more details on the objectives, scope, and methodology of our
228
work.) Based on interviews with private-sector and state CIOs and
229
other research, we have developed a framework of critical success
230
factors and leading principles. The balance of this guide describes
231
this framework and its application to CIOs in the federal
232
government.
233
CIOs of leading organizations we interviewed described a
234
consistent set of key principles of information management that
235
they believed contributed to the successful execution of their
236
responsibilities. These principles touch on specific aspects of
237
their organizational management such as formal and informal
238
relationships among the CIO and others, business practices and
239
processes, and critical CIO functions and leadership activities.
240
The specific nature of these principles varied depending on the
241
organization«s mission, size, culture, and other factors, but each
242
underlying key principle was consistently observed.
243
The CIOs interviewed considered these principles instrumental
244
because they address critical organizational and operational
245
aspects of the CIO«s role. Notably, the principles address senior
246
executives« responsibility for creating an effective management
247
context for their CIOs, as well as the CIOs« responsibilities for
248
building credibility and organizing information technology and
249
management to meet business needs. The practices are not new ideas
250
in the general management of organizations, but rather are the
251
application of well-founded principles in the maturing area of
252
information technology and management.
253
These principles are most effective when implemented together in
254
a mutually reinforcing manner. As ad hoc efforts, each individual
255
principle addresses a single aspect that is necessary, but is not
256
sufficient for success by itself. The failure to execute a single
257
principle may render the others less effective. Further, although
258
there is no precedence among the principles, organizational
259
conditions may make it more feasible to address one principle
260
before another. For example, the chief executive officer (CEO) may
261
ƒposition the CIO for success≈ in advance of hiring a new CIO while
262
the other principles await the CIO«s attention.
263
Figure 1 illustrates the six fundamental principles described by
264
the CIOs interviewed during the development of this guide. In
265
addition, for each principle, several key characteristics of
266
organizations that successfully execute these principles are
267
listed. These key characteristics can provide insights into what
268
constitutes successful CIO organizations.
269
Figure 1: Six Principles and Key Characteristics of CIO
270
Management in Leading Organizations
271
272
Evaluating the intent of the six principles, we observed that
273
they naturally fell into three distinct sets, which we refer to as
274
critical success factors. Figure 2 illustrates the six principles
275
and their relationship with the three critical success factors and
276
their respective organizational foci.
277
Figure 2: Critical Success Factors and Organizational
278
Relationships
279
Critical Success Factors
280
281
Principles
282
283
Organizational Foci
284
285
286
a COO-Chief Operating Officer
287
Understanding the six principles in terms of critical success
288
factors is particularly useful because of characteristics that are
289
shared by principles within the same success factor. Following is a
290
brief description of each critical success factor.
291
Align Information Management Leadership for Value Creation
292
The principles under the first critical success factor, ƒAlign
293
Information Management Leadership for Value Creation,≈ advocate the
294
need to recognize the role of information management in creating
295
value and positioning the CIO for success; both of these principles
296
address issues of senior executive support. Both principles require
297
that the leaders of the enterprise embrace the critical role
298
information management can play in the success of the organization
299
and the leadership role the CIO must play in order for information
300
technology and management to meet its potential. The first
301
principle addresses the acceptance of this premise by senior
302
executive management, and the second ensures that the CIO has the
303
organizational legitimacy to execute his or her role.
304
Promote Organizational Credibility
305
While the first success factor refers to legitimacy at a
306
strategic planning level, this success factor addresses a more
307
operational level. The principle that addresses the need to ensure
308
the credibility of the CIO organization and the principle that
309
encourages measuring success and demonstrating results, if executed
310
successfully, will lead to the confidence of those with operational
311
responsibility in the enterprise. Without credibility, the CIO
312
organization will struggle to be accepted as a full participant in
313
the development of new organizational systems and processes.
314
Execute CIO Responsibilities
315
The last critical success factor, ƒExecute CIO Responsibilities≈
316
addresses the need to organize information resources to meet
317
business needs and to develop the associated human capital. These
318
two principles provide the foundation for the CIO«s effectiveness
319
in carrying out the CIO organization«s specific responsibilities.
320
Once executive management endorses the centrality of the CIO
321
organization and becomes a partner in the development of new
322
systems, the CIO organization must execute its responsibilities
323
successfully.
324
The last section in figure 2, ƒOrganizational Foci,≈ illustrates
325
how both principles within a single critical success factor require
326
the same organizational units to collaborate in their execution.
327
Both principles within a critical success factor also focus on the
328
same organizational units as targets of their implementation. For
329
example, in the case of, ƒPromote Organizational Credibility,≈ both
330
principles rely on the collaboration of senior executives and
331
division heads for success and have as their target the senior
332
management of the enterprise.
333
The common features within a critical success factor can become
334
especially significant as the CIO, and other players, plan the
335
execution of the six principles described in this guide. As this
336
group plans its strategy, it can utilize the commonality among
337
principles to link initiatives and utilize the synergy between
338
related efforts. For example, while organizing information
339
resources to meet enterprise needs and developing human capital are
340
distinct initiatives, they share extensive areas of commonality.
341
Executing both principles in
342
Page 10 GAO-01-376G CIO Executive Guide
343
conjunction with each other can create opportunities for
344
efficiency and effectiveness not otherwise available.
345
Finally, the organization of principles into critical success
346
factors illustrates the extent to which the work of a successful
347
CIO must extend throughout the enterprise. In particular, the role
348
that the CEO and other senior managers play in ensuring the success
349
of the CIO should be noted. While it is the responsibility of the
350
CIO to execute the specific responsibilities of his or her
351
position, it became clear to us during our case studies that the
352
successful CIO relies extensively on both vertical and horizontal
353
relationships within the enterprise in order to carry out these
354
responsibilities.
355
This executive guide includes examples from our case study
356
organizations as well as information from selected federal
357
organizations, which helped us confirm the applicability of our
358
findings to federal government experience. At the conclusion of
359
each principle, we provide a case study to describe the principle
360
in practice at one of the organizations we visited, as well as
361
strategies to consider when implementing the principle. Although
362
this guide focuses on fundamental practices rather than detailed
363
guidance, the examples illustrate and complement much of the
364
specific guidance contained in similar and related GAO documents
365
cited in appendix III.
366
367
368
The Federal CIO Environment Today
369
The CIO position in the federal government is still evolving.
370
Agencies are learning how a CIO can help improve effectiveness and
371
efficiency and better realize the benefits of their information
372
resources. Current federal CIOs are learning how to carry out their
373
responsibilities in the federal environment with all of the
374
incumbent expectations and constraints. Both the agencies and the
375
CIOs are working to meet the letter and intent of the Clinger-Cohen
376
Act and associated legislation effectively. The principles offered
377
in this guide are intended to provide insight into what CIOs at
378
leading organizations consider critical to their success, and
379
provide advice to federal CIOs and senior agency management as they
380
work to improve the use of information technology and management in
381
the federal government.
382
The federal CIO faces an environment that includes many of the
383
elements encountered by CIOs interviewed for this guide. At the
384
same time, the federal CIO faces additional challenges as a result
385
of specific legislative responsibilities (e.g., records management
386
and defined contracting requirements). The federal CIO is also
387
subject to a funding process that is more complex and uncertain
388
than in most other organizations. The effect of the appropriations
389
process and the highly distributed management structures found in
390
several federal agencies tend to move some of the control of
391
processes having to do with information management away from the
392
CIO. Together, these characteristics, among others, differentiate
393
the federal CIO environment from other environments. These
394
differences, and their impact on the framework developed in this
395
guide, will be discussed in the ƒUsing this Guide≈ section. The
396
following discussion focuses on the common elements among the
397
private, state, and federal sectors, and the application of the
398
framework across all three.
399
In a series of one-on-one interviews with half of the Federal
400
CIO Council, we found that federal organizations face many of the
401
same issues as their private-sector and state government
402
counterparts. Specifically, federal organizations must overcome the
403
challenges of effectively linking information technology and
404
management to agency missions, positioning and legitimizing
405
information management leadership, measuring performance, and
406
building capabilities and skills. Our meeting with five members of
407
the Federal Small Agency CIO Council and a number of independent
408
studies provide similar conclusions.5 The six principles that
409
emerged from our discussions with private-sector and state
410
government CIOs also describe the general areas that federal CIOs
411
agreed needed to be addressed. However, the specific approaches to
412
executing those principles tended to differ among the various
413
sectors.
414
The Federal Chief Information Officer: Third Annual Top Ten
415
Challenges Survey, Association for Federal Information Resources
416
Management, November, 1998; Implementing Best Practices, Capital
417
Planning and IT Investment Committee, Federal CIO Council, June
418
1998; The Impact of Change: Clinger-Cohen Act Implementation,
419
Laying the Foundation for Year 2000 and Beyond, Eighth Annual ITAA
420
Survey of Federal CIOs, Grant Thornton LLP, December 1997; and
421
IAC/CIO Task Force Draft Report, Federal Chief Information
422
Officer«s Working Group and Industry Advisory Council, July 9,
423
1996.
424
In three of the principle areas, the level to which practices of
425
leading private versus federal organizations have evolved is
426
significantly different. For example, in principle I, while leading
427
organizations generally include their CIOs in executive business
428
decisionmaking, in the federal government setting information
429
management is still often viewed as a support function rather than
430
a strategic activity. Leading organizations also consider various
431
leadership models and position their CIOs at a clear, executive
432
level, as in principle II. In contrast, federal CIO implementation
433
is in more nascent stages, lacking criteria for matching CIO types
434
with organizational needs. Further, in principle V, while leading
435
organizations are flexible in reassigning staff and structuring
436
capabilities across business and technology lines, federal staffing
437
practices and organizational structures are less flexible in
438
nature.
439
Performance measurement (principle IV) and information
440
management human capital development (principle VI) are two areas
441
that private, state, and federal CIOs all agreed must be addressed
442
in order for the CIO and the supporting organization to be
443
successful. Practices used by both the private and public sectors
444
in the area of performance measurement are still evolving. In both
445
performance measurement and human capital development, practices
446
used by the federal CIOs differed from those of CIOs in leading
447
organizations, though federal CIOs were actively trying to address
448
the issues. Differences in the approaches used probably resulted
449
from specific constraints in the federal CIO environment, including
450
a focus on nonfinancial program benefits, rather than financial
451
return on investments.
452
Credibility building, principle III, is the one area in which
453
CIOs in both the public and private sector have all adopted similar
454
practices. The precise application of the practices depended on the
455
specific contexts of their organizations, but the approaches were
456
consistent. It may be noted that this is one of the few principles
457
that CIOs may address themselves, without regard to organizational
458
constraints or CEO support. Of course, as stated earlier, the
459
effectiveness of this principle is moderated by the extent to which
460
the other principles have been implemented.
461
The following table summarizes the practices of our sample
462
organizations in each principle area and compares them with
463
practices in the federal CIO environment.
464
Table 1: Comparison of Leading Practices and Federal CIO
465
Management Practices
466
467
In terms of critical success factors, federal CIO organizations
468
tend to trail the CIOs interviewed for this guide in the ƒAlign
469
Information Management Leadership for Value Creation≈ and ƒExecute
470
CIO Responsibilities≈ factors. The successful execution of these
471
two critical success factors depends to a great extent on officials
472
other than the CIO. In the first success factor, the CIO depends to
473
a great extent on the other senior executive officers to support
474
the inclusion of the CIO in critical strategic discussions. In the
475
other factor, the federal CIO tends to be constrained by
476
organizational attributes typical of the federal sector. These
477
attributes include, but are not limited to, relatively little
478
flexibility in financial reward systems and highly distributed
479
organizational structures in a number of federal agencies.
480
This is not to say that there are no examples of progress in the
481
federal sector in either of these two success factors. The federal
482
response to the year 2000 computing challenge created an
483
opportunity in many agencies for CIO and program organizations to
484
partner in responding to specific agency mission needs. This
485
partnering took place at the senior executive level and contributed
486
to the success of the federal Y2K effort. In addition, the CIO
487
Council, the Office of Personnel Management, and individual
488
agencies have been working together to develop new approaches to
489
compensating and retaining information technology and management
490
workers.
491
It is interesting to note that the remaining critical success
492
factor, ƒPromote Organizational Credibility,≈ is executed about the
493
same within all sectors, since all sectors approach principle III
494
similarly, and no sector executes principle IV well. As noted, it
495
is within this critical success factor that the CIO is able to
496
operate with the greatest individual flexibility.
497
Table 1 indicates that a gap exists between the practices of
498
federal CIOs and CIOs of leading organizations. Areas in which gaps
499
exist should be examined carefully to understand the basis for the
500
differences as well as opportunities for greater implementation of
501
the principles. It is possible that the business context for
502
federal CIOs is sufficiently different from that of CIOs in leading
503
organizations that lessons learned may not be applicable. Some of
504
these differences are described in the final section of this guide.
505
At the same time, an understanding of the information technology
506
and management practices of leading organizations could contribute
507
to the development of improved CIO management practices in the
508
federal sector.
509
The following sections describe each of the general principles
510
and practices discovered in our work with leading CIO
511
organizations.
512
Critical Success Factors
513
514
Principles
515
Organizational Foci
516
517
518
519
520
Critical Success Factor 1: Align Information Management
521
Leadership for Value Creation
522
523
The CIO and supporting organization must have active support and
524
commitment at the very top of the enterprise or they will remain
525
limited and tangential to the business, despite their potential
526
contribution to mission accomplishment. This first critical success
527
factor focuses on the role of the senior executive of the
528
enterprise in developing a culture that includes the CIO in
529
senior-level decision making and that assumes the potential of IT
530
in creating value for the enterprise. Executive leadership is
531
essential to the successful execution of this factor.
532
A common theme among the CIOs we interviewed was that the
533
message of the importance of IT to the organization must be
534
communicated at the highest levels. Senior executives must embrace
535
the central role of technology, and the CIO must be a full
536
participating member at the table with them as business strategy is
537
discussed. This behavior begins with the CEO, who sets the example
538
for senior and mid-level executives and, through them, the rest of
539
the organization. In addition, the participation of the CIO in
540
long-range strategic planning is necessary to take full advantage
541
of the opportunities IT can provide and to ensure that the
542
technology infrastructure is in place as business strategies
543
develop.
544
545
Principle I: Recognize the Role of Information Management in
546
Creating Value
547
ƒThe CIO«s ability to add value is the biggest single factor in
548
determining whether the organization views IT as an asset or a
549
liability.≈
550
551
Instituting an effective CIO organization does not start with
552
selection or placement of an information technology and management
553
leader, nor does it begin with establishing a structure for
554
managing information resources and activities. Rather, it begins
555
with consideration on the part of executive-level managers of the
556
role of IT and how vital it is to accomplishing mission objectives.
557
It also entails thinking about ways to incorporate the information
558
technology and management leader in the executive-level management
559
structure and create an environment that facilitates
560
business/technology sharing and exchange of ideas. Moreover, CEOs
561
and governors can set powerful examples through their own strong
562
relationships with CIOs. Such relationships symbolize the
563
importance of information technology and management within their
564
organizations.
565
566
Key Characteristics
567
Senior executives have primary responsibility for setting the
568
business context for their CIOs and formulating strategies for
569
integrating information technology and management into their
570
business operations. Executives of leading organizations no longer
571
regard technology management as a separate support function and
572
instead strive to understand how investments in information
573
resources are made and how they integrate with other investments
574
and the overall business vision. These executives also increasingly
575
focus on the management, operations, program and service delivery
576
benefits, and performance of their major strategic information
577
systems. CEOs have a key role in setting the example for the rest
578
of the agency to follow in seeking to understand information
579
technology and management concepts and appreciating the strategic
580
role that information technology and management can play in helping
581
to accomplish business objectives. Viewing information and
582
technology not just as assets to manage, these CEOs assign their
583
information technology and management leaders a prominent role in
584
business decision making. Recognizing the business transformation
585
potential of IT, these executives also position their CIOs as
586
change agents with responsibility for applying technology to
587
achieve major improvements in fundamental business processes and
588
operations. With CEO support, the CIOs are in a good position to
589
have significant impact on not just IT, but the entire business
590
enterprise.
591
Following the CEO«s lead, members of the senior executive team
592
learn to value the advice of the CIO in setting business directions
593
and developing strategies for improving organizational capabilities
594
and competitiveness. They seek to embrace fundamental information
595
technology and management principles and work with their CIOs to
596
develop a shared vision of the role of IT within the business
597
context. They engage in dialogue on
598
Page 18 GAO-01-376G CIO Executive Guide
599
ways that technology can be incorporated to improve business
600
processes, outputs, and outcomes. They incorporate information
601
management as an intrinsic part of their business planning and
602
decision making processes, discussing the benefits and risks
603
associated with specific strategies for improving service, reducing
604
cycle time, or reducing costs.
605
In leading organizations, senior managers make joint decisions
606
on information resources, formulate business plans, and set
607
performance expectations. Increasingly, managers make IT investment
608
decisions based on the value of the investments to their
609
enterprises, not just to a specific business unit or function. By
610
asking strategic and operational questions at the beginning of the
611
planning and evaluation period, senior managers gain a better
612
understanding of the potential benefits and value of IT.
613
Information and technology managers in leading organizations are
614
also adopting processes that help them quantify and align projects
615
with their organizations« business planning and measurement
616
processes. They produce plans that link to overall business plans
617
and assign managers to act as liaisons between business units and
618
CIO organizations. Increasingly, managers also focus on measuring
619
reliability, responsiveness, and customer satisfaction, which in
620
the eyes of senior management are just as important as strictly
621
financial measures.
622
Leading organizations work to create environments that are
623
conducive to sharing ideas on how information technology can
624
support the businesses and vice versa. They adopt formal mechanisms
625
and structures that facilitate the ability of their businesses and
626
information technology and management leaders to understand and
627
communicate one another«s issues and work together to accomplish a
628
shared business vision. These mechanisms and structures include
629
forums, councils, and boards for discussion and exchange on
630
business and technology issues. Such forums help promote
631
organizationwide perspective and facilitate the ability to achieve
632
consensus or stakeholder buy-in to business/technology directions.
633
For example, one state has a strategic planning forum that brings
634
together major stakeholders statewide to identify strategic and
635
tactical issues, including IT issues confronting the state. The
636
state prepares a strategic planning document based on this
637
stakeholder input. This process has helped to integrate information
638
management into overall business planning by aligning IT products
639
and services with business functions and linking technology to the
640
state«s overall strategic direction.
641
To further support the business/technology collaboration,
642
leading organizations adopt a common business language, skillfully
643
avoiding technical jargon and instead using language that general
644
managers and legislatures can understand. They use analogies,
645
terminology, and processes that help fuse business and technology
646
interests and ideas together. Other strategies for
647
business/technology learning include informal activities such as
648
newsletters, presentations, reports, and service-level results
649
placed in common areas to communicate the effectiveness of their
650
CIO organizations. Leading organizations further the two-way
651
exchange of ideas and perspectives by bringing in experts from the
652
field to advise or educate managers on recent trends and
653
developments in both the business and technology arenas. Realizing
654
that attitudes, expectations, and culture seldom change quickly,
655
they plan for whatever time and resources are necessary to create a
656
common ground and organizational cohesiveness. Their efforts go a
657
long way in shoring up commitment from across the organization to
658
strategies for achieving common goals.
659
Leading organizations also focus on hiring managers who bring a
660
hybrid of business and technical expertise to the organization. One
661
large multinational corporation uses ƒtechnical facilitators≈ to
662
support its initiatives. In the past, this company had experienced
663
problems in sharing information resources. Managers in the
664
different lines of business were unwilling to share information
665
resources because each felt his or her particular line of business
666
was unique. Because technology was becoming critical to future
667
success in this business sector, top managers were increasingly
668
assigned to support and manage the company«s internal information
669
management functions. Several of the managers assigned had both
670
business and technology acumen and had the ability to raise
671
business issues from a technical perspective in a nonthreatening
672
manner. In resolving business issues, they were sometimes able to
673
identify more efficient technical opportunities.
674
675
Case Study: Recognizing the Role of Information Management in
676
Creating Value
677
Due to changes in market conditions and requirements for
678
increased productivity through using common components, a large
679
manufacturing company decided that it needed to make major changes
680
in the way it managed IT to support the business. The company had
681
outsourced its information management function, but lacked the
682
infrastructure to provide strategic direction, discipline, and
683
overall management of information management to ensure optimal
684
implementation and cost. Given this situation, the company was
685
faced with a proliferation of legacy systems and inefficient
686
business processes built around them. The company also met with
687
bureaucratic business resistance to change to a common information
688
systems environment.
689
By way of improvement, senior executives adopted a new IT
690
strategic direction and focus that tracked back to the company«s
691
business priorities¬ ƒcommon, lean and fast, global, and growth.≈
692
Senior management then hired a CIO as a change agent, reporting to
693
the Vice Chairman and the company«s senior decision making council,
694
and gave him responsibility for transforming the IT function,
695
thereby making him an enabler of the function and an integral part
696
of the business strategy.
697
The CIO recruited an IT management team that understood both the
698
business and technical sides of the enterprise. He instituted a
699
matrix management organization, creating a leadership structure
700
that provided flexibility for meeting future information management
701
needs as well as maintaining existing IT systems. The new IT
702
organization became responsible for such strategic activities as
703
participating in the development of overall business strategies;
704
prioritizing IT requirements; generating IT business plans; setting
705
technical and architectural standards; managing user interfaces,
706
outsourcing contracts, suppliers, and systems engineering; and
707
allocating IT resources. To assess performance, the IT organization
708
instituted several sets of measures that link directly to the
709
business objectives and priorities defined by the CEO in the
710
company«s strategic plan.
711
The major steps that the company took to improve, are
712
illustrated in figure 3, below.
713
Figure 3: Steps for Transforming Business Operations Using
714
Information Management
715
716
717
718
719
Defined strategic business priorities including Common,
720
Lean, Fast, Global and Growth
721
722
723
724
Executive team shared a challenging vision of the role of
725
IT
726
727
728
729
Implemented a matrix IT organization (functional and
730
operational alignment)
731
732
733
734
Established virtual organizational structure for
735
flexibility and responsiveness
736
737
738
739
740
741
742
743
Strategies to Consider
744
Instituting information technology and management as a support
745
function separate from the business is an ineffective and outdated
746
model. Leading organizations recognize the role of IT in supporting
747
mission accomplishment and seek to integrate it with business
748
operations. The following outlines the strategies that senior
749
executives in leading organizations commonly use to promote
750
information management leadership involvement in business decision
751
making and maximize the benefits from their IT investments.
752
Focus on efforts to incorporate the CIO organization into the
753
overall business by
754
755
756
757
ensuring executive leadership and commitment for the CIO
758
organization, both at the career and political levels;
759
760
761
762
embracing the CIO as a full participant of the executive
763
management team;
764
765
766
767
developing structured approaches for exploring the broad
768
range of opportunities and strategies in information technology
769
available to enhance the business; and
770
771
772
773
774
focusing technology initiatives on creating value and
775
providing the information needed by internal and external
776
customers.
777
778
Provide an atmosphere that supports executive understanding of
779
IT by
780
781
782
783
creating and using formal and informal executive
784
communication channels to make the business case for integrating
785
information management into organizationwide decision-making;
786
and
787
788
789
790
emphasizing returns and metrics that clearly link
791
information management with an organization«s business
792
needs.
793
794
795
796
797
798
Principle II: Position the CIO for Success
799
ƒThere is no cookie-cutter approach, so knowing what fits in an
800
organization is key to finding the right CIO to match with the
801
organization.≈
802
803
There is no one right way to establish a CIO position.
804
Diversities in corporate missions, structures, cultures, and
805
capabilities prohibit a prescriptive approach to information
806
management leadership. There are nonetheless a number of practices
807
and alternative strategies that senior executives in leading
808
organizations use to help define and institute their CIO positions
809
to effectively meet business needs. This section examines those
810
practices, providing pragmatic guidance that other organizations
811
can also consider in determining how best to integrate CIO
812
functions into their respective organizations.
813
814
Key Characteristics
815
Senior executives in leading organizations recognize that a
816
one-size-fits-all solution to establishing information management
817
leadership does not exist. Rather, they take responsibility for
818
ensuring that their CIO models are consistent with the business,
819
technical, and cultural contexts of their enterprises. Executives
820
do so by examining their internal environments and asking a series
821
of questions about the problems that need fixing, how information
822
technology and management can help, and how a CIO might best fit
823
within their management structures to guide technology solutions.
824
The answers to these questions help them choose from a range of
825
alternative CIO approaches.
826
Specifically, by defining mission improvement objectives, senior
827
executives determine whether their organization needs a CIO who is
828
a networking/marketing specialist, business change agent,
829
operations specialist, policy/oversight manager, or any combination
830
thereof. Studying existing IT capabilities helps define the
831
structure and responsibilities of the new CIO organization.
832
Considering the centralized or decentralized nature of the
833
enterprise helps determine the corporate CIO«s authority level and
834
how the CIO shares responsibility with other managers across the
835
agency. Further, appreciating organizational culture and change
836
readiness helps define the pace and extent to which CIOs can
837
accomplish business transformation.
838
Business executives keep in mind that initial CIO models adopted
839
should not be set in stone, but may have to be adjusted over time
840
as their enterprises grow or mature. For example, while a company
841
may need a business strategist to build a new IT capability, over
842
time another type of CIO may be better suited to sustaining
843
operations. This evolution in the CIO role is also reflected by the
844
introduction of variant leadership positions in information
845
management (i.e., chief knowledge officers or chief technical
846
officers) that diffuse responsibility across several senior-level
847
managers. For example, one industry organization that we visited
848
has multiple product line CIOs. The most senior information
849
management executive positioned at a level above these CIOs asserts
850
that he is not the ƒcorporate CIO≈ and does not want to be. With
851
the belief that one person cannot embody all the knowledge needed
852
to effectively direct information technology and management in an
853
organization, this executive uses an executive-level technology
854
committee as a forum for building consensus for IT initiatives.
855
In conjunction with determining their CIO models, senior
856
executives clearly define up front the roles, responsibilities, and
857
accountability of their CIOs for enterprisewide information
858
management, better enabling their CIOs to operate effectively
859
within the parameters of their positions vis-à-vis those of their
860
senior management counterparts (i.e., CFO, COO). Typically, CIOs
861
serve as a bridge between top managers, IT professionals, and end
862
users. CIOs provide leadership and vision, focusing senior
863
executives on highvalue information technology issues, investments,
864
and decisions. They may also serve as business change agents,
865
challenging conventional approaches and developing new methods and
866
systems for delivering mission benefits. The case study at the end
867
of this section provides an example of a CIO hired specifically to
868
help transform information management and business operations.
869
In this strategic capacity, CIOs take the lead role in
870
integrating information and technology management and performance
871
across the entire information life cycle. They are responsible for
872
such activities as planning, setting standards and policies, and
873
designing and managing architectures to guide introduction of
874
technology products and services. While not all CIOs necessarily
875
have hands-on responsibility, their purview may also incorporate
876
any or all of the operational elements of information and
877
technology management, such as data processing, infrastructure
878
management, and systems acquisition.
879
Senior executives provide their CIOs with the authority they
880
need to effectively carry out their diverse responsibilities.
881
Executives ensure this by giving the CIO a key role in IT
882
investment decision-making, providing budget control, or ensuring
883
leadership backing for information technology and management
884
programs and initiatives. Formally documenting or, in the case of
885
public-sector organizations, legislating, CIO roles and
886
responsibilities can help in managing performance and expectations
887
of both the enterprise and the CIO. For example, the position of
888
one state government CIO that we interviewed was based on a
889
specific statute establishing the CIO at the cabinet level and
890
assigning clear-cut responsibilities for funding and overseeing IT
891
operations statewide.
892
While there is no single template for doing so, senior
893
executives in leading organizations apply consistent criteria in
894
selecting their CIOs. The most obvious criterion is relevant IT
895
expertise. Rather than being technical experts specifically, their
896
CIOs intuitively understand IT principles and trends and act as
897
strategists, applying technology and approaches skillfully to help
898
resolve or overcome daunting business challenges. But even while IT
899
expertise is important, their CIOs are business managers as well,
900
with experience in administrative, financial, and corporate
901
management. Such experience better enables the CIOs to work with
902
business managers to build a shared vision for meeting mission
903
needs. For instance, one state government CIO attributed his
904
success to his breadth of experience across a variety of financial,
905
retail, and IT units, which facilitates his ability to
906
Page 24 GAO-01-376G CIO Executive Guide
907
get buy-in from stakeholders in the state. Additional
908
proficiencies critical to CIO success include leadership ability,
909
innovation and flexibility, effective communications skills,
910
interpersonal skills, and political astuteness. The weight that
911
senior executives assign to each of these criteria in selecting a
912
CIO depends on the information management leadership model and the
913
needs of the enterprise.
914
CIOs are no longer tied to a single functional unit√i.e., the
915
ƒIT shop.≈ Instead, they are positioned as senior executives with
916
the ability to strategically view and apply IT to the best
917
advantage of the enterprise. CIOs generally report to and partner
918
with their agency heads, forging relationships that ensure high
919
visibility and support for far-reaching information management
920
initiatives. As active members of the CEOs« executive teams, these
921
CIOs are well situated to provide advice and direction, integrate
922
IT with the business vision, and take part in high-level
923
decision-making. Active participation in executive processes and
924
committees facilitates the CIOs« ability to build effective
925
executive-level working relationships.
926
927
Case Study: Positioning the CIO for Success
928
In 1996, this manufacturing company instituted a CIO position to
929
help build its information management capability after deciding to
930
split its former internal IT service provider off as an independent
931
business. For years, the manufacturing company had relied on a
932
wholly owned subsidiary to provide IT products and services. With
933
minimal IT talent left in the company following the split-off, the
934
CIO had to create a new IT leadership staff.
935
The company used a consultant to search for a CIO to build the
936
in-house information management capability. Essentially, the
937
company wanted a CIO with IT expertise, strong management skills,
938
and background experience in managing large, centralized companies.
939
The current CIO exceeded their requirements. He came highly
940
recommended due to his prior success in transforming two other
941
companies and his skill in outsourcing, which would be needed to
942
manage the manufacturer«s continued reliance on information
943
technology contract services. The CIO accepted the position only
944
after obtaining senior executives« commitment to his vision for
945
transforming not just information technology and management, but
946
processes in the entire company.
947
Senior executives set the CIO up to succeed. They positioned him
948
as a member of the senior decision-making board, reporting to the
949
Vice-Chairman of the company. They gave him the flexibility to
950
bring in managers from the outside and set up a matrix management
951
organization consisting of multiple business sector CIOs aligned
952
with functional CIOs across the company, all reporting to the
953
corporate CIO. They required that any IT initiative include
954
collaboration between a sector CIO and a process-responsible CIO,
955
as illustrated in figure 4. Senior executives also made the CIO the
956
final authority on all IT budget, operations, and process
957
management issues. During the period from 1996 through 1999, the
958
CIO has been effective in lowering projected annual IT costs, for
959
1999 the total reduction was over $450 million, when taking into
960
account both cost avoidance and cost reduction, while enhancing the
961
provision of IT services to the company.
962
Figure 4: Matrix Management Organization in a Leading
963
Organization
964
965
966
Global Processes and Systems
967
968
969
970
Strategies to Consider
971
In the absence of a single model for instituting a CIO, senior
972
executives take precautions to ensure that their information
973
management leadership positions are appropriately defined and
974
implemented to meet their unique business needs. The following is
975
an outline of the strategies that senior executives in these
976
organizations use to determine the types of CIOs they need, select
977
individuals to carry out these roles, and position them as
978
effective and influential members of the senior executive
979
decision-making team.
980
Determine the CIO model by
981
982
983
984
examining the current environment and identifying what
985
the enterprise expects to accomplish through information management
986
before establishing a CIO position to lead improvements;
987
and
988
989
990
991
992
making the CIO type (i.e., business strategist, marketing
993
specialist, policy and oversight manager, operations specialist,
994
etc.) consistent with the enterprise«s mission, history, current
995
environment, culture, and change readiness.
996
997
Define clear roles and accountability for the CIO by
998
999
1000
1001
delineating CIO roles and responsibilities vis-à-vis
1002
those of other senior managers;
1003
1004
1005
1006
ensuring that the CIO has the authority needed to be
1007
effective; and
1008
1009
1010
1011
1012
documenting CIO roles, responsibilities, and
1013
accountabilities to help manage expectations and
1014
performance.
1015
1016
Select a CIO with the right skills set by
1017
1018
1019
1020
choosing someone with information technology and
1021
management expertise and the potential to help in business
1022
transformation, consistent with the CIO model selected;
1023
and
1024
1025
1026
1027
1028
ensuring that the individual also has the leadership and
1029
communications skills and other proficiencies needed to effectively
1030
carry out the CIO position.
1031
1032
Make the CIO a business partner by
1033
1034
1035
1036
having the CIO partner with other senior executive
1037
managers,
1038
1039
1040
1041
empowering the CIO to work with other senior executives
1042
to discuss and decide among alternative IT products and strategies
1043
for meeting business needs, and
1044
1045
1046
1047
ensuring that the CIO is involved in strategy discussions
1048
at the highest levels so that he or she can lead the enterprise in
1049
using information management to corporate advantage rather than
1050
merely responding to client requests.
1051
1052
1053
Critical Success Factors
1054
Principles
1055
1056
Organizational Foci
1057
1058
1059
1060
1061
1062
1063
Critical Success Factor 2: Promote Organizational
1064
Credibility
1065
The second critical success factor focuses on the CIO«s ability
1066
to establish the CIO organization as a central player in the
1067
enterprise. The legitimacy of the CIO and the CIO organization must
1068
be developed for the CEO«s message of information technology and
1069
management«s central role to be accepted and for the CIO
1070
organization to become a full participant in formulating corporate
1071
strategy.
1072
Both principles in this critical success factor pertain to the
1073
demonstration of the CIO organization as an entity that can
1074
complete critical projects successfully and contribute to the well
1075
being of the enterprise. This effort is largely the responsibility
1076
of the CIO, and the focus is lateral and downward. The CIO must
1077
create an environment in which the ability of the CIO organization
1078
to contribute to the success of the enterprise is recognized.
1079
Success, to be appreciated, has to be demonstrable and measurable.
1080
If the CIO is not able to demonstrate that he or she deserves the
1081
support of the CEO and makes a valuable contribution to the
1082
corporate mission, the CIO will not be effective as a full
1083
participant in the corporate decision-making process.
1084
1085
Principle III: Ensure the Credibility of the CIO
1086
Organization
1087
ƒWhile placement of the CIO position at a high level within the
1088
organization may carry some weight, the CIO generally must earn
1089
credibility by making things happen.≈
1090
1091
Instituting a CIO position consistent with organizational needs
1092
and finding a capable leader to fill the job are no guarantee of
1093
CIO success. Rather, the burden of ensuring information technology
1094
and management effectiveness shifts from senior executives to the
1095
CIO and his or her supporting organization. Given the relative
1096
newness of the position vis-a-vis the rest of the business, the CIO
1097
is faced with having to gain the attention and respect of managers
1098
at all levels across the organization and build the support and
1099
cooperation needed to effectively execute the information
1100
management leadership role. The following is a discussion of the
1101
strategies that CIOs in leading organizations use to legitimize
1102
their roles and successfully collaborate with their business
1103
counterparts to guide IT solutions to meet mission needs.
1104
1105
Key Characteristics
1106
CIOs in leading organizations recognize that providing effective
1107
information management leadership and vision is a principal means
1108
of building credibility for their CIO positions. CIOs do this in a
1109
number of ways. Foremost, they do not manage IT in a vacuum, but
1110
rather make sure that the information management program is well
1111
integrated with what senior executives want to accomplish. CIOs
1112
work with their executive peers to jointly produce a vision
1113
educating senior managers on the strategic value of IT, providing
1114
advice and direction, and setting expectations of what can be
1115
achieved. CIOs express this vision in business rather than
1116
technical terms, and in such a manner as to generate enthusiasm,
1117
buy-in, and motivation for managers to strive together toward the
1118
achievement of common goals. Further, CIOs participate on executive
1119
committees and boards that provide forums for promoting and
1120
building consensus for IT strategies and solutions. We found this
1121
to be true for each of the case study organizations that we
1122
visited. Having achieved senior management interest and backing,
1123
CIOs can leverage this support as needed to help ensure cooperation
1124
for carrying out information technology and management and business
1125
change initiatives across the enterprise.
1126
Effective CIOs, and their supporting organizations, do not set
1127
out to force their ideas and solutions on their business
1128
counterparts. Instead, they seek to bridge the gap between
1129
technology and the business by networking informally, forming
1130
alliances, and building friendships that help ensure support for
1131
information technology and management. CIO organizations then work
1132
with rather than for the businesses, getting them involved in
1133
projects and driving ownership and accountability to line
1134
management, rather than to the IT shop. For example, in one case
1135
study, the state legislature placed the CIO organization in charge
1136
of managing the planning, funding, and implementation of a project
1137
to develop a single telecommunications network to serve the state«s
1138
entire education community. Rather than a technical challenge, the
1139
project has been a huge coordination effort, requiring that the CIO
1140
organization overcome rivalries and achieve the commitment and
1141
cooperation of traditionally autonomous education sectors.
1142
CIOs retain the support of their business colleagues by
1143
following through on commitments to effectively lead business
1144
transformation projects, provide needed IT products and services,
1145
and train and educate the user community. Through it all, CIOs
1146
strive to maintain open communications and build trust. They do so
1147
by being accessible to the businesses, listening to user feedback,
1148
and focusing on user needs.
1149
CIOs recognize that balancing short-term successes with
1150
longer-term business change initiatives is key to keeping their
1151
business customers satisfied. In the initial months of tenure, CIOs
1152
set out to understand their enterprises« needs and tackle tough
1153
issues (i.e., runaway projects and crisis situations such as year
1154
2000 management) that demand immediate attention or could pose
1155
immediate obstacles to success. In the short term, they also focus
1156
on building relationships, addressing business imperatives (i.e.,
1157
process streamlining and consolidation), and demonstrating success
1158
by promptly providing highimpact products and services (i.e.,
1159
commercial off-the-shelf software and desktop equipment) that allow
1160
them to achieve positive and visible accomplishments fairly
1161
quickly. CIOs recognize that showing interim results concurrent
1162
with more protracted efforts such as multiyear systems
1163
developments, ƒbig-ticket≈ infrastructure projects, or business
1164
process reengineering can have significant positive impact on CIO
1165
credibility.
1166
Often, CIOs outline plans of attack or roadmaps to help guide
1167
them in effectively implementing their short- and long-term
1168
strategies. Documenting their courses of action helps them manage
1169
schedules and expectations and provides baselines against which to
1170
assess progress and performance. These CIOs are careful not to get
1171
caught in the cycle of continual planning, but take steps to ensure
1172
effective progression from planning to implementation. They return
1173
to their plans iteratively, updating them as progress is made and
1174
business needs evolve.
1175
Finally, CIOs in leading organizations recognize that there is
1176
too much going on in the area of information technology and
1177
management for them to absorb all of the issues alone. Rather than
1178
allowing their technology ideas and programs to stagnate, they keep
1179
abreast of changes in the fast-paced environment that might be
1180
applied to enhance capability and improve mission performance in
1181
their own organizations. They do so through avid reading, working
1182
with vendors, and following market directions. CIOs also benchmark,
1183
partner with, or seek advice from successful peers and competitors
1184
on initiatives that provide opportunities for exchanging ideas,
1185
sharing capability and expertise, and achieving mutual benefits in
1186
the larger information technology and management community. For
1187
example, one state CIO with whom we met said that he values the
1188
1189
GAO-01-376G CIO Executive Guide Page 31
1190
guidance received from a CIO advisory board of private industry
1191
representatives, convened by the governor to facilitate learning
1192
from business organizations. This CIO also partners with a major IT
1193
corporation on a project to acquire standard desktop equipment for
1194
all agencies under the governor«s purview. Participation in key
1195
councils, advisory groups, and government, trade, and professional
1196
associations such as the Industry Advisory Council and the National
1197
Association of State Information Resource Executives is also useful
1198
for exchanging ideas, sharing information, and identifying new ways
1199
to meet common challenges.
1200
1201
1202
Case Study: Ensuring the Credibility of the CIO
1203
Organization
1204
This state«s Justice Network (JNET) illustrates how
1205
implementation of many of the practices discussed in this section
1206
has enhanced the credibility of the CIO and his supporting
1207
organization. JNET is a highly successful project started by the
1208
CIO organization enabling agencies to jointly develop a single,
1209
secure, web-based system to support administration of criminal
1210
justice across the state. The project responds to the governor«s
1211
priority for consolidated agency projects, thereby ensuring
1212
high-level support for CIO efforts. The CIO organization conceived
1213
the idea for JNET after receiving multiple requests from criminal
1214
justice agencies for funding to develop redundant systems. The
1215
organization identified the joint project as a good opportunity to
1216
save on costs, share information, and reduce redundancy and errors
1217
by making it possible to enter new offender information only once
1218
as subjects proceed through the criminal justice process.
1219
Historically, the state«s justice agencies have been highly
1220
autonomous and distrustful of outsiders. Prior attempts to get the
1221
agencies to work together failed. IT managers recognize that
1222
success with the current initiative goes a long way in increasing
1223
CIO credibility with the state agencies.
1224
The CIO organization launched JNET by bringing together
1225
stakeholders from across the state in a series of meetings over the
1226
course of 2 months to establish a vision for a shared system that
1227
would also meet individual justice agency information needs. Under
1228
executive order, a senior-level leadership committee, including the
1229
CIO, is responsible for establishing JNET policy, direction, and
1230
standards and for authorizing the release of JNET funds. A steering
1231
committee consisting of justice agency representatives works with
1232
information management professionals and consultants to refine
1233
project details. Its biweekly meetings provide a good opportunity
1234
for the CIO organization to build relationships with the state
1235
agencies and for agency representatives to get acquainted and learn
1236
about one another«s operations and data resources. With central
1237
responsibility for controlling contracts and funding drawn from the
1238
agencies« budgets, the CIO organization is credited with being the
1239
ƒglue≈ that holds JNET together. A JNET office, established to
1240
administer the project on a day-to-day basis, also reports directly
1241
to the CIO.
1242
Under CIO guidance, JNET has been planned as a multiphase,
1243
multiyear development effort with interim products and results. The
1244
CIO organization has helped agencies successfully complete a pilot
1245
phase to prototype initial JNET content and applications, also
1246
demonstrating the CIO organization«s ability to help deliver on
1247
commitments. Three additional phases involve testing the system«s
1248
basic data-sharing function and adding new capabilities such as
1249
data importing, on-line processing, and document management.
1250
Initially, the justice agencies thought JNET was a bad idea; agency
1251
representatives were pessimistic and merely went through the
1252
motions of working together. They posed such resistance that at one
1253
point, the CIO had the lieutenant governor make a surprise visit to
1254
a steering committee meeting to oversee project progress,
1255
demonstrate senior management support, and ensure agency
1256
cooperation toward meeting common objectives. Once the agencies saw
1257
the operational prototype and the project«s potential, they
1258
realized that their individual sacrifices had paid off.
1259
Today, JNET continues to grow in scope and popularity. Along
1260
with it, CIO credibility has increased. The CIO organization is
1261
currently working with several counties to help link them with
1262
JNET. Next steps include instituting JNET at the local level and
1263
ultimately partnering with other states to construct a nationwide
1264
justice network. JNET«s success has served to legitimize and
1265
increase the value of the CIO function to its business
1266
counterparts. Now, other agencies, including the departments of
1267
Health and Public Welfare, also want to work with the CIO
1268
organization on similar cross-functional information management
1269
initiatives.
1270
1271
1272
1273
Strategies to Consider
1274
While senior executives are responsible for creating the
1275
environments and positions likely to ensure CIO success, it is the
1276
responsibility of the CIOs themselves to make that success a
1277
reality. Regardless of all the promising skills, strategies, and
1278
technologies they may bring to bear, no CIO can be effective
1279
without first building credibility with business executives, IT
1280
professionals, and user communities alike to ensure commitment and
1281
support for their information management leadership and
1282
initiatives. The following practices, commonly used by CIOs in
1283
leading organizations to build credibility, can also be considered
1284
and applied by CIOs in federal departments and agencies to better
1285
legitimize their positions and help ensure success in their
1286
individual business/cultural environments.
1287
Provide information management leadership and vision by
1288
1289
1290
1291
ensuring that the vision encompasses senior management
1292
priorities,
1293
1294
1295
1296
educating top managers on the value of information
1297
technology and management in helping to accomplish mission
1298
objectives,
1299
1300
1301
1302
articulating the vision in business terms to facilitate
1303
line management understanding and achievement of buy-in,
1304
and
1305
1306
1307
1308
1309
using senior management discussion and decision-making
1310
forums as opportunities to build consensus for IT programs and
1311
initiatives.
1312
1313
Establish effective working relationships by
1314
1315
1316
1317
networking informally and forming alliances with other
1318
senior managers to help defuse potential opposition and build
1319
commitment to new technology directions;
1320
1321
1322
1323
getting managers from the business side of the enterprise
1324
involved and accountable for information management
1325
projects;
1326
1327
1328
1329
fulfilling commitments to provide effective IT goods and
1330
services; and
1331
1332
1333
1334
1335
establishing open communications and feedback mechanisms,
1336
such as surveys and questionnaires, as a way to build
1337
trust.
1338
1339
Balance quick successes with long term impact by
1340
1341
1342
1343
setting priorities and distinguishing between short term,
1344
high-impact initiatives and longer term objectives that require
1345
more vested interest; and
1346
1347
1348
• outlining a plan or strategy for accomplishing these
1349
priorities in an efficient and effective manner.
1350
Leverage external information technology and management
1351
expertise by
1352
1353
1354
1355
keeping abreast of technological change and incorporating
1356
new products and strategies in the enterprise«s IT program as
1357
appropriate,
1358
1359
1360
1361
forming partnerships and building off of the success and
1362
expertise of external CIO peers, and
1363
1364
1365
1366
networking and participating in forums in the larger
1367
community to debate and identify ways to address common information
1368
technology and management issues and concerns.
1369
1370
1371
1372
1373
1374
Principle IV: Measure Success and Demonstrate Results
1375
ƒMeasurement determines what one pays attention to. The things
1376
that are measured become relevant; the things that are omitted are
1377
out of sight and mind.≈
1378
1379
In many organizations the value of information technology and
1380
management is considered intangible¬difficult to measure and mired
1381
in terms of ƒsoft dollars≈ or ƒstrategic assets.≈ For this reason,
1382
in the past, few organizations embarked on programs to measure the
1383
effectiveness of IT systems. However, it has become increasingly
1384
evident that without a measurement process where results can be
1385
demonstrated, not only is information management at a disadvantage
1386
when competing for scarce resources, but also when making its case
1387
in support of efficiency and effectiveness initiatives. For the CIO
1388
organization to be viewed as part of the business, a structured
1389
process needs to be in place to measure success and demonstrate
1390
results to the organization. This section discusses the approaches
1391
that leading organizations use to measure performance and
1392
results.
1393
1394
Key Characteristics
1395
While there is no standardized approach to performance
1396
measurement, leading organizations strive to understand and measure
1397
what drives and affects their businesses and how to best evaluate
1398
results. These organizations have generally struggled with
1399
identifying and adopting measures to assess the value of IT, but
1400
have been able to put some measures in place to help demonstrate
1401
performance. They use measures for a variety of purposes. The
1402
measures are a vehicle for communicating with senior management and
1403
stakeholders in the areas the organization deems important.
1404
Measures also serve as vital management and decision-making tools,
1405
providing information that can be used to make improvements in
1406
business outcomes and service delivery.
1407
Many managers told us that the measures that capture the most
1408
attention from senior management are simple ones¬or at least simple
1409
in terms of how they are expressed. In a number of instances, the
1410
organizations we visited used uncomplicated terms to communicate
1411
measures, but the underlying concepts were quite involved and
1412
required a good understanding of IT and business fundamentals.
1413
These organizations collapsed a lot of information into a form that
1414
effectively communicated the success or failure of information
1415
technology and management activities and, in the case of the
1416
latter, expanded on the issues and supplied additional information.
1417
For example, one international organization, involved in several
1418
product lines, measures its performance in line with the following
1419
organizational business priorities:
1420
1421
1422
1423
Maximize performance (i.e., improve service and reduce IT
1424
and management costs)
1425
1426
1427
1428
Improve business processes (i.e., IT projects and
1429
E-commerce)
1430
1431
1432
1433
Increase team contributions
1434
1435
1436
1437
Create a leading-edge electronic communications
1438
process
1439
1440
1441
Even though these measures seem simple, a considerable amount of
1442
time, effort, and data are involved in amassing and assessing the
1443
results tied to these business priorities.
1444
To establish joint ownership for performance management,
1445
organizations strive to construct measures jointly with their
1446
stakeholders, customers, managers, and CIO staff. They work
1447
together to achieve a common understanding of goals, metrics, and
1448
anticipated outcomes that are easy to understand but are aimed at
1449
adding value. Managers told us that performance measurement systems
1450
work best when combined with established measures that reflect
1451
customer/stakeholder needs and the activities of employees that are
1452
directly involved in information management. The CIO organization«s
1453
responsibility does not end with the establishment of measures, nor
1454
does the CIO organization have sole responsibility for
1455
technological success. As a practical matter, those responsible for
1456
judging the success of programs and their supporting functions
1457
should agree on the measures used and become involved in monitoring
1458
the outcomes.
1459
Although approaches vary, leading organizations develop measures
1460
with a focus toward improving not only internal IT performance but
1461
also external relationships with technology users and the overall
1462
business. Organizations balance various technical measures to
1463
ensure that IT products and services are deployed in the most
1464
effective and efficient ways and lead to desired business results.
1465
They focus on monitoring short- and long-term IT measures that
1466
directly affect business activities and produce real business
1467
value. This means that IT activities must be directly related to
1468
company relationships with customers, clients, and suppliers, and
1469
also affect business results, such as direct costs or market
1470
share.
1471
Leading organizations use performance measures that focus on
1472
business outcomes such as customer satisfaction levels, service
1473
levels, and in some instances total requests satisfied. For
1474
example, one state agency commissioner requires that his
1475
departments develop tactical plans for all areas, not just IT. All
1476
executives participate in the planning process. The performance
1477
measures are broken down to meaningful levels as a way of holding
1478
the ƒIT shop≈ and other departments accountable for the services
1479
they provide. IT goals and objectives are incorporated into the
1480
plans and IT performance outcomes are provided to the commissioner
1481
and his executive staff on a quarterly basis. This exercise has
1482
served to build credibility and help demonstrate the value that IT
1483
adds to the organization. The existence of performance measures has
1484
also made a difference in how agencies behave because the
1485
documentation they provide serves to make them accountable.
1486
To properly collect and analyze information, leading
1487
organizations develop measurement systems that provide insight into
1488
their IT service delivery and business processes. The establishment
1489
of an information feedback system allows organizations to link
1490
activities and functions to business initiatives and management
1491
goals. This feedback, in turn, leads to increased IT productivity
1492
and organizational effectiveness. One state we visited established
1493
an information services board to develop statewide policy standards
1494
and to monitor projects as part of its portfolio management
1495
process. The board, however, has
1496
Page 36 GAO-01-376G CIO Executive Guide
1497
increasingly become more involved in monitoring and making
1498
recommendations on troubled IT projects. Some of the lessons
1499
learned from the board«s project reviews are that:
1500
1501
1502
1503
the board needs to get involved early in monitoring and
1504
overseeing projects before considerable funds are spent on the
1505
projects;
1506
1507
1508
1509
long-term, high-cost projects are no longer sustainable
1510
because sponsors tend to be unable to sustain long-term
1511
support;
1512
1513
1514
1515
projects are best managed in a limited-commitment, phased
1516
approach; and
1517
1518
1519
1520
projects should quickly demonstrate results.
1521
1522
1523
Once planning and decision-making structures are in place and
1524
performance results can be used as part of the decision-making
1525
process, organizations are in a better position to ensure that
1526
goals and objectives clearly link and align with IT performance
1527
measures. Leading organizations also assess the readiness of their
1528
organizations to use IT measures and their receptiveness to data
1529
collection, measurement, and analysis. Further, they nurture a
1530
philosophy that is positive toward performance management and
1531
measurement, and they view measures as a way to focus on business
1532
value and customer satisfaction.
1533
In summary, managers at the organizations we studied cautioned
1534
that IT performance measurement is in its infancy and measurement
1535
techniques are still evolving, partly due to changes in technology.
1536
Most of the organizations are continually looking for ways to
1537
improve their IT measurement systems as a means of supporting
1538
achievement of organizational goals.
1539
1540
Case Study: Measuring Success and Demonstrating Results
1541
To measure its information technology (IT) and management
1542
initiatives, one state instituted a performance measurement process
1543
(illustrated in figure 5) that is driven by an IT strategic plan.
1544
The plan sets forth the goals and strategies needed to support the
1545
state«s entities in developing IT plans, in using information
1546
resources, and in defining IT performance measures. The IT
1547
strategic plan also aligns very closely with the state«s strategic
1548
plan, that sets forth four broad goals for the use of IT within the
1549
state: (1) improve service delivery; (2) make information more
1550
accessible; (3) use IT to improve productivity; and (4) invest in
1551
people, tools, and methods. The IT strategic plan also incorporates
1552
stakeholder involvement by including perspectives by state agency
1553
executives, legislators, educators, and other stakeholders on the
1554
use of the state«s IT resources. Also included in the plan is
1555
information from the state«s biennial IT performance report. This
1556
report evaluates the state«s progress toward meeting the last
1557
biennium«s IT Strategic Plan goals and includes a summary of
1558
strategic and operational performance measures. These measures, in
1559
part, are the result of the state«s previous IT strategic plan and
1560
are meant to measure how well IT resources are being used to
1561
achieve the state«s overall strategic goals and operational
1562
(technical) objectives. These results are published in the State«s
1563
Biennial IT Performance Report and are used to benchmark the
1564
state«s information management services. The state legislature also
1565
uses this information to allocate future funding.
1566
Figure 5: Performance Measurement Framework
1567
1568
measured and monitored
1569
1570
1571
Strategic Performance Measures
1572
Operational Performance Measures
1573
• Progress made in deploying the state« s Educational
1574
• Number of workload transactions completed and
1575
Telecommunications network
1576
telephone lines installed
1577
• Increase in state«s use of Internet resources
1578
• Number of driver«s licenses issued for specific periods
1579
• Increase in the number of courts having access to state«s
1580
Justice Information Network.
1581
1582
Information from the Biennial IT Performance Report is used to
1583
develop the IT Strategic Plan
1584
1585
1586
1587
1588
Strategies to Consider
1589
Performance measurement is a critical step in ensuring results
1590
and success from any project, but especially from information
1591
technology and management initiatives whose value is often
1592
difficult to capture. While performance measurement is still
1593
evolving in principle and in practice, leading organizations have
1594
pinpointed a number of strategies that have proven useful in
1595
gauging the impact and benefits of their IT investments. These
1596
strategies are discussed below.
1597
Engage internal and external stakeholders in defining and
1598
managing IT performance by
1599
1600
1601
1602
ensuring that mission delivery and IT performance
1603
measures are integral to strategic management and decision-making
1604
processes; and
1605
1606
1607
1608
1609
establishing internal and external customer groups to
1610
periodically review, validate, and accept IT performance
1611
measures.
1612
1613
Ensure that processes are in place to balance business and
1614
technical measures by
1615
1616
1617
1618
developing specific technical performance measures for IT
1619
products and services and balancing them with business-driven
1620
measures, and
1621
1622
1623
1624
1625
demonstrating that the performance measurement data
1626
generated are reliable and useful.
1627
1628
Establish an effective data collection and performance feedback
1629
process by
1630
1631
1632
1633
developing well-designed performance data collection
1634
methods;
1635
1636
1637
1638
establishing a limited set of outcome-based performance
1639
measures that link to mission outputs and outcomes; and
1640
1641
1642
1643
utilizing concise, understandable performance reporting
1644
tools and techniques and conducting performance measurement
1645
reviews, as needed.
1646
1647
1648
Critical Success Factors
1649
1650
Principles
1651
Organizational Foci
1652
1653
1654
1655
1656
1657
1658
Critical Success Factor 3: Execute CIO Responsibilities
1659
The CIO and supporting organization are ultimately responsible
1660
for successfully executing their role in the enterprise«s mission.
1661
How central this role is to the strategic plans of the enterprise
1662
will depend on each of the first two critical success factors, but
1663
support from the top and all efforts to build credibility will be
1664
futile unless the CIO organization is run effectively. If the CIO
1665
organization is not able to execute its responsibilities, and if it
1666
is not able to play the critical role for which it has been
1667
developed, the corporation will learn to work around it, or it will
1668
be replaced.
1669
There are many aspects to successfully organizing and running a
1670
CIO organization. However, this critical success factor, as well as
1671
the underlying principles, focuses on the elements that leading
1672
organizations believe are most central to the CIO«s responsibility.
1673
Determination of the CIO organization structure must fall to the
1674
CIO, as he or she is the senior executive of that unit. Aligning
1675
the CIO organization with the needs of the enterprise is critical
1676
to the satisfaction of those needs. Communicating enterprise
1677
requirements to staff and making appropriate decisions to meet the
1678
needs of the enterprise are the responsibility of the CIO. As the
1679
CIO organization«s representative in strategic decision-making
1680
forums, the CIO must be the translator of those strategies into CIO
1681
organization initiatives.
1682
Along with technology, human capital is the central resource the
1683
CIO has to execute his or her responsibilities. While the CIO is
1684
accountable for and reviews technology decisions, staff from
1685
business areas may develop most of the investment proposals. Human
1686
capital plans for the information management and technology area
1687
are seen as the particular responsibility of the CIO. In the
1688
current IT environment, technology has become a commodity. The
1689
human capital involved in applying that technology to achieve the
1690
mission of the enterprise is a resource that requires the CIO«s
1691
attention. The hiring, retention, and training of information
1692
management and technology personnel is seen by leading
1693
organizations as a fundamental principle of good CIO practice.
1694
1695
Principle V: Organize Information Resources to Meet Business
1696
Needs
1697
ƒWhile the CIO is important, it is the operating environment for
1698
the entire organization that will make it successful.≈
1699
1700
Developing a CIO organization is an ongoing process that demands
1701
a clear understanding of the organization«s responsibility for
1702
helping meet business needs. This responsibility, along with parent
1703
business processes, market trends, internal legacy structures, and
1704
available IT skills, drives decisions as to the structure of the
1705
CIO organization and how the organization is aligned with the rest
1706
of the enterprise. Ultimately, the CEO controls the assignment of
1707
information technology and management functions to the CIO, the CIO
1708
organization, and other organizational units. Once these decisions
1709
are made, the CIO organization must provide effective, responsive
1710
support through efficient allocation of resources and the
1711
day-to-day execution of its responsibilities. This principle
1712
examines the practices that leading organizations commonly use in
1713
establishing CIO organizations to effectively meet their mission
1714
needs.
1715
1716
Key Characteristics
1717
It is the duty of a CIO to manage expectations and help ensure
1718
that all members of a CIO organization have a clear understanding
1719
of their responsibilities. In leading organizations, evolving
1720
business processes play a key role in determining how these
1721
information management responsibilities are structured and adapted
1722
to meet changing needs. We found that leading organizations quickly
1723
reallocate and make information resources available on a routine,
1724
sometimes daily or hourly basis to address changes in business
1725
processes. External factors, such as market trends, changing
1726
technology, and available skills as well as internal legacy
1727
structures and corporate ventures, also influence how a CIO
1728
organization is formed, aligned, and adjusted to help support the
1729
rest of an enterprise. For example, one organization that we
1730
studied had experienced two mergers that required the company to
1731
quickly integrate the new businesses and restructure to meet
1732
growing business needs. Human resources systems were consolidated
1733
and new corporate structures were quickly defined to ensure
1734
continued support to the enlarged customer base. The company
1735
remains prepared to restructure to meet ever-changing business
1736
requirements.
1737
In lieu of establishing either completely centralized or
1738
decentralized CIO organizations, leading organizations manage their
1739
information resources through a combination of such structures. In
1740
this hybrid, the CEO assigns central control to a corporate CIO and
1741
supporting CIO organization, while delegating specific authority to
1742
each business unit for managing its own unique information
1743
management requirements. The corporate CIO and supporting CIO
1744
organization centrally formulate policies and standards for all
1745
IT-related activities. They also centrally manage architectures and
1746
a core set of infrastructure components to provide common IT
1747
services to the entire corporation. The corporate CIO works with
1748
CIOs or other information managers in each of the business units to
1749
ensure efficient, reliable, and interoperable technology for the
1750
entire corporation. The following figure illustrates traditional
1751
centralized and decentralized organizational structures, in
1752
comparison with the hybrid combination used by leading
1753
organizations today.
1754
Figure 6: Comparison of Decentralized, Centralized, and Hybrid
1755
Structures
1756
1757
Leading organizations decide, as part of a sourcing strategy,
1758
whether to provide specific information technology and management
1759
services with in-house staff or external providers. An
1760
organization«s sourcing strategy is part of a larger human capital
1761
development strategy, which is discussed in principle VI. The
1762
shortage of skilled IT workers in the current market environment is
1763
often a major reason for leading organizations to outsource. The
1764
CIO and decision-making authorities decide what type of work is
1765
appropriate to outsource and what type of work is best performed
1766
internally. Typically, leading organizations cultivate long-term
1767
skills such as contract management, project management, and
1768
security management, while outsourcing short-term skills such as
1769
application development. For example, one state capital that we
1770
visited is home to over 600 software companies. IT skills are in
1771
great demand which made hiring by the state difficult, so this CIO
1772
looked for alternatives to in-house software development and
1773
management. It made sense for the state to outsource tactical
1774
functions such as help desks and mainframe management.
1775
On the other hand, there are responsibilities such as IT
1776
planning and oversight that must remain in-house. As the state
1777
contracts out more of its information technology and management
1778
functions, it is also essential that it have good contract
1779
management expertise.
1780
Along with effective allocation of available resources, leading
1781
organizations execute their information management responsibilities
1782
reliably and efficiently. Technology is highly integrated with the
1783
business processes in these organizations because technology is
1784
viewed as an enabler for the business, not just a tool. The
1785
organizations make IT investment decisions based on business case
1786
analyses and return-on-investment projections. Consistent with a
1787
fundamental strategic information management approach, the
1788
organizations also focus on continuous process improvement. The
1789
organizations provide reliable information management capabilities
1790
on a daily basis, but also look to the future by pursuing new
1791
initiatives that show how technology can improve the business of
1792
tomorrow. For example, one state CIO that we interviewed said that
1793
his role was to identify enterprisewide and strategic initiatives
1794
to improve state information management. One initiative involved
1795
establishing strategic direction, guidelines, and standards for
1796
instituting electronic commerce in the state government. Electronic
1797
commerce was to be used for such activities as renewing licenses
1798
and paying taxes.
1799
Leading organizations simplify projects by producing incremental
1800
deliverables that quickly show success and demonstrate the impact
1801
of effective CIO management while still focusing on long-term
1802
objectives. As discussed in principle III, carrying out successful
1803
projects is expected in leading organizations, and adds to the
1804
credibility of the CIO and the CIO organization.
1805
1806
Case Study: Organizing Information Resources to Meet Business
1807
Needs
1808
Implementing a combination of centralized and decentralized
1809
information management enables leading organizations to effectively
1810
support their business operations. One leading organization
1811
implements a combination of centralized and decentralized IT and
1812
structures to best meet the needs of its three diverse lines of
1813
business√an international services division, an international
1814
industry division, and a retail division. The organization uses a
1815
centralized IT infrastructure with decentralized development
1816
efforts to provide efficiency and security for its corporate
1817
customers. Efficiency is the number one priority of the
1818
organization in terms of dollars spent as well as technology
1819
performance.
1820
The organization has CIOs in each of its three business units.
1821
Each business unit makes IT investment decisions based on business
1822
requirements and the technology available to support those
1823
requirements. For example, desktop platforms and software vary
1824
among business units depending on the unique needs of each business
1825
area. The work in the business units is all performed in-house and
1826
is not outsourced, as business expertise is considered a core
1827
competency. The business CIOs work together to determine how IT can
1828
be used to reach customers across business lines. The international
1829
services and international industry divisions have some common
1830
requirements based on the international nature of the two
1831
divisions. The international industry division and the retail
1832
division have common requirements based on the specific industry.
1833
The CIOs of these divisions work together, leveraging opportunities
1834
for shared IT products and services so that each unit can invest
1835
fewer dollars to accommodate common needs.
1836
The corporate IT organization«s role is to aggregate needs
1837
across business units and provide solutions that can be integrated
1838
to serve the entire corporation. Common components of each business
1839
area include data centers, human resources, payroll, a financial
1840
architecture, and a common desktop environment. Standard processes
1841
and tools, such as contingency planning, interdependency
1842
identification, protocols, and risk management, are used to
1843
coordinate multiple business areas. These standard utilities
1844
evolved through two corporate mergers and are now institutionalized
1845
across the corporation. The mergers required that the organization
1846
quickly adopt new organizational structures and address new
1847
business requirements. The standard processes and policies
1848
developed, applied, and improved as a result of the mergers provide
1849
this organization with the flexibility it needs to adapt to future
1850
changes in responsibility.
1851
This organization is constantly looking to improve its IT
1852
investment processes. All technology investments are justified
1853
using business case analyses. The decision-making process for
1854
establishing business cases recently evolved to include competitive
1855
needs. Competitive needs were not considered when this organization
1856
initially postponed electronic commerce initiatives due to low
1857
return-on-investment projections. The organization fell behind the
1858
competition in providing this service and the delay may have cost
1859
it customers. As a result, competitive needs are now considered
1860
part of the decision-making process.
1861
1862
1863
1864
Strategies to Consider
1865
An effective CIO organization is a dynamic structure, responding
1866
not only to business, mission, and cultural requirements, but also
1867
to rapidly changing technologies, elusive skills, and competing
1868
resources in the external market environment. Leading organizations
1869
recognize the myriad forces driving their IT capabilities. The
1870
following is an outline of the strategies that these organizations
1871
consider in deciding how to effectively structure, source, and
1872
execute their technology management operations.
1873
Create a clear understanding of responsibilities within the
1874
organization by
1875
1876
1877
1878
articulating a common description of responsibilities to
1879
all levels of the CIO organization, and
1880
1881
1882
1883
1884
assigning responsibilities to parts of the organization
1885
based on skills and organizational structure.
1886
1887
Use a combination of centralized and decentralized
1888
organizational structures by
1889
1890
1891
1892
centrally formulating policy and standards for all
1893
IT-related activities, and providing common IT services through a
1894
centrally managed infrastructure; and
1895
1896
1897
1898
1899
delegating authority to the business units to manage
1900
individual information management requirements.
1901
1902
Create an adaptable organizational structure by
1903
1904
1905
1906
1907
redeploying internal resources to quickly address
1908
changing business and customer requirements.
1909
1910
Select appropriate sourcing strategies by
1911
1912
1913
1914
considering outsourcing noncore responsibilities to
1915
address the shortage of skilled IT workers in the current market
1916
environment, and
1917
1918
1919
1920
1921
keeping core competencies in-house.
1922
1923
Execute CIO responsibilities efficiently by
1924
1925
1926
1927
providing reliable and efficient IT services and
1928
products,
1929
1930
1931
1932
making IT investment decisions based on business case
1933
analyses and return-on-investment, projections, and
1934
1935
1936
1937
producing incremental deliverables to demonstrate results
1938
while still focusing on longterm objectives.
1939
1940
1941
1942
1943
1944
Principle VI: Develop Information Management Human Capital
1945
ƒProviding good benefits packages and building core competencies
1946
are other ways of attracting, stimulating, and retaining IT
1947
workers¬ especially among today's Δself-preservation-minded
1948
generation-Xers.«≈
1949
1950
As is true with the other principles, the business requirements
1951
of an enterprise drive decisions related to the specific types of
1952
resources needed to implement technology successfully. External
1953
market forces and internal legacies influence the types of skills
1954
available to a CIO organization. Given these realities, the CIO
1955
organization must provide an effective, responsive IT workforce to
1956
help accomplish missions and goals. This principle discusses the
1957
strategies that leading organizations use to assess their skill
1958
bases and attract, recruit, and retain IT professionals.
1959
1960
Key Characteristics
1961
Leading organizations develop human capital strategies to assess
1962
their skill bases and recruit and retain staff who can effectively
1963
implement technology to meet business needs. Figure 7 provides an
1964
overview of the strategy that leading organizations use to secure
1965
information management human capital.
1966
Figure 7: Strategy for Securing Human Capital in Leading
1967
Organizations
1968
Training
1969
it
1970
1971
u
1972
Outsource
1973
Leading organizations assess their IT skills on an ongoing basis
1974
to determine what expertise is needed to meet current
1975
responsibilities and support future initiatives. They can evaluate
1976
the skills of their employees using methods provided by entities
1977
such as Carnegie Mellon University«s Software Engineering
1978
Institute6 and the Information
1979
Curtis B. Hefley, W.E. & Miller, S. (1995). People
1980
Capability Maturity Model. [Technical Report CMU/SEI-95-MM-02].
1981
Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon
1982
University.
1983
1984
GAO-01-376G CIO Executive Guide Page 47
1985
Technology Association of America. Needed skills are compared
1986
with existing capabilities in the organization to determine gaps in
1987
the IT skills base. For example, the state university at one of our
1988
case study locations had conducted a study revealing continuing
1989
gaps in the state«s ability to recruit and retain IT workers
1990
vis-à-vis industry. In response to the governor«s initiative to
1991
expand the state«s IT workforce, proposals were made for a program
1992
to recruit and fund college and university students willing to
1993
study technology management as a prelude to becoming part of the
1994
state government«s labor force. Strengthening the skills and
1995
capabilities of IT professionals through training and innovative
1996
hiring practices is part of a formula for building information
1997
technology and management capabilities.
1998
Leading organizations sometimes use surveys that compare missing
1999
capabilities with market availability to determine what skills to
2000
acquire through hired professionals. When professionals with the
2001
necessary skills cannot be hired, these organizations supplement
2002
the existing workforce with external information resources. More
2003
specifically, they cultivate expertise in their internal
2004
workforces, while outsourcing skills that are available from
2005
multiple sources at lower cost. Leading organizations may even
2006
choose to replace labor with technology when they cannot hire the
2007
skilled professionals they need. Core information management
2008
functions include project management, security management, and
2009
contract management practices that can apply to a variety of
2010
projects. The various staffing and sourcing strategies provide
2011
leading organizations with dynamic workforces that can quickly
2012
carry out these functions to meet changing business needs.
2013
Studies forecast an ever-increasing shortage of IT
2014
professionals, presenting a great challenge for both industry and
2015
the federal government. Organizations are finding it difficult to
2016
retain staff when their competitors can always offer higher
2017
salaries. For example, one state government CIO organization that
2018
we studied experienced a 22 percent turnover in IT professionals.
2019
Despite having higher technology wages than any other state in the
2020
country, the state remains at a disadvantage in competing with
2021
industry and must rely on alternative strategies and incentives to
2022
attract and retain skilled workers.
2023
While benefits, recognition, and challenging responsibilities
2024
are also useful in securing staff, leading organizations identify
2025
training as a major nonsalary incentive for attracting and
2026
retaining skilled IT professionals. Leading organizations dedicate
2027
an increasing percentage of their IT budgets to training. Sometimes
2028
such funds are devoted to retraining existing nontechnical
2029
personnel to supply them with IT expertise. For example, one
2030
industry case study organization sponsors a 3-month course to
2031
retrain about 2,000 legacy employees in project management skills.
2032
The company also offers a range of formal classroom training, less
2033
formal workshops, and informal mentoring programs. Given the change
2034
management environment for IT in this company, staff always wants
2035
and needs to be in a learning mode. Similarly, another industry CIO
2036
told us that he provides IT training through a program that pays
2037
new employees 50 percent of their salaries while they attend
2038
school. Upon completion of training, the employees each earn 75
2039
percent of their salary during an initial performance evaluation
2040
period, and full salary at the end of that period.
2041
While managers in leading organizations are accountable for
2042
creating opportunities for their employees« training, individual
2043
staff are responsible for taking advantage of those opportunities.
2044
In general, leading organizations provide training as part of a
2045
changing high-tech work environment that includes state-of-the-art
2046
tools and methods allowing skilled IT workers to perform their jobs
2047
to the best of their ability.
2048
We identified additional strategies that leading organizations
2049
use to enhance their information management workforces.
2050
Specifically, these organizations bring in employees with desirable
2051
skills from across the enterprise to work in conjunction with IT
2052
professionals, thereby maximizing the capability of their technical
2053
resources. These employees make up cross-functional teams that
2054
provide an appropriate mix of business expertise and IT skills to
2055
accomplish the various tasks of a project. Working together, the
2056
members reflect the interests of not just information technology
2057
and management, but the user community and the project«s
2058
stakeholders, and provide a holistic blend of technical, project
2059
management, value management, budget, finance, and procurement
2060
skills and capabilities to meet mission needs.
2061
2062
2063
Case Study: Developing Information Management Human
2064
Capital
2065
Using a variety of staffing and sourcing strategies provides
2066
leading organizations with dynamic workforces that can quickly meet
2067
changing business needs. One leading company«s CIO said that
2068
recruiting information management workers with special skills in
2069
areas such as data networks and systems administration is extremely
2070
competitive. To be successful in recruiting, his organization has
2071
devised different offer packages to attract employees. A package
2072
might include accelerated salary schedules or stock options. Once
2073
hired, the company sends these employees back to college for IT
2074
training and invests in them. This CIO acknowledges, however, that
2075
his company does not spend enough on training. Currently,
2076
approximately 1 percent of the IT operating budget is devoted to
2077
training.
2078
This organization also provides training to new employees
2079
through a program that pays 50 percent of the employee«s salary
2080
while he or she attends school. Upon completion of training, the
2081
employee enters a performance evaluation period during which the
2082
employee earns 75 percent of his or her salary. After successfully
2083
completing the performance evaluation period, the employee then
2084
begins earning a full salary.
2085
The organization increased its salary base to compete with other
2086
companies in retaining and attracting talented information
2087
management workers. Besides salaries, company managers view a good
2088
working environment and awards and recognition as essential for
2089
retaining employees. Recently, the CIO took over 400 employees and
2090
guests to a five-star hotel for an evening out to celebrate the
2091
group«s accomplishments. When senior managers appreciate business
2092
accomplishments, they are willing to spend funds for staff
2093
recognition. This CIO admits that his IT workers are constantly
2094
asked to work long hours and undergo a lot of stress though they
2095
get little in return for the amount of work they do.
2096
This CIO believes that money is not the only motivator for IT
2097
staff. He feels that an important element to managing staff is
2098
finding ways to recognize individuals and say ƒthank you.≈ When the
2099
thank you comes from inside the organization, it goes a long way.
2100
The CIO uses different means to show his appreciation. For
2101
instance, his staff publishes a monthly appreciation newsletter
2102
through the Intranet. The CIO believes there is big payoff in these
2103
types of activities and the costs are minimal, if any. The CIO also
2104
views time off as a good incentive bonus because it does not cost
2105
the company very much. Other incentives his group has undertaken
2106
include taking staff out for lunch or handing out $100 American
2107
Express checks. In today«s environment, organizations have to be
2108
creative. One of the managers created a thank you toolkit to show
2109
her appreciation to her staff. The CIO states, ƒIf you don«t have a
2110
lot of money to spend, you have to ask yourself, what are the
2111
little things you can do to show your appreciation.≈
2112
2113
2114
2115
Strategies to Consider
2116
Given the increasing shortage of IT professionals in the current
2117
market environment, securing an effective, responsive technology
2118
management workforce is a challenging task for both business and
2119
government organizations alike. Leading organizations have
2120
identified the following strategies that help in assessing their IT
2121
skills and recruiting, retaining, and utilizing talent to meet
2122
their business needs. These organizations consider and apply the
2123
various strategies as appropriate within the organizational,
2124
financial, and cultural parameters of their individual business and
2125
government enterprises.
2126
Assess the skill base by
2127
2128
2129
2130
determining expertise needed to perform information
2131
management responsibilities, and
2132
2133
2134
2135
2136
identifying gaps between skills available and skills
2137
needed.
2138
2139
Identify innovative ways to attract talent by
2140
2141
2142
2143
providing good benefits packages, and
2144
2145
2146
2147
2148
building core competencies.
2149
2150
Provide training, tools, and methods to help retain expertise,
2151
including
2152
2153
2154
2155
directing an increasing percentage of the budget to fund
2156
training,
2157
2158
2159
2160
evaluating staff to make sure they are achieving the
2161
desired technical skills,
2162
2163
2164
2165
holding managers accountable for providing training
2166
opportunities for their staffs, and
2167
2168
2169
2170
2171
providing a high-tech environment of tools and
2172
methodologies for skilled IT professionals.
2173
2174
Employ alternative methods and sources for supplying talent,
2175
including • outsourcing and supplementing the existing workforce
2176
with external expertise,
2177
2178
2179
2180
bringing in employees with desirable skills from across
2181
the enterprise to work with and help maximize the capability of
2182
information technology and management professionals, and
2183
2184
2185
2186
replacing labor with technology.
2187
2188
2189
2190
2191
2192
2193
Using This Guide
2194
The principles and practices we developed based on our
2195
interviews with leading organizations in the private sector and
2196
state government have enabled us to construct a framework to guide
2197
federal CIO organizations. In our discussions with about half of
2198
the CIOs of major federal departments and agencies and five CIOs of
2199
small federal agencies, we found that they generally agree with the
2200
leading organizations on the fundamental management principles for
2201
information management and technology. At the same time, we found
2202
that the practices used by federal CIOs tend to differ from those
2203
used by leading organizations. We did not study the reasons for
2204
these deviations specifically, although some likely result from the
2205
context in which federal CIOs operate. Both operational and
2206
structural aspects of the CIO«s environment can vary significantly
2207
between the public sector and the private sector.
2208
Rather than dwell on differences, it is more useful to focus on
2209
the considerable common ground between public and private CIO
2210
organizations to build efforts for improvement. The specific key
2211
conditions and strategies described in this guide can be used as
2212
suggestions for federal CIOs to apply or adapt to their
2213
environments, as appropriate. More generally, the key conditions
2214
and strategies can be thought of as addressing specific aspects of
2215
the six primary principles, which CIOs from all sectors agree are
2216
critical to the successful execution of their responsibilities and
2217
realization of the potential benefits of information technology
2218
investments. Taken as areas of focus, these aspects may be
2219
evaluated by federal CIO organizations and tackled using techniques
2220
suited to their situations. Recognition of the differences
2221
described above, as well as others, should influence the
2222
application of advice provided in this guide. But the advice of
2223
CIOs of leading organizations should remain relevant regardless of
2224
the specifics of the situation.
2225
The ideas presented in this guide may also provide the
2226
foundation for further discussion within the federal CIO community.
2227
Many federal CIOs, in the normal course of their own efforts, have
2228
already begun working along the lines of the advice provided in
2229
this guide. These CIOs have gained valuable insights into applying
2230
the practices of leading organizations to the federal sector. The
2231
CIO Council, or other organizations of federal CIOs, can create an
2232
opportunity for sharing these experiences, using the principles
2233
described in this guide as an organizing framework. The challenge
2234
of understanding how the federal context influences the
2235
effectiveness of the principle may be best met with support from
2236
managers who work in the same context.
2237
In addition, the specific key conditions and strategies
2238
described in this guide will provide insight when considering areas
2239
of future study. For example, specific principles may be
2240
investigated more deeply and strategies for implementing a
2241
principle, such as developing information technology human capital,
2242
may be proposed in more detail. Or those aspects of the federal CIO
2243
environment that constrain the federal CIO flexibility and hinder
2244
the ability to perform effectively may be examined more closely,
2245
and specific strategies to cope with those aspects may be proposed.
2246
Understanding how CIOs of leading organizations approach their
2247
work, and acknowledging those aspects of the federal CIO
2248
environment that limit the ability to implement similar strategies,
2249
may prompt congressional and executive board discussions about the
2250
need for future legislation and policy changes.
2251
A few dimensions in which the federal and private sector can
2252
differ are described below. These examples largely stem from the
2253
nature of the public sector in which federal CIOs operate. Many of
2254
these examples were mentioned by federal CIOs interviewed for this
2255
guide. However, the extent to which the differences create
2256
additional constraints on the CIOs depends on how they and agency
2257
leaders respond to them.
2258
2259
2260
2261
Senior executive management in the federal sector can
2262
differ significantly from the private sector. The agency head is a
2263
political appointee who often is more focused on policy issues than
2264
on internal management and operations. This can deny the CIO the
2265
ƒCEO≈ support that is so critical for the successful integration of
2266
information technology into business or mission
2267
functions.
2268
2269
2270
2271
The budget decision-making process used for information
2272
technology projects can present particular challenges for the
2273
federal CIO not found in the private sector. For example,
2274
legislative actions, such as tax law changes and Medicare payment
2275
process changes, may require extensive system modifications, and
2276
the CIO does not have the flexibility to decide whether or not to
2277
pursue them. This ties up resources that might otherwise have been
2278
expended differently. In fact, mandated projects often must be
2279
funded by money that had been planned for other projects. Long-term
2280
investment strategies are difficult because agencies are asked to
2281
put together funding requests 1824 months in advance of funding
2282
availability. In addition, IT funds may be contained within the
2283
appropriations for a specific program or an overall administrative
2284
budget, making them less visible and, if part of discretionary
2285
spending, more subject to volatile changes in the federal budget.
2286
As a result, the CIO may not have control or direct oversight over
2287
much of the IT funding within the agency.
2288
2289
2290
2291
Personnel decisions in the federal sector are often
2292
constrained due to work rules or organizational factors. Current
2293
information management job descriptions do not match the
2294
occupations recognized in the industry today. Training funds are
2295
often limited due to larger budget considerations. Recently, the
2296
Office of Personnel Management (OPM) found salaries in the federal
2297
government to be lower than in the private sector. On November 3,
2298
2000 OPM implemented a governmentwide policy increasing salaries in
2299
several IT categories in an effort to make federal employment more
2300
competitive. Because this policy was recently implemented, we
2301
cannot yet assess the impact of these changes on federal employment
2302
practices.
2303
2304
2305
2306
The federal CIO may direct an organizational structure in
2307
which duties that would typically be a CIO«s responsibility in the
2308
private sector are not under his or her direction at all. For
2309
example, some federal CIOs are in charge of large policy and
2310
oversight functions with little operational responsibility. While
2311
this may be an appropriate model, it is critical that any model be
2312
matched with the overall needs of the agency in mind.
2313
2314
2315
2316
The range of responsibilities, as defined by legislation,
2317
that accrue to the CIO are very broad in the federal sector,
2318
including areas such as records management and Freedom of
2319
Information Act requirements, for which there is little parallel in
2320
the private sector. While federal CIOs often may not have
2321
operational authority for the full range of responsibilities in the
2322
legislation, they and their agencies are still subject to oversight
2323
by the Congress in many of these areas.
2324
2325
2326
Though the environment faced by a CIO in the federal sector
2327
clearly differs from that of CIOs in other contexts, the principles
2328
that form the basis for this guide remain relevant. The underlying
2329
principles were observed consistently in our sample of leading
2330
organizations, and were cited as being critical to the success of
2331
their CIOs. Federal CIOs can learn from the successes of these
2332
leading organizations and can apply the principles as appropriate
2333
in their own organizations. In addition, agency heads and other
2334
senior leaders in the federal government can gain an understanding
2335
of their roles in executing the critical success factors that must
2336
be addressed as CIOs work to meet the letter and intent of the
2337
Clinger-Cohen Act and related legislation.
2338
2339
Appendix I Federal Legislation Affecting Information
2340
Management
2341
Federal Financial Management Improvement Act of 1996 (Public Law
2342
104-208) ¬ This Act requires that agency financial management
2343
systems comply with federal financial management system
2344
requirements, applicable federal accounting standards, and the U.S.
2345
Government Standard General Ledger (SGL) in order to provide
2346
uniform, reliable, and more useful financial information. The act
2347
requires that auditors for each of the 24 departments and agencies
2348
named in the CFO Act report, as part of their annual audits of the
2349
agencies« financial statements, whether the agencies« financial
2350
management systems comply substantially with federal financial
2351
management systems requirements, applicable federal accounting
2352
standards, and SGL at the transaction level. The act also requires
2353
that GAO report on its implementation annually.
2354
Clinger-Cohen Act of 1996 (Public Law 104-106) ¬ This law is
2355
intended to improve the productivity, efficiency, and effectiveness
2356
of federal programs through the improved acquisition, use, and
2357
disposal of IT resources. Among other provisions, it (1) encourages
2358
federal agencies to evaluate and adopt best management and
2359
acquisition practices used by both private and public sector
2360
organizations,
2361
(2) requires agencies to base decisions about IT investments on
2362
quantitative and qualitative factors associated with the costs,
2363
benefits, and risks of those investments and to use performance
2364
data to demonstrate how well the IT expenditures support
2365
improvements to agency programs, through measurements such as
2366
reduced costs, improved employee productivity, and higher customer
2367
satisfaction, and (3) requires executive agencies to appoint CIOs
2368
to carry out the IT management provisions of the act and the
2369
broader information resources management requirements of the
2370
Paperwork Reduction Act. The Clinger-Cohen Act also streamlines the
2371
IT acquisition process by eliminating the General Services
2372
Administration«s central acquisition authority, placing procurement
2373
responsibility directly with federal agencies, and encouraging the
2374
adoption of smaller, modular IT acquisition projects.
2375
Paperwork Reduction Act (PRA) of 1995 (Public Law 104-13) ¬ PRA
2376
applies life cycle management principles to information management
2377
and focuses on reducing the government«s information-collection
2378
burden. To this end, PRA designated senior information resources
2379
manager positions in the major departments and agencies with
2380
responsibility for a wide range of functions. PRA also created the
2381
Office of Information and Regulatory Affairs within the OMB to
2382
provide central oversight of information management activities
2383
across the federal government.
2384
Government Management Reform Act of 1994 (Public Law 103-356) ¬
2385
This legislation expands the requirement for a fully audited
2386
financial statement under the CFO Act to 24 agencies and components
2387
of federal entities designated by the Office of Management and
2388
Budget. The act requires the Department of the Treasury to produce
2389
a consolidated financial statement for the federal government,
2390
which GAO is to audit annually.
2391
Federal Acquisition Streamlining Act of 1994 (FASA) (Public Law
2392
103-355) ¬ This law requires agencies to define cost, schedule, and
2393
performance goals for federal acquisition programs (to include IT
2394
projects) and monitor these programs to ensure that they remain
2395
within prescribed tolerances. If a program falls out of tolerance,
2396
FASA requires the agency head to review, take necessary actions,
2397
and, if necessary, terminate the program.
2398
Government Performance and Results Act (GPRA) of 1993, Public
2399
Law 103-62 ¬ GPRA requires agencies to prepare multiyear strategic
2400
plans that describe mission goals and methods for reaching them.
2401
The act requires agencies to develop annual performance plans that
2402
OMB uses to prepare a federal performance plan that is submitted to
2403
the Congress along with the President«s annual budget submission.
2404
The agency plans must establish measurable goals for program
2405
activities and describe the methods by which performance toward
2406
those goals will be measured. The act also requires agencies to
2407
prepare annual program performance reports to review progress
2408
toward annual performance goals
2409
Chief Financial Officers (CFO) Act of 1990 (Public Law 101-576)
2410
¬ The CFO Act provides a framework for improving federal government
2411
financial systems. It centralizes within OMB, through the Deputy
2412
Director for Management and the Office of Federal Financial
2413
Management, the establishment and oversight of federal financial
2414
management policies and practices and requires OMB to prepare and
2415
submit to Congress a governmentwide, 5-year financial management
2416
plan. The act also requires the 24 major agencies to have CFOs and
2417
deputy CFOs and lays out their authorities and functions. Further,
2418
the act sets up a series of pilot audits under which certain
2419
agencies are required to prepare agencywide financial statements
2420
and subject them to audit by the agencies« inspectors general.
2421
Computer Security Act of 1987 (Public Law 100-235, as amended by
2422
Public Law 104106) ¬ This law addresses the importance of ensuring
2423
and improving the security and privacy of sensitive information in
2424
federal computer systems. The act requires that the National
2425
Institute of Standards and Technology develop standards and
2426
guidelines for computer systems to control loss and unauthorized
2427
modification or disclosure of sensitive information and to prevent
2428
computer-related fraud and misuse. The act also requires that all
2429
operators of federal computer systems, including both federal
2430
agencies and their contractors, establish security plans.
2431
Federal Managers« Financial Integrity Act (FMFIA) of 1982
2432
(Public Law 97-255) ¬FMFIA requires agencies to establish internal
2433
accounting and administrative controls in compliance with standards
2434
established by the Comptroller General. The act also requires that
2435
OMB establish, in consultation with the Comptroller General,
2436
guidelines that the agencies shall follow in evaluating their
2437
systems of internal accounting and administrative controls.
2438
Government Information Security Reform (P.L. No. 106-398, Div.
2439
A, Title X, subtitle G) -This legislation amends 44 U.S.C. Chapter
2440
35 by enacting a new subchapter on "Information Security." The
2441
Security Act requires the establishment of agencywide information
2442
security programs, annual agency program reviews, annual
2443
independent evaluations of agency programs and practices, agency
2444
reporting to OMB, and OMB reporting to Congress. The Act covers
2445
programs for both unclassified and national security systems, but
2446
exempts agencies operating national security systems from OMB
2447
oversight. The Security Act is to be implemented consistent with
2448
the Computer Security Act.
2449
Government Paperwork Elimination Act (GPEA) (P.L. No. 105-277,
2450
Div. C, Title XVII) -GPEA requires that by 2003 federal agencies
2451
provide, where practicable, for the option of submitting,
2452
maintaining, or disclosing information in electronic form as a
2453
substitute for paper, and for the use and acceptance of electronic
2454
signatures.
2455
Privacy Act of 1974 (Public Law 93-579) ¬ The Privacy Act
2456
protects the privacy of individuals identified in information
2457
systems maintained by federal agencies by regulating the
2458
collection, maintenance, use, and dissemination of information by
2459
such agencies.
2460
Freedom of Information Act of 1966 (Public Law 89-554) ¬ This
2461
law established the right of public access to government
2462
information by requiring agencies to make information accessible to
2463
the public, either through automatic disclosure or upon specific
2464
request, subject to specified exemptions.
2465
2466
2467
Appendix II Objectives, Scope, and Methodology
2468
The objective of our research was to determine how several
2469
leading organizations have implemented their CIO positions and
2470
supporting management infrastructures. We were interested in
2471
identifying effective CIO management practices used across a
2472
variety of organization types and structures. In doing so, we also
2473
sought to develop specific case study information on how CIOs have
2474
helped improve the effectiveness of their organizations« business
2475
operations. We have used this information to develop suggested
2476
guidance to assist federal agencies in effectively integrating
2477
newly created CIO functions into their respective
2478
organizations.
2479
We synthesized a great deal of literature and research on CIO
2480
organizations to provide ideas on effective practices in
2481
information technology and management. This body of knowledge
2482
served as a foundation for designing our project approach. We then
2483
conducted case studies at a number of private and public
2484
organizations. We have found that case studies provide an abundant
2485
source of information describing management practices and the
2486
intellectual background that led to the development of those
2487
practices. Case studies also provide the flexibility to pursue
2488
particularly rich avenues of inquiry as they develop during
2489
interviews. Finally, they are also an excellent means of
2490
communicating the essence of practices that have worked well by
2491
capturing the context as well as the specific practice.
2492
We identified candidate organizations for our study based on
2493
awards and recognition from professional organizations and
2494
publications over the past several years. We conducted multi-day
2495
visits to organizations that agreed to participate in our study to
2496
learn
2497
2498
2499
2500
each organization«s approach to selecting, positioning,
2501
and defining the roles and responsibilities of its CIO;
2502
2503
2504
2505
techniques for instituting IT policies and standards,
2506
managing technical personnel and financial resources, building
2507
customer/supplier relationships, and measuring the performance of
2508
IT organizations in meeting business needs; and
2509
2510
2511
2512
2513
strategies for promoting and facilitating business and
2514
organizational change through IT.
2515
2516
We visited three private and three public sector organizations
2517
recognized as leaders in successfully managing information and
2518
technology investments to create value and improve business
2519
performance. We selected private organizations across a range of
2520
dimensions, including type of business, number of employees, and
2521
revenues. All private organizations contacted had received
2522
recognition by professional organizations and publications,
2523
corporate executives, or independent researchers. Our selection of
2524
state organizations was based on recognition by professional
2525
publications, state CIOs, and the National Association of State
2526
Information Resource Executives (NASIRE). In particular, NASIRE
2527
awards recognition to states whose systems have made important
2528
contributions to the operations of state governments. The following
2529
organizations participated in our study:
2530
2531
2532
2533
Commonwealth of Pennsylvania
2534
2535
2536
2537
State of Texas
2538
2539
2540
2541
State of Washington
2542
2543
2544
2545
Chase Manhattan Bank
2546
2547
2548
2549
General Motors Corporation
2550
2551
2552
2553
J.C. Penney
2554
2555
2556
We also interviewed the former CIO of the state of California
2557
and the current CIO at U.S. West Communications, although we did
2558
not conduct comprehensive case studies at these entities.
2559
We conducted site visits to each participating organization and
2560
obtained supporting documentation, illustrations, and examples.
2561
During the visits, we interviewed the CIO, members of the senior
2562
executive team, IT managers, and other officials as identified by
2563
the host organization, to obtain their individual perspectives on
2564
information and technology management issues. Based on the
2565
documentation and interviews obtained from our site visits, we
2566
compared practices across organizations to identify innovative
2567
practices used by individual organizations as well as common
2568
practices used across the variety of organizations participating in
2569
our study.
2570
We subsequently interviewed 50 percent of the Federal CIO
2571
Council members as a means of comparing federal CIO practices with
2572
our case study results and ensuring that practices used in the
2573
industry and state organizations also addressed the challenges
2574
found in the federal government. We selected a mix of federal
2575
organizations to visit, taking into consideration their various
2576
mission types (civilian, military, or regulatory), centralized and
2577
decentralized structures, and prior GAO study results. Further, we
2578
met with a panel of CIOs from five small federal agencies to
2579
determine whether the practices identified are also applicable
2580
across diverse organizational sizes (based on dimensions such as
2581
budget, personnel, etc.). These discussions, which are summarized
2582
in the section entitled ƒCurrent Federal CIO Environment,≈ helped
2583
us identify similarities and differences in the CIO management
2584
practices of federal versus leading organizations. The discussions
2585
have also enabled us to pinpoint areas where federal agencies can
2586
benefit from integrating the practices of such leading
2587
organizations in their respective organizations.
2588
Our research was conducted from March through October 1999 and
2589
culminated in the issuance of an exposure draft in March 2000.
2590
Since March 2000 we received comments from a variety of
2591
organizations and individuals. Based on suggestions from the
2592
general public we have considered and made changes to the text
2593
where appropriate. General consensus of those providing input was
2594
that the CIO Guide represented leading practices and that the
2595
document was insightful and valuable.
2596
2597
2598
Appendix III Related GAO Documents
2599
Information Security Risk Assessment: Practices of Leading
2600
Organizations
2601
(GAO/AIMD-00-33, November 1, 1999).
2602
Executive Guide: Creating Value Through World-class Financial
2603
Management
2604
(GAO/AIMD-99-45, Exposure Draft, August 1999).
2605
Executive Guide: Leading Practices in Capital Decision-Making
2606
(GAO/AIMD-99-32, December 1998).
2607
Executive Guide: Information Security Management: Learning From
2608
Leading Organizations (GAO/AIMD-98-68, April 1998).
2609
The Results Act: An Evaluator«s Guide to Assessing Agency Annual
2610
Performance Plans
2611
(GAO/GGD-10.1.20, Version 1, April 1998).
2612
Executive Guide: Measuring Performance and Demonstrating Results
2613
of Information Technology Investments (GAO/AIMD-98-89, March
2614
1998).
2615
Agencies' Annual Performance Plans Under the Results Act: An
2616
Assessment Guide to Facilitate Congressional Decisionmaking
2617
(GAO/GGD/AIMD-10.1.18, Version 1, February 1998).
2618
Business Process Reengineering Assessment Guide (GAO/AIMD
2619
10.1.15, Version 3, May 1997).
2620
Agencies« Strategic Plans Under GPRA: Key Questions to
2621
Facilitate Congressional Review (GAO/GGD-10.1.16, Version 1, May
2622
1997).
2623
Assessing Risks and Returns: A Guide for Evaluating Federal
2624
Agencies' IT Investment Decision-Making (GAO/AIMD-10.1.13, Version
2625
1, February 1997).
2626
Executive Guide: Effectively Implementing the Government
2627
Performance and Results Act
2628
(GAO/GGD-96-118, June 1996).
2629
Strategic Information Management (SIM) Self-Assessment Toolkit
2630
(Exposure Draft, Version 1.0, October 28, 1994).
2631
Executive Guide: Improving Mission Performance Through Strategic
2632
Information Management and Technology (GAO/AIMD-94-115, May
2633
1994).
2634
Meeting the Government«s Technology Challenge: Results of A GAO
2635
Symposium
2636
(GAO/IMTEC-90-23, February 1990).
2637
2638
2639
Appendix IV Selected CIO Resources
2640
2641
Professional Organizations
2642
Association for Federal Information Resources Management:
2643
www.affirm.org Chief Financial Officers Council: www.financenet.gov
2644
Federal Chief Information Officers Council: www.cio.gov Government
2645
Information Technology Services Board: www.gits.gov Industry
2646
Advisory Council: www.iaconline.org Information Systems Audit and
2647
Control Association and Foundation: www.iasca.org Information
2648
Technology Association of America: www.itaa.org Information
2649
Technology Resources Board: www.itrb.gov International Federation
2650
of Accountants: www.ifac.org National Association of State
2651
Information Resource Executives: www.nasire.org Society for
2652
Information Management: www.simnet.org
2653
2654
2655
Publications
2656
Beyond Computing: www.beyondcomputingmag.com CIO Magazine:
2657
www.cio.com Federal Computer Week: www.fcw.com Government Computer
2658
News: www.gcn.com Government Executive: www.govexec.com
2659
InformationWeek: www.informationweek.com
2660
International Data Group: www.idg.com Sloan Management Review:
2661
www.mitsloan.mit.edu/smr/index.html
2662
2663
GAO-01-376G CIO Executive Guide Page 61
2664
2665
2666
2667
Research Organizations
2668
Forrester Research, Inc.: www.forrester.com Foundation for
2669
Performance Measurement: www.fpm.com Gartner Group: www.gartner.com
2670
GIGA Information Group: www.gigaweb.com International Data
2671
Corporation: www.idc.com IT Governance Institute:
2672
www.itgoverence.org/itgi META Group Inc.: www.metagroup.com Yankee
2673
Group: www.yankeegroup.com
2674
2675
2676
Federal Resources
2677
Federal Acquisition Regulation: www.ARNet.gov/far/ Critical
2678
Infrastructure Assurance Office: www.caio.gov Federal Computer
2679
Incident Response Capability: www.fedcirc.gov Federal Information
2680
Processing Standards: www.itl.nist.gov General Accounting Office:
2681
http://www.gao.gov/ GSA«s Policyworks: www.policyworks.gov IT
2682
Policy On-Ramp: www.itpolicy.gsa.gov National Partnership for
2683
Reinventing Government: www.npr.gov Office of Management and Budget
2684
Homepage: www.whitehouse.gov/omb
2685
2686
2687
Other Resources
2688
Chief Information Officer ¬ Treasury Board of Canada:
2689
http://www.cio-dpi.gc.ca/home_e.html
2690
2691
2692
2693
Appendix V Selected Books and Articles
2694
ƒBest Practices in Improving IT Staff Competencies,≈ GIGA
2695
Information Group, December 1998.
2696
Blodgett, Mindy, ƒThe CIO Starter Kit: Ten Tools Every New CIO
2697
Needs to Succeed,≈ CIO Magazine, May 15, 1999.
2698
Boar, Bernard H., Practical Steps for Aligning Information
2699
Technology with Business Strategies: How to Achieve a Competitive
2700
Advantage (John Wiley & Sons, Inc., New York, New York,
2701
1994).
2702
Boar, Bernard H., Strategic Thinking for Information Technology
2703
(John Wiley & Sons, Inc., New York, New York, 1996).
2704
Bryson, John M., Strategic Planning for Public and Nonprofit
2705
Organizations: A Guide to Strengthening and Sustaining
2706
Organizational Achievement (Jossey-Bass Publishers, San Francisco,
2707
California, 1991).
2708
Camp, Robert C., Benchmarking: The Search for Industry Best
2709
Practices That Lead to Superior Performance (ASQC Quality Press,
2710
New York, New York, 1989).
2711
Cortada, James W., Best Practices in Information Technology
2712
(Prentice Hall PTR, Upper Saddle River, New Jersey, 1998).
2713
Earl, Michael J., and Feeny, David F., ƒDoes the CIO Add Value?≈
2714
Informationweek, May 30, 1994.
2715
Ferris, Nancy, ƒCIOs on the Go,≈ Government Executive, March
2716
1999.
2717
Government Executive Magazine/Price Waterhouse, The Manager«s
2718
Edge (National Journal Group, Washington, D.C., 1998).
2719
Hubbard, Douglas, ƒThe IT Measurement Inversion,≈ CIO
2720
Enterprise,≈ April 15, 1999.
2721
Mayor, Tracy, ƒMaking a Federal Case of IT,≈ CIO Magazine, July
2722
1, 1999.
2723
Morin, Therese; Devansky, Ken; Little, Gard; and Petrun, Craig,
2724
Information Leadership: A Guide for Government Executives
2725
(PricewaterhouseCoopers, LLP, 1999).
2726
Stephens, Charlotte S., The Nature of Information Technology
2727
Managerial Work: The Work Life of Five Chief Information Officers
2728
(Quorum Books, Westport, Connecticut, 1995).
2729
Stuart, Anne, ƒThe CIO Role: The New IS Role Models,≈ CIO
2730
Magazine, May 15, 1995.
2731
Tapscott, Don and Caston, Art, Paradigm Shift ¬ The New Promise
2732
of Information Technology (McGraw-Hill, Inc., New York, New York,
2733
1993).
2734
Wakin, Dr. Edward, ƒThe Multifaceted CIO,≈ Beyond Computing, May
2735
1995.
2736
Wang, Charles B., Techno Vision II: Every Executive«s Guide to
2737
Understanding and Mastering Technology and the Internet
2738
(McGraw-Hill, Inc., New York, New York, 1997).
2739
Weill, Peter and Broadbent, Marianne, Leveraging the New
2740
Infrastructure: How Market Leaders Capitalize on Information
2741
Technology (Harvard Business School Press, Boston, Massachusetts,
2742
1998).
2743
Woldring, Roelf, ƒChoosing the Right CIO,≈ Business Quarterly,
2744
Spring 1996.
2745
Wreden, Nick, ƒExecutive Forum: Proving the Value of
2746
Technology,≈ Beyond Computing, July/August 1998.
2747
2748
2749
Appendix VI Selected Information Management Reports and
2750
Guidance
2751
An Analytical Framework for Capital Planning and Investment
2752
Control for Information Technology, U.S. General Services
2753
Administration, Office of Policy, Planning and Evaluation, Office
2754
of Information Technology, May 1996.
2755
ƒBest IT Practices in the Federal Government,≈ CIO Council and
2756
IAC, October 1997.
2757
Capital Programming Guide, Version 1.0, Supplement to Office of
2758
Management and Budget Circular A-11, Part 3: Planning, Budgeting,
2759
and Acquisition of Capital Assets, July 1997.
2760
Evaluating Information Technology Investments: A Practical
2761
Guide, Version 1.0, Office of Information and Regulatory Affairs,
2762
Information Policy and Technology Branch, Office of Management and
2763
Budget, November 1, 1995.
2764
Federal Enterprise Architecture Framework, Version 1.1, Federal
2765
CIO Council, September 1999.
2766
Federal Information Technology, Executive Order on ITMRA, The
2767
White House, July 17, 1996.
2768
Federal IRM Training Roadmap: A Guide for Federal CIOs, (Draft),
2769
Federal CIO Council, Education and Training Committee, January
2770
1999
2771
Funding Information Systems Investments, M-97-02, Office of
2772
Management and Budget, October 25, 1996.
2773
IAC / CIO Task Force Draft Report, Industry Advisory Council,
2774
July 9, 1996.
2775
Implementing Best Practices: Strategies at Work, Federal CIO
2776
Council, Capital Planning and IT Investment Committee, June
2777
1998.
2778
Implementing Capital Planning and Information Technology
2779
Investment Processes: An Assessment, Federal CIO Council, Capital
2780
Planning and IT Investment Committee, Best Practices Subcommittee,
2781
May 29, 1998.
2782
ƒMajor System Acquisitions,≈ Circular No. A-109, Office of
2783
Management and Budget, April 5, 1976.
2784
Management of Federal Information Resources, Circular No. A-130,
2785
Revised, Office of Management and Budget, February 8, 1996.
2786
Meeting the Federal IT Workforce Challenge, Federal CIO Council,
2787
Education and Training Committee, June 1999.
2788
Preparation and Submission of Budget Estimates, Circular No.
2789
A-11, Revised, Office of Management and Budget, June 23, 1997.
2790
ROI and the Value Puzzle, Federal CIO Council, Capital Planning
2791
and IT Investment Committee, April 1999.
2792
Strategic Plan, Federal CIO Council, Fiscal Year 2000.
2793
The Federal Chief Information Officer: Fourth Annual Top Ten
2794
Challenges Survey, Association for Federal Information Resources
2795
Management, December 1999.
2796
The Impact of Change: Clinger-Cohen Act Implementation, Laying
2797
the Foundation for Year 2000 and Beyond, Eighth Annual ITAA Survey
2798
of Federal CIOs, December 1997.
2799
2800
2801
Appendix VII Project Adviser Acknowledgments
2802
We would like to acknowledge the following individuals whose
2803
advice and assistance throughout this project have been
2804
invaluable.
2805
Dr. Lynda McDonald Applegate Professor of Business
2806
Administration Harvard Business School
2807
Thomas V. Fritz President & Chief Executive Officer Private
2808
Sector Council
2809
Laraine Rodgers Vice President Emerald Solutions
2810
Paul Rummell Senior Partner KPMG Consulting
2811
(310400)
2812
2813
Ordering Information
2814
The first copy of each GAO report is free. Additional copies of
2815
reports are $2 each. A check or money order should be made out to
2816
the Superintendent of Documents. VISA and MasterCard credit cards
2817
are accepted, also.
2818
Orders for 100 or more copies to be mailed to a single address
2819
are discounted 25 percent.
2820
2821
Orders by mail:
2822
U.S. General Accounting Office
2823
P.O. Box 37050 Washington, DC 20013
2824
Orders by visiting: Room 1100 700 4th St. NW (corner of 4th and
2825
G Sts. NW)
2826
U.S. General Accounting Office Washington, DC
2827
Orders by phone: (202) 512-6000 fax: (202) 512-6061 TDD (202)
2828
512-2537
2829
Each day, GAO issues a list of newly available reports and
2830
testimony. To receive facsimile copies of the daily list or any
2831
list from the past 30 days, please call (202) 512-6000 using a
2832
touchtone phone. A recorded menu will provide information on how to
2833
obtain these lists.
2834
Orders by Internet: For information on how to access GAO reports
2835
on the Internet, send an e-mail message with "info" in the body
2836
to:
2837
[email protected]
2838
or visit GAO's World Wide Web home page at:
2839
http://www.gao.gov
2840
2841
2842
Contact one:
2843
2844
2845
2846
To Report Fraud,
2847
• Web site: http://www.gao.gov/fraudnet/fraudnet.htm
2848
2849
2850
Waste, or Abuse in
2851
2852
• e-mail: [email protected]
2853
1-800-424-5454 (automated answering system)
2854
2855
2856
2857
2858
2859
2860
2861
2862