Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Tue Sep 28, 2010 1:41 am Post subject:
Firstly there is no such thing as a "typical" figure or benchmark for such behaviour. Nor is there an average or a tolerance threshold.
The issue is management and control.
As far as casual requests are concerned, the only acceptable number to deal with is none whatsoever.
Control is not retrospective. You can empower your engineers to make decisions "on the spot", but you cannot permit them to make uninformed decisions and the limits of their scope and authority must be clearly defined.
How do your service desk engineers establish that the person waylaying them is authorized to make the request?
How do they establish priority for the request?
How do they inform "HQ" that they have been delayed?
How do they account for their time?
What do they do if they are not the best person for the particular task (but think they can muddle through okay)?
How do they access the history of the service component(s) they are asked to do something to?
Of course, they are stymied if a change is required anyway.
These kind of issues need addressing. Nevertheless there is also the issue of travel and saving journeys where remote sites are involved. So, still dealing with all the control issues, it might be prudent to enable an engineer to perform a number of actions on one visit, if (to repeat myself) you still achieve full management control of the activity by some means. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum