- Management Reference Guide
- Table of Contents
- Introduction
- Strategic Management
- Establishing Goals, Objectives, and Strategies
- Aligning IT Goals with Corporate Business Goals
- Utilizing Effective Planning Techniques
- Developing Worthwhile Mission Statements
- Developing Worthwhile Vision Statements
- Instituting Practical Corporate Values
- Budgeting Considerations in an IT Environment
- Introduction to Conducting an Effective SWOT Analysis
- IT Governance and Disaster Recovery, Part One
- IT Governance and Disaster Recovery, Part Two
- Customer Management
- Identifying Key External Customers
- Identifying Key Internal Customers
- Negotiating with Customers and Suppliers—Part 1: An Introduction
- Negotiating With Customers and Suppliers—Part 2: Reaching Agreement
- Negotiating and Managing Realistic Customer Expectations
- Service Management
- Identifying Key Services for Business Users
- Service-Level Agreements That Really Work
- How IT Evolved into a Service Organization
- FAQs About Systems Management (SM)
- FAQs About Availability (AV)
- FAQs About Performance and Tuning (PT)
- FAQs About Service Desk (SD)
- FAQs About Change Management (CM)
- FAQs About Configuration Management (CF)
- FAQs About Capacity Planning (CP)
- FAQs About Network Management
- FAQs About Storage Management (SM)
- FAQs About Production Acceptance (PA)
- FAQs About Release Management (RM)
- FAQs About Disaster Recovery (DR)
- FAQs About Business Continuity (BC)
- FAQs About Security (SE)
- FAQs About Service Level Management (SL)
- FAQs About Financial Management (FN)
- FAQs About Problem Management (PM)
- FAQs About Facilities Management (FM)
- Process Management
- Developing Robust Processes
- Establishing Mutually Beneficial Process Metrics
- Change Management—Part 1
- Change Management—Part 2
- Change Management—Part 3
- Audit Reconnaissance: Releasing Resources Through the IT Audit
- Problem Management
- Problem Management–Part 2: Process Design
- Problem Management–Part 3: Process Implementation
- Business Continuity Emergency Communications Plan
- Capacity Planning – Part One: Why It is Seldom Done Well
- Capacity Planning – Part Two: Developing a Capacity Planning Process
- Capacity Planning — Part Three: Benefits and Helpful Tips
- Capacity Planning – Part Four: Hidden Upgrade Costs and
- Improving Business Process Management, Part 1
- Improving Business Process Management, Part 2
- 20 Major Elements of Facilities Management
- Major Physical Exposures Common to a Data Center
- Evaluating the Physical Environment
- Nightmare Incidents with Disaster Recovery Plans
- Developing a Robust Configuration Management Process
- Developing a Robust Configuration Management Process – Part Two
- Automating a Robust Infrastructure Process
- Improving High Availability — Part One: Definitions and Terms
- Improving High Availability — Part Two: Definitions and Terms
- Improving High Availability — Part Three: The Seven R's of High Availability
- Improving High Availability — Part Four: Assessing an Availability Process
- Methods for Brainstorming and Prioritizing Requirements
- Introduction to Disk Storage Management — Part One
- Storage Management—Part Two: Performance
- Storage Management—Part Three: Reliability
- Storage Management—Part Four: Recoverability
- Twelve Traits of World-Class Infrastructures — Part One
- Twelve Traits of World-Class Infrastructures — Part Two
- Meeting Today's Cooling Challenges of Data Centers
- Strategic Security, Part One: Assessment
- Strategic Security, Part Two: Development
- Strategic Security, Part Three: Implementation
- Strategic Security, Part Four: ITIL Implications
- Production Acceptance Part One – Definition and Benefits
- Production Acceptance Part Two – Initial Steps
- Production Acceptance Part Three – Middle Steps
- Production Acceptance Part Four – Ongoing Steps
- Case Study: Planning a Service Desk Part One – Objectives
- Case Study: Planning a Service Desk Part Two – SWOT
- Case Study: Implementing an ITIL Service Desk – Part One
- Case Study: Implementing a Service Desk Part Two – Tool Selection
- Ethics, Scandals and Legislation
- Outsourcing in Response to Legislation
- Supplier Management
- Identifying Key External Suppliers
- Identifying Key Internal Suppliers
- Integrating the Four Key Elements of Good Customer Service
- Enhancing the Customer/Supplier Matrix
- Voice Over IP, Part One — What VoIP Is, and Is Not
- Voice Over IP, Part Two — Benefits, Cost Savings and Features of VoIP
- Application Management
- Production Acceptance
- Distinguishing New Applications from New Versions of Existing Applications
- Assessing a Production Acceptance Process
- Effective Use of a Software Development Life Cycle
- The Role of Project Management in SDLC— Part 2
- Communication in Project Management – Part One: Barriers to Effective Communication
- Communication in Project Management – Part Two: Examples of Effective Communication
- Safeguarding Personal Information in the Workplace: A Case Study
- Combating the Year-end Budget Blitz—Part 1: Building a Manageable Schedule
- Combating the Year-end Budget Blitz—Part 2: Tracking and Reporting Availability
- References
- Developing an ITIL Feasibility Analysis
- Organization and Personnel Management
- Optimizing IT Organizational Structures
- Factors That Influence Restructuring Decisions
- Alternative Locations for the Help Desk
- Alternative Locations for Database Administration
- Alternative Locations for Network Operations
- Alternative Locations for Web Design
- Alternative Locations for Risk Management
- Alternative Locations for Systems Management
- Practical Tips To Retaining Key Personnel
- Benefits and Drawbacks of Using IT Consultants and Contractors
- Deciding Between the Use of Contractors versus Consultants
- Managing Employee Skill Sets and Skill Levels
- Assessing Skill Levels of Current Onboard Staff
- Recruiting Infrastructure Staff from the Outside
- Selecting the Most Qualified Candidate
- 7 Tips for Managing the Use of Mobile Devices
- Useful Websites for IT Managers
- References
- Automating Robust Processes
- Evaluating Process Documentation — Part One: Quality and Value
- Evaluating Process Documentation — Part Two: Benefits and Use of a Quality-Value Matrix
- When Should You Integrate or Segregate Service Desks?
- Five Instructive Ideas for Interviewing
- Eight Surefire Tips to Use When Being Interviewed
- 12 Helpful Hints To Make Meetings More Productive
- Eight Uncommon Tips To Improve Your Writing
- Ten Helpful Tips To Improve Fire Drills
- Sorting Out Today’s Various Training Options
- Business Ethics and Corporate Scandals – Part 1
- Business Ethics and Corporate Scandals – Part 2
- 12 Tips for More Effective Emails
- Management Communication: Back to the Basics, Part One
- Management Communication: Back to the Basics, Part Two
- Management Communication: Back to the Basics, Part Three
- Asset Management
- Managing Hardware Inventories
- Introduction to Hardware Inventories
- Processes To Manage Hardware Inventories
- Use of a Hardware Inventory Database
- References
- Managing Software Inventories
- Business Continuity Management
- Ten Lessons Learned from Real-Life Disasters
- Ten Lessons Learned From Real-Life Disasters, Part 2
- Differences Between Disaster Recovery and Business Continuity , Part 1
- Differences Between Disaster Recovery and Business Continuity , Part 2
- 15 Common Terms and Definitions of Business Continuity
- The Federal Government’s Role in Disaster Recovery
- The 12 Common Mistakes That Cause BIAs To Fail—Part 1
- The 12 Common Mistakes That Cause BIAs To Fail—Part 2
- The 12 Common Mistakes That Cause BIAs To Fail—Part 3
- The 12 Common Mistakes That Cause BIAs To Fail—Part 4
- Conducting an Effective Table Top Exercise (TTE) — Part 1
- Conducting an Effective Table Top Exercise (TTE) — Part 2
- Conducting an Effective Table Top Exercise (TTE) — Part 3
- Conducting an Effective Table Top Exercise (TTE) — Part 4
- The 13 Cardinal Steps for Implementing a Business Continuity Program — Part One
- The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Two
- The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Three
- The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Four
- The Information Technology Infrastructure Library (ITIL)
- The Origins of ITIL
- The Foundation of ITIL: Service Management
- Five Reasons for Revising ITIL
- The Relationship of Service Delivery and Service Support to All of ITIL
- Ten Common Myths About Implementing ITIL, Part One
- Ten Common Myths About Implementing ITIL, Part Two
- Characteristics of ITIL Version 3
- Ten Benefits of itSMF and its IIL Pocket Guide
- Translating the Goals of the ITIL Service Delivery Processes
- Translating the Goals of the ITIL Service Support Processes
- Elements of ITIL Least Understood, Part One: Service Delivery Processes
- Case Study: Recovery Reactions to a Renegade Rodent
- Elements of ITIL Least Understood, Part Two: Service Support
- Case Studies
- Case Study — Preparing for Hurricane Charley
- Case Study — The Linux Decision
- Case Study — Production Acceptance at an Aerospace Firm
- Case Study — Production Acceptance at a Defense Contractor
- Case Study — Evaluating Mainframe Processes
- Case Study — Evaluating Recovery Sites, Part One: Quantitative Comparisons/Natural Disasters
- Case Study — Evaluating Recovery Sites, Part Two: Quantitative Comparisons/Man-made Disasters
- Case Study — Evaluating Recovery Sites, Part Three: Qualitative Comparisons
- Case Study — Evaluating Recovery Sites, Part Four: Take-Aways
- Disaster Recovery Test Case Study Part One: Planning
- Disaster Recovery Test Case Study Part Two: Planning and Walk-Through
- Disaster Recovery Test Case Study Part Three: Execution
- Disaster Recovery Test Case Study Part Four: Follow-Up
- Assessing the Robustness of a Vendor’s Data Center, Part One: Qualitative Measures
- Assessing the Robustness of a Vendor’s Data Center, Part Two: Quantitative Measures
- Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part One: What Did the Team Do Well
- (d) Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part Two
This is the first of a two-part case study of how a large international insurance company performed its initial planning to significantly upgrade its service desk. The firm hired me recently as a consultant to facilitate their planning efforts (implementation to occur later) and to direct them along the lines of the framework of the Information Technology Infrastructure Library (ITIL). ITIL is a set of books that document a framework of best practices for managing infrastructure processes, including the service desk function.
Part One will focus on our efforts to identify and prioritize their overall objectives of why they wanted to do the upgrade and what they hoped to accomplish by it. Part Two deals with the SWOT (strengths, weaknesses, opportunities, threats) analysis we performed. These two activities set the stage for the eventual implementation of the new service desk which is expected to happen within a few months.
One of the first actions my client took in support of the ITIL framework was to change the name their help desk to that of a service desk in support of fostering a service-oriented attitude and approach. Next we agreed to brainstorm the overall objectives of why they were doing this service desk upgrade, and what they hoped to achieve. Sponsors formed a service desk improvement team (SDIT) with representatives from the service desk area, technical services, desktop support, applications and the end-user area.
I facilitated the brainstorming in which participants identified 22 overall objectives for the service desk by using a round-robin brainstorming technique. The team then categorized the objectives into timeframes resulting in seven short-term objectives (within six months), nine medium-term objectives (6 to 12 months), and six long-term objectives (longer than 12 months).
Next the team prioritized each group of objectives using a nominal group technique. In this method team members rank their top three choices (four for medium-term objectives due to more responses) and assign decreasing point values to their selections. That is, the short-term response ranked first by a team member received three points, the second choice received two points and the third choice received one. The sum of total points results in a relative prioritization which I analyzed for each group of objectives.
Short-Term Objectives
The SDIT identified seven short-term objectives. Table 1 below shows their descriptions and priority ranking. The table also shows the distribution of votes in terms of responses receiving three, two or one point.
Table 1 Short-Term Objectives
Rank |
Pts |
Description of Short-Term Objectives |
Distribution |
1 |
11 |
Identify the roles of the Service Desk |
3,3,2,2,1 |
2 |
10 |
Provide a central point of contact |
3,3,2,2 |
3 |
7 |
Improve customer experience and expectations |
3,2,1,1 |
4 |
5 |
Provide consistency |
2,1,1,1 |
5 |
3 |
Be highly compensated |
3 |
T6 |
0 |
Become an entry point for technical career path |
0 |
T6 |
0 |
Be highly professional |
0 |
Analysis:
As mentioned previously, short-term objectives are defined as those that are intended to be completed within the first six month's of initiating the Service Desk. As a result, these objectives are expected to be completed by July 1, 2007.
The top two ranked short-term objectives involved identifying the roles of the Service Desk and providing a central point of contact for users. These responses were nearly identical in priority with 11 and 10 points respectively. These objectives emphasize the need to clearly define the roles, responsibilities and the authority of the Service Desk early on, and to market it as the single point of contact for all IT-related issues.
The next two short-term objectives dealt with service-oriented issues of improving the customer experience and expectations and providing consistency. The one other short-term objective receiving votes involved the staff-related issue of providing competitive compensated for personnel.
Medium-Term Objectives
The SDIT identified nine medium-term objectives shown below in Table 2.
Table 2 Medium-Term Objectives
Rank |
Pts |
Description of Medium-Term Objectives |
Distribution |
1 |
18 |
Maximize the number of 1st call resolutions |
4,4,4,3,2,1 |
T2 |
10 |
Allow engineers to address complex, technical problems, rather than simple ones |
4,3,2,1 |
T2 |
10 |
Identify opportunities to improve efficiencies and effectiveness |
3,3,2,2 |
4 |
8 |
Accurately record and dispatch all incidents |
4,3,1 |
5 |
5 |
Facilitate communication with customers in all areas |
4,1 |
T6 |
3 |
Have Service Desk drive work flow |
3 |
T6 |
3 |
Improve SLAs and OLAs |
1,2 |
8 |
2 |
Improve proactive communication |
2 |
9 |
1 |
Build up a knowledge base |
1 |
Analysis:
A medium-term objective is described as one that is intended to be completed within the first year of initiating the Service Desk. Consequently these objectives are expected to be completed by December 31, 2007
Maximizing the number of 1st call resolutions was far and away the highest ranked medium-term objective with 18 points. This should be a clear-cut metric on which to track, analyze and continually improve upon. The first step should be to determine what the current percentage is of the 1st call resolutions, and then to set goals and timeframes to continually increase this percentage.
The next two medium-term objectives had identical scores of ten points and are related in content as well. Both deal with making the staff in general, and engineers in particular, more productive by working on more critical tasks in a more efficient manner.
The fourth medium-term objective, with eight points, described the accurate recording and dispatching of all incidents. This clearly needs to be done in order for the first medium-term objective of increasing the number of 1st call resolutions is to be achieved. Other medium-term objectives touched on topics such as communication, work flow, SLAs and OLAs, and building a knowledge-base.
Long-Term Objectives
Table 3 below shows the six long-term objectives that the SDIT identified and prioritized.
Table 3 Medium-Term Objectives
Rank |
Pts |
Description of Long-Term Objectives |
Distribution |
1 |
11 |
Identify opportunities to automate |
3,3,2,2,1 |
2 |
9 |
Provide management reports for departmental performance |
3,3,2,1 |
3 |
7 |
Become highly valued |
3,2,1,1 |
4 |
6 |
Attract and retain higher caliber personnel |
3,2,1 |
5 |
2 |
Provide automated customer relationship mgmt |
2 |
6 |
1 |
Enable quicker problem resolution by using 24x7 problem assignment |
1 |
Analysis:
A long-term objective is described as one that is intended to require over a year to be completed.
The top ranked long-term objective with 11 points was the identification of opportunities to automate. Caution should be exercised so as not to rush into automating parts of the Service Desk process without first streamlining the process as much as possible. An automation tool should be selected to fit the process rather than fitting a process to a particular tool.
The second ranked long-term objective is to provide management reports for departmental performance, and this had nine points. The remaining four long-term objectives involved a variety of topics including that of becoming highly valued, attracting and retaining higher caliber personnel, providing automated customer relationship management, and enabling quicker problem resolution by using 24x7 problem assignment.
Summary of Planning a Service Desk Part One – Objectives
In this first portion of the two-part case study, I presented the initial strategy used by a large international insurance firm to upgrade its service desk. I discussed how we jointly decided to first brainstorm the overall objectives of their new and improved service desk and then to categorize them as to short, medium or long-term. Next we prioritized their responses in each of the three categories using the nominal group technique. After I compiled the results of the voting I offered a brief analysis of the responses and their priorities. In part two I explain the results of a similar type of brainstorming in which we identified and prioritized the current strengths, weaknesses, opportunities and threats to the initiative to upgrade their service desk.