What Are The Drone Anti-jamming Systems Technology?
Bain lti slides hdi
1. Session 813
Coming of Age
Overnight
Shane Kobus
Peter Dorfman
Senior Client
Services Manager
Bain Capital, LLC
Principal Consultant
Leveraged Technology
Inc.
BainCapital
20. Session 813
Thanks for
listening
Shane Kobus
Peter Dorfman
Senior Client Services Manager
Bain Capital, LLC
Principal Consultant
Leveraged Technology Inc.
skobus@baincapital.com
peter.dorfman@levtech.com
BainCapital
Editor's Notes
Application Support?
Extremely rapid growth of the Business (20% annually)
Growth brings rapid change, can lead to operational chaos
Extremely high expectations for service
Managing Directors, deal professionals need and expect high levels of support, polished and personal service
Low tolerance for error and expectation of immediate response
History of delivering on critical incidents but underperforming on simple, routine issues, eroding end user trust
Small Service Desk, small company operating style
Support provided through e-mail contact only – no longer effective
Moved to phone support April 2007
Weak performance management/metrics
Growth has made former casual relationship management style obsolete
Senior techs needed to protect time for supervision/management
A big company that really, really misses being a small company.
IT and the Business did not clearly understand one another
There were no Service Level Agreements and no clear definition of effective service
The Business lacked confidence in the Service Desk
The Business saw support for trading systems and other critical applications as separate from the Service Desk mission
“Helpme” emails were not an effective medium for incidents; high expectations for phone support
Service Desk staff too junior to meet expectations of the business
Service Desk lacked clear process definitions
Incident management system (Altiris) incompletely implemented
Focus effort on mastering routine issues (fix the easy stuff)
Train analysts on soft skills
Augment staff with more senior Service Desk analysts and engineers
Proceed with phone support adoption
Implement ACD switch
Design and adopt a comprehensive new support process, based on ITIL® principles and focused initially on:
Incident Management
Problem Management
Change Management
Build out Knowledge Management process and knowledge base
Key component of the Problem Management process
Make knowledge base available, eventually, to end users via Intranet
Enhance performance metrics and hold staff to them
Adopt Service Level Management
Operational Level Agreements between Service Desk and its partners
Service Level Agreement with the Business
Market service improvements, especially phone support launch, internally to rebuild end user confidence
Implement a serious asset inventory; create an Asset Management process
Precursor to Configuration Management process
Speak to the visualization – this is the start of the Incident Management process:
Value of process visualization for team’s understanding
Multiple channels of incident reporting
Urgent call process for trading issues
Involvement of the end user
Use of the knowledge base
Note separate flow for Service Requests (can include if there is time)
End Point of Incident Management process
Opportunities for first contact resolution
Operational Level Agreement targets – exceed threshold?
All incidents confirmed as resolved with the end user
Opportunity to add new content to the knowledge base when a new error is resolved
ACD scripting: After call work; log back into the queue
Functional Escalation
Note difference between this and Hierarchical Escalation (separate process for issues that exceed SLA thresholds)
Distinguish between issues that stay at the service desk and those that involve service partners
New errors trigger Problem Management process
Ownership of Incidents – all Incidents are sent back on resolution to the Level 1 analyst who originally opened (build relationships with end users)
Change Management process
Describe Change Review Board
Evaluate feasibility
Involvement of Development (and other service partners)
Change Release process
Leverage Altiris functionality for knowledge authoring, search, linking to Incidents
Roles and responsibilities
End user
Author, Subject Matter Expert, Reviewer/Approver
Knowledge Manager (responsible for content quality)
Administrator
Documented processes
Generating, maintaining, retiring articles
Searching, linking
Content quality standards
Taxonomy of issues documented
Set expectations for analysts to contribute