| Audience -Author- |
| Context |
| Goals |
| Resources |
| Input |
| Output |
| Benefits |
| Database |
| Admin Tools |
| Measures |
| Conclusion |
Conclusions:
- Do more cooks spoil the stew? Not when your making stone soup. It is impossible for one staff member to be in a position to solve all of the problems in the labs. Although many of us have overlapping capabilities, often only one of us is available to respond. This problem reporting process maximizes staff time, by offering up the problem to multiple people. The other staff members can quickly and easily determine whether the problem has already been resolved or not, and act accordingly.
- Should we drop the email function and have an open browser window with auto-refresh? Having each report emailed to several people necessitates that we all wade through needless messages at times. Perhaps we can leave the Administrator tool open on the desktop and won't need the email prompt after time.
- Refine search and report functionality? This is an exciting area and I believe I will know more once I have had a semester to fill the database and run reports.
- Use reports to revisit training strategy? One very exciting potential here is that I will be able to see which problems are often reported even though they might have been easily resolved on site by the student employee. Spotting these patterns will dictate reorganization of training topics.
Page URL http://www.d.umn.edu /~jdavis/planb/rconclusion.html
Last Modified on Monday, 27-Mar-2000 13:01:29 CST
©2000 Jason Davis email: jdavis@d.umn.edu
Presented at the Great Lakes Academic Computer Lab Management Conference on March 3, 2000.