1 / 21

Continuous Improvement

Continuous Improvement. Turning Sticky Notes Into Teamwork And Quality Assurance. Ashley Weese Iowa State University. Overview of it services. Who we support. Who we were at the time. Employees did not have the same skill levels Low moral Employees who didn’t want to assist others

kura
Download Presentation

Continuous Improvement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Continuous Improvement Turning Sticky Notes Into Teamwork And Quality Assurance Ashley Weese Iowa State University

  2. Overview of it services

  3. Who we support

  4. Who we were at the time • Employees did not have the same skill levels • Low moral • Employees who didn’t want to assist others • Overthinking • Lots of uncertainty due to budget • Employees were put off from the leadership change • Employees were relocated to be within earshot of each other • Single Point Of Contact (SPOC)

  5. goals • What do we do? • What expectations do we have for each other/ourselves? • Reduce the amount of time the customer waits for service • Create a team atmosphere • Improve quality • Gain trust throughout our team and the IT Services department • Improve moral • Start TCO – Total Contact Ownership

  6. Ideas…Where in the world did we come up with this? • Recent restructuring of positions • Former manager didn’t have the energy to deal with the “us vs. them” mentality • It was a perfect time to implement some changes that would improve our services and our teamwork.

  7. process • Created multiple 30 minute sessions with ½ of the team in each session • Two-person teams that rotated after each scenario • Gave everyone an opportunity to work together. • Each team was equipped with sticky notes and a marker and then teams were provided with scenarios based on • Expectations of each job duty • Previous calls that year • Teams were given two minutes to work together • Asked to write down five • Expectations • Different troubleshooting questions they would ask the customer. • After time was up, each team submitted the sticky notes to share and discuss amongst the group. • Other sticky notes were added we the group discussed ideas.

  8. implementation • Created improvement sessions • What do we do? • What are the expectations? • Common Calls – What questions to ask • How to find answers • What tools should we be using • Rotating groups • Manager proctored, but didn’t contribute • Scenario based Are you on or off campus??

  9. Try it out • Scenario 1: • I am not able to get email messages on my iPhone. Can you help?

  10. Try it out • Scenario 1: • I am not able to get email messages on my iPhone. Can you help? • Questions: • Are you using a wireless connection or a data connection? • When was your last message received? • When was the last time you changed your password? • Are you able to open a web browser and go to Google? • Can you restart your device? • Can we review your server settings?

  11. Try it out • Scenario 2: • Help! I can’t log into my computer!

  12. Try it out • Scenario 2: • Help! I can’t log into my computer! • Questions: • Are you on or off campus? • Are others in your area having the same troubles? • When was the last time you were able to login? • Can you restart your machine? • What does your screen look like? • Are you getting an error message?

  13. Results:What to document in the ticket

  14. Results:Expectations of the group

  15. Results:expectations Definitions: In the queue: logged into the queue, auxed in the queue, not taking non-queue calls, not making a non-queue call Available time: time spent on a queue call or available for the next queue call. When calculated for a phones day, only hours that the phone lines are open (7:30am-4pm over breaks and summer) will be used. The formula used will be “Total time logged in” – “Total time auxed out” + “Time scheduled for meetings in Outlook” = “Total available time” • Lunch Expectations (Phones, Installs/Email): • Will select an available lunch hour and put the time up on the lunch board by 10:30am. • If selecting the 10:50-noon lunch, will be in the queue between 12pm-1:10pm • If selecting the noon-1:10pm lunch, will be in the queue between 10:50am-12pm. • If selecting the 1-2:10pm or Other lunch, will be in the queue between 10:50am-1:10pm. • Paid time off expectations (Phones, Installs/Email): • If you need to take the day off after the initial schedule is distributed, find someone who is not otherwise scheduled to fill in for you before that day. Inform the team of these schedule changes by emailing scnotice@iastate.edu. • If you are sick, email scnotice or call 4-4000 and to inform the team. If someone else is available, they will fill in for you. You will take over one of their days in the future. • If you need to leave early, email scnoticeto inform the team. If you do not find a substitute you will still have the 6 hours of available time.

  16. Results:expectations • What we do on each scheduled phone day: • Will abide by the lunch expectations and paid time off expectations outlined above. • Will be in the queue between 8am-9am for the early morning rush. • Will have at least 6 hours “available time”. • What we do on each scheduled email day: • Will abide by the lunch and paid time off expectations outlined above. • Will handle all email tickets assigned by the end of the day. • What we do on a backup manager day: • Create CEL and premessage in “outage” situations • Check for tickets in Employee Technical Services that are not assigned to a person • Remind people of tickets that have not been updated in over 1 business day. • Be the go to person when there is a problem that cannot be solved • Could be a technical issue • Could be an external/staffing issue • Run the 8:15am phone team meeting

  17. Results:expectations • What we do on each non-scheduled day: • Pick up coverage for anyone out sick.  Email scnoticeif you are trading the day with someone. • If you are not picking up sick coverage, you do not need to log in, you do not need to log in from 8am-9am, you do not need to log in for lunch coverage, you do not need to sign up for a lunch time. • Work on any tickets that are assigned to you, keeping customers working is always the top priority. • System administration work.   • Training • Creating specific trainings assigned to you • Training others on a specialty you have • Watching training videos

  18. Post Sticky notes • All the sticky notes were typed up • Sent documented notes to the group • Some information was documented in our Knowledgebase • Idea of what training was needed for tools • Created a Quality Assurance form • Started one on one sessions with management • Implement the exercise into weekly staff meetings

  19. Quality Assurance Form • Greeting • Troubleshooting Steps Used • First Call Resolution • Customer Service Skills • Appropriate Tools Used • Call Handling • Documentation • Asset Information • ITS Representation

  20. The Results Are In • People finally were working together • It took awhile, but over the following months you could see the bonding that was taking place • Willingness to help increased • Positive customer feedback • Employees were building relationships

  21. Questions? Ashley Weese aweese@iastate.edu aweese.public.iastate.edu/SIGUCCS12.html

More Related