Skip to main content

Unsourcing

I recently read a very interesting article in the June 2, 2012 Technology Quarterly edition of The Economist magazine.   There is a new trend in technical and customer support that relies heavily on the contributions from actual customers, “Unsourcing” involves the use of online communities to enable peer – to – peer support among users.  Instead of speaking to a paid internal or outsourced service desk analyst, customers post issues to a central forum and wait for answers from experienced users.    To create unsourced communities, companies are setting up discussion groups on their website or leveraging social networks like Facebook and Twitter.  As you can imagine, the savings can be considerable.

Gartner estimates that user communities can reduce support costs by as much as 50%.  When Tom Tom, a maker of satellite navigation systems, switched to social support, members handled 20,000 cases in the first month , saving the firm around $150,000.  Best Buy has instituted an online support group and has estimated that its 600,000 users save the company $5M annually.
Lithium, the software company that provided Tom Tom’s and Best Buy’s systems, engages experienced users by creating a game environment.  “Gamification” works by awarding points for helpful answers.  This allows helpers to achieve different levels within the game and attain recognition titles such as “super fan” in the top 0.5% of responders.
Super fans are highly prized by companies because they account for a disproportionate number of responses.  For example, in Lenovo’s support network for personal computers, a mere 30 users account for nearly half of 1,200 accepted solutions.

While cutting costs using peer – to – peer support may be attractive, there are limits and risks to the use of unsourcing.     Peer – to – peer support may not be appropriate for issues with privacy, confidential access, legal or regulatory concerns.   High volume, high profile or complex deployments may also require more control.   
How and when you apply unsourcing will be an individual organization's decision.  However, the concept certainly has merit and is worth exploring for many environments.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem