Confessions of an IT Manager_Phil Factor
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
The Incident <strong>of</strong> 'The Two Johns' –<br />
<strong>an</strong> <strong>IT</strong> M<strong>an</strong>ager confesses<br />
First published 20 March 2006<br />
Keep your friends close <strong>an</strong>d your enemies closer; but<br />
try not to muddle which is which. <strong>Phil</strong> exploits his<br />
cloak <strong>of</strong> <strong>an</strong>onymity to confess to a grievous mix up in<br />
his m<strong>an</strong>agerial appraisal <strong>of</strong> two team members.<br />
As <strong>an</strong> <strong>IT</strong> M<strong>an</strong>ager, I used to love doing staff appraisals. These rituals come<br />
by different names in different comp<strong>an</strong>ies, be it 'perform<strong>an</strong>ce review', '<strong>an</strong>nual<br />
report', 'staff assessment' <strong>an</strong>d so on. There are periodic crazes for tinkering with<br />
the process, <strong>an</strong>d pinning a different name on it, but the tradition itself remains<br />
basically the same.<br />
I appreciated the value <strong>of</strong> st<strong>an</strong>ding back <strong>an</strong>d taking stock <strong>of</strong> how ones 'direct<br />
reports' were shaping up. To mull over the events <strong>of</strong> the year, advise them as<br />
best one could, <strong>an</strong>d to do what one could to help the adv<strong>an</strong>cement <strong>of</strong> their<br />
careers. I looked forward to the process … until the incident <strong>of</strong> 'The Two<br />
Johns'<br />
In my development team, I had two programmers who couldn't have been<br />
more different. They were both called John. Clever John found the world <strong>of</strong><br />
work easy. He ploughed through every job he was given with supercilious ease.<br />
He was a useful member <strong>of</strong> the team, though he seemed to get bored with<br />
mund<strong>an</strong>e jobs <strong>an</strong>d <strong>of</strong>ten overcomplicated his code, just to keep himself amused.<br />
Dull John, by contrast, was a plodder. He didn't seem to read enough to keep<br />
up-to-date <strong>an</strong>d he was inclined to ask for help at every turn. He was content to<br />
do just enough to tick along but stay invisible in the team.<br />
When appraisal time approached, I put together reports for every member <strong>of</strong><br />
the team, as usual. Because hum<strong>an</strong> nature dictates that it is easier to remember<br />
negative things about people, I used to keep a notebook with me to record every<br />
good thing that happened in the day-to-day work <strong>of</strong> the team. By the end <strong>of</strong> the<br />
year, the appraisals flowed naturally from these notes.<br />
Clever John's appraisal was a work <strong>of</strong> unstinting praise, emphasising his<br />
readiness to take on more responsibility <strong>an</strong>d the maturity <strong>of</strong> his attitude to the<br />
work. I liked the way he took on the 'ownership' <strong>of</strong> problems <strong>an</strong>d issues when<br />
they happened <strong>an</strong>d told him so. Dull John's report was more <strong>of</strong> a struggle. I