Home > KCS Adoption Guide > Appendix A: Opportunity Assessment Survey

Appendix A: Opportunity Assessment Survey

Click here for a pdf of this sample Opportunity Assessment Survey.

 

  1. Number of Support Analysts?  (worldwide audience for Knowledge sharing/KCS)
  2. Geographies – how many support centers?  (centers with more than 6 people)
    1. Locations and number of people in each?
  3. Company employees vs. partner employees (outsourced)
    1. # of company Support Analysts
    2. # of outsourced Analysts
    3. Number of partner/outsource partners
  4. Products – how many product families or domains are supported? Most support organizations support a wide variety of products and organize them into groups or families, which in turn have a certain number of Support Analysts associated with supporting a product family. 
  5. Support structure
    1. How many levels of support do you have? (how many escalations happen between the customer’s first point of technical contact and development?)
  6. People and product groups (see the KCS Adoption Planning Matrix worksheet under Adoption Strategy and Road Map in the Adoption Guide.)
  7. Workload
    1. Number of incidents/cases closed per month
    2. %  from customers
    3. % internal (if applicable)
    4. For internal help desk, average incidents/user/month 
    5. Channels of incident/case submission by customers (the total of 1-5 below should be 100%)
      1. % via web submit (click to create/submit an incident)
      2. % via chat 
      3. % via email 
      4. % via phone call 
      5. % other  (please describe, ie system generated)
    6. Utilization rate? (% of time Support Analysts are working on the queues – usually in the neighborhood of 50-65%)
  8. Current tools
    1. CRM/case management system(s) 
    2. Knowledge management system(s) 
    3. Other key tools the Support Analysts use
  9. Problem solving methodology
    1. Training on problem solving?  (e.g. Kepner-Tregoe)
    2. How is collaboration enabled?  (wikis, blogs, IM, email, phone, face to face, webex)
    3. Technical mentoring program? (formal, informal, none)
  10. Content development process
    1. Is there a knowledge management process in place?
    2. Is there a knowledge base?
    3. What are the criteria for what gets put into the KB?
    4. How and when is content for the KB created?
    5. Is there a life cycle defined for the knowledge articles? (yes, no)
      1. Life cycle states?
    6. Do the users of the content have a way to give feedback to the creators of the content? 
    7. How is the content in the KB kept up-to-date? 
    8. What measurements are in place to assess:
      1. The usefulness of the content
      2. The completeness of the content (% of what is known Vs what gets published?) 
      3. The timeliness of the content (time to publish)
  11. Customer self-service model?
    1. Briefly describe the kinds of self-service delivery are used:
      1. Integrated into the application user interface
      2. Automation (detect, report, repair)
      3. Support portal or Web based self-service
        1. Customers sign in to use the web self-help (yes/no)
        2. Types of self-help offered? (FAQs, search KB, online docs)
        3. % of customers who use the web before opening an incident?
        4. % of time the customers find what they need on the web?
  12. Organizational goals – what are the key initiatives for the company this year? (at least the top three)
  13. What is your long term vision for Support? 
  14. How is support viewed by other departments within your company?  (ex.   Very well integrated, it is the voice of the customer, or not integrated with sales but integrated well within development).
  15. Describe any major changes or initiatives that have occurred within support during the past three years and any impact on employee or customer satisfaction.
  16. What role does support play in contributing to the key company initiatives?
  17. Organizational measures - what are the executive level metrics used for the service organization?
  18. Performance assessment – how is the Support Analyst contribution measured?
  19. Teamwork – how is teamwork encourage and assessed?
  20. Support Analyst rewards and recognition – what programs are in place?
  21. Teams based rewards and recognition – what programs are in place?
  22. Management communications:
    1. Methods?
    2. Effectiveness- is there a measure for the effectiveness of communications?
      1. Do people understand the goals and objectives of the support organization?
      2. Do people understand how they are measured and why?
  23. Observations about the culture:
    1. Is it combative/competitive or collaborative?
    2. Is the leadership model focused on command and control or alignment: providing task level direction vs influence? (employee engagement, participation and enablement)
    3. To what extent is there trust between Support Analysts?
    4. To what extent do the Support Analyst trust and respect their managers?
    5. To what extent do the managers trust and respect the Support Analysts?
    6. Do people deal with contention and conflict or it is avoided/ignored? 
    7. If people deal with contention/conflict is it in a constructive way?
    8. To what extent are people willing to make commitments and be accountable?
Viewing 4 of 4 comments: view all
The PDF download/link at the top of the page appears to be a corrupt file. Tried a couple different browsers as well as downloading and opening with Acrobat all gave the same result.
Click here for a pdf of this sample Opportunity Assessment Survey.
Posted 23:50, 4 Nov 2014
I second the comment on the PDF being corrupt.

Adobe Acrobat can't open it.
Posted 22:45, 21 Jan 2015
To download a working PDF of this article, click on the PDF icon link that is displayed in the upper right corner of the page under the Search field.
Posted 23:55, 29 Oct 2015
This page should be listed in the contents of the KCS Adoption Guide.
Posted 12:02, 7 Jan 2016
Viewing 4 of 4 comments: view all
You must to post a comment.
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.