![[University of Washington]](http://www.washington.edu/
home/graphics/uwid.gif){kind=small}
David Wall davidw@cac.washington.edu
Modified: 15 May 2002
For the Faculty/Staff Consulting group
These ideas for improving customer service or group processes were suggested by consultants during disussions in March 2002.
| a | Make QnA answers archive more easily searchable |
| b | Need consulting knowledgebase |
| c | Need index of tools/resources (eg, Rref, FaqFinder, etc) |
| d | Review/improve quality of answers given via phone |
| e | Group meetings could be used to present consulting problem skills or technical info |
| f | Systematic tracking of active problem areas so that consultants have access to latest info. Perhaps Bugzilla could be used. |
| g | Make better use of the support-l list by sending tech updates |
| h | Increase knowledge of dept. support staff and do more collaboration |
| i | Improve communication giving more access to who knows what |
| j | Facilitate communication by getting information about changes to the people who need to know |
| k | Access to information about FSCO and C&C projects |
| l | Integrate call tracking with QnA |
| m | Outreach from FSCO to the TechSupport group re who covers what |
| n | Audits of consulting answers to find opportunities to improve |
| o | Better tools for customers to find solutions on their own |
| p | Use our student staff more, and more effectively |
| q | Create better FAQs and documentation by having subject experts write to a standard format, then let publications experts do design, layout, polishing. |
| s | Create more useful and accessible documentation by structuring documents to perform multiple roles. |
| t | Pass project ideas to students, then use monitoring processes to get work completed |
| u | Need generally more and better information of all kinds |
| v | For tasks like testing a software product, make specific people responsible |
| w | Improve Router'sRef |
| x | Do outreach to departments to deliver our messages and get to know the customers |
| y | Do a post mortem when any project is completed, then record and distribute lessons learned. |
| z | Provide/develop/support project management tools for consultants |
| aa | Increase the knowledge among FSCO consultants about what each one does, knows |
| ab | Build tools so users can figure out modem-over-quota situations |
| ac | Increase personal communication within FSCO group |
| ad | Better address needs of people who mistakenly write to "help" |
| ae | Improve coordination with other UW helpdesk groups |
| af | Explore tools like camtasia to add animation/voice to FAQs |
| ag | Add a chat service for customer support |
| ah | Better knowledge of other C&C groups and projects |
|
|
Computing & Communications David Wall davidw@cac.washington.edu Modified: 15 May 2002 |