21
KCS Swarming Ways to Gain Efficiencies for Desktop Support

KCS Swarming - HDI

  • Upload
    others

  • View
    8

  • Download
    0

Embed Size (px)

Citation preview

Page 1: KCS Swarming - HDI

KCS Swarming

Ways to Gain Efficiencies for Desktop Support

Page 2: KCS Swarming - HDI

/pnyborg/

KCS Trainer & Knowledge Advisor

ComAround

Agenda

• Tap into service desk motivation

• Swarming Scope & Swarming around today’s support structure

• Where to Start

• Measure for success & proven results

Page 3: KCS Swarming - HDI

The world outside work have changed

The world inside

work have not

Page 4: KCS Swarming - HDI

Talent Management

• If you don’t develop them, some one else will

• Give Employee a voice – the smartest person in the room is all of us

• Engage to motivate

• Increase responsibility based on passion and skills

• Recognize contribution and creativity

• Coach, Care & keep your promises

Keep your Talent

Page 5: KCS Swarming - HDI

Swarming Scope

Page 6: KCS Swarming - HDI

Swarming Principles

• No tiered support groups

• Case move directly to person most likely to resolve (intelligent matching)

• Same person own case until resolved

• Unbound networks, increasing reach

Intelligent swarming as support model

• No tiered support groups

• No escalations from one tier/group to another

• The case should move directly to the person most likely to be able to resolve it

• The person who takes the case is the one who sees it through to resolution

• Unbound networks, increasing reach

Page 7: KCS Swarming - HDI
Page 8: KCS Swarming - HDI
Page 9: KCS Swarming - HDI

Types of Swarms

Dispatch swarming

• Larger teams with dedicated Swarm Masters

– Meet at set intervals, based on organizational need

– product-line focus

– What new tickets can be resolved instantly?

– Validation of tickets before assignment to product line support teams

Page 10: KCS Swarming - HDI
Page 11: KCS Swarming - HDI

Severity swarm

• Small team with Swarm Master on a scheduled weekly rotation

– Provide instant response, and resolve as soon as possible

Page 12: KCS Swarming - HDI
Page 13: KCS Swarming - HDI

Backlog swarm

• Meet on Daily basis

– Address challenging tickets brought to them by product-line support teams

– Replace the role of individual subject matter experts

Page 14: KCS Swarming - HDI
Page 15: KCS Swarming - HDI

Where to Start

Page 16: KCS Swarming - HDI

Build a Foundation

• Executive buy-in & Executive Sponsor

• Find the people you want in your pilot – challenge them

• Design your swarm – and prepare to re-design once you start

• Measure and promote desired results

Pilot for Further Buy-in

• Start with a pilot (identify a collaboration group)

Organizational Network Analysis

• Let the Support Analysts design the process

Triggers, ability, motivation for seven scenarios

• Iterate on the process

• Start with manual process and refine your:– requirements based on that experience

– People profiles

– Measures

• Communicate goals

Page 17: KCS Swarming - HDI

Measurements

What to Measure

• Backlog rate

• Time to Assign

• Time to Efficiency

• Duplication of Effort

• Net Promotor score

• Number of escalation and Time to Resolve (tiers vs teams swarming)

• Agent buy-in and engagement

Page 18: KCS Swarming - HDI

Proven Result

• Call backs Reduction

• Reduction in time to resolve

• Reduce time to proficiency by 50%

• Increased Capacity per agent

• Achieve 90/0 in self-service

• Accelerated learning and skills grow

• Backlog down

• Increased Employee Engagement

• Reduced new hire time (up to 50%)

• Increased customer satisfaction

• Less Customer Effort

• Better way to deliver on Brand Promise

• Better Customer Experience

Learn from the Best

Page 19: KCS Swarming - HDI

Lesson learned

• Tweak and re-engineer the system many times in the initial phase as you get experience

• Collaborate on the new process itself: managers, engineers, project leader

• Recognize ALL key contributions, and highlight the heroes

• Pilot Team - needs to deal with ambiguity

• Offer more then collaboration request per case

• Measure parameters in the swarm to quickly assess new changes to the process

• Integrate short cuts where ever one is identified

• Mandatory to participate, no more tiers

• Group skills by technology not product

Lesson learned

Page 20: KCS Swarming - HDI
Page 21: KCS Swarming - HDI

Sources https://www.forbes.com/sites/mikemyatt/2012/12/13/10-reasons-your-top-talent-will-leave-you/#f68800738a62

https://insightsresources.seek.com.au/7-reasons-why-you-are-losing-your-top-talent

https://www.gartner.com/doc/reprints?id=1-419YGGE&ct=170526&st=sb

https://www.forbes.com/sites/larrymyler/2013/09/02/why-are-70-of-employees-disengaged-and-what-can-you-do-about-it/#434cbe987303

https://www.serviceinnovation.org/included/docs/kcs_publication_bmc_swarming.pdf

https://medium.com/@JonHall_/itsm-devops-and-why-the-three-tier-structure-must-be-replaced-with-swarming-91e76ba22304

https://www.fastcompany.com/3068771/how-employees-at-apple-and-google-are-more-productive