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 the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…