Occasional thoughts on business process management, eprocurement, customer service, the dark art of sales and the creatures that inhabit these worlds.

Thursday, May 25, 2006

Adminaphobic knowledge workers

Today I am coining a new phrase - remember, you read it here first - the "Adminaphobic knowledge worker". The what? The well paid, over-ego'd, middle/senior ranking colleague who believes he (let's face it, rarely a she) is too important/busy/needed elsewhere to be bothered with the nuisance of administrative tasks such as purchase requisitioning, timesheets, incident reporting, leave requests etc etc etc. (Read this for an excellent explanation of the "knowledge worker" as opposed to the adminaphobe).

Know anyone like that in your patch?

The challenge for business management is the sickening reality that sometimes these guys are actually right - they may well be a little too important to us in some way, we may be somewhat over exposed, they could well be the "bus man" (the one person you don't want run over by that proverbial bus). Unfortunately they are also frequently arrogantly aware of this and willing to flaunt and abuse their position of power. So what can we do - because we really do want these guys to perform their admin.

An aside but an interesting and relevant little anecdote and a flash back to the malevolence of a previous ORA post. One of our iPOS eProcurement for SunSystems clients was complaining that "the system doesn't work for us". Now, I would say that pretty much everytime I have heard something like that the problem boils down to the fact that their business processes or people are the cause of the problem - not the "system" (and that is not a proud boast on our software, I would say it is a fairly safe general comment about most commercial, mature software applications). Sure enough, the problem was that requisitions for inappropriate spend were being "approved by the system incorrectly". After a little forensic analysis it actually turned out that one of their adminaphobes had handed over his password and responsibility to a group admin assistant to approve his requisitions (I'm too busy for that) and as she had no basis for deciding what was right and wrong she was merrily approving everything that came his way on his behalf.

So how would I approach the conundrum of our adminaphobic friends?

To be continued ..... (don't you hate that).

No comments: