Step 3: Develop Blueprint for Change

Taking the outputs from the Rapid Assessment phase, the team will then work to define future state requirements to support process efficiency, cost reduction and new strategic initiatives in the form of a Blueprint for Change. At this point the teams may expand to include business management and user groups to contribute and buy into the end state designs. Workshops are utilized at this stage to rapidly produce consensus based solution blueprints driven by business and customer focused strategy and objectives.

On collaborative engagements, it is particularly important to communicate requirements in plain English. The following example Blueprint deliverable, representing an Incident Management scenario, is structured to communicate the change that needs to take place to all stake holders.

blueprint01.jpg

Whether outsourcing or improving in house IT service management functions - people do what is measured. Here is an example of Key Performance Indicators that are developed as part of Blueprinting for Incident Management:  

  • Volume of Incidents/Service Requests by Priority

Measures the volume of Incidents/Service Requests by priority.  Priority is defined by the impact on the business and the urgency with which a resolution or work-around is needed.

  • Time to Restore Service

Measures duration of Incident opened to service being restored for the user.  Can be measured against a target, e.g. 85% of Incident service restored in 4 hours. 

  • Time To Resolve Service Request

Measures duration of Service Request opened to all tasks/activities within the service request being completed.  Can be measured against a target, e.g. 85% of Service Requests resolved in 5 business days. 

  • Breached Service Level Targets for Incidents and Service Requests

Measures the duration of Incidents/Service Requests that have failed to achieve their service level targets.

  • Service Desk First Time Fix

Measures the percentage of incidents resolved by the Service Desk without referring issue to any Resolver Groups. Requires support from the end to end support chain.  Does not include Service Requests which are handled under a different set of performance metrics.

  • Knowledgebase

Number of additions to the knowledgebase