Once upon a time there was this guy who left everything behind to face a new challenge. Opportunities were there, sure, but they weren't that good. When all is said and done, there isn't much to say about retirement plan, health insurance or a new car... It wasn't the conditions but the challenge that brought the man in.
He wasn't the ideal candidate. Far from it. But, for some jobs, the ideal candidate is an HR wet dream. He didn't speak the language, had a very narrow focus, and didn't exercised leadership as he should have. As far as I understand it, he didn't even knew what leadership is, he took it all for granted.
It didn't took long for things to go sour. People began asking for reassignment ("I do not know what I should be doing.", "I do not understand what is expected of us.", "What are we here for? What is the plan?"), or just plainly quit. People depending upon his work began to ask questions ("What is he doing?", "Why is he here?", "What is his role?", "Should I go through him for that?"). Then the criticisms ("We all agreed upon that, but he doesn't know/remember/understand.", "He isn't from around here, how can we trust him?", "He doesn't know us."). Possibly, he ran afoul of some deal, picked the wrong resource or contractor, made the wrong friends, was unable to gain the trust he needed.
In the meantime, he established quality standards, reasserted the end-user responsibility in requirements analysis, brought a new methodology and new talent in.
And then he was out.
Not of his own choosing.
A few words to the wise:
He wasn't the ideal candidate. Far from it. But, for some jobs, the ideal candidate is an HR wet dream. He didn't speak the language, had a very narrow focus, and didn't exercised leadership as he should have. As far as I understand it, he didn't even knew what leadership is, he took it all for granted.
It didn't took long for things to go sour. People began asking for reassignment ("I do not know what I should be doing.", "I do not understand what is expected of us.", "What are we here for? What is the plan?"), or just plainly quit. People depending upon his work began to ask questions ("What is he doing?", "Why is he here?", "What is his role?", "Should I go through him for that?"). Then the criticisms ("We all agreed upon that, but he doesn't know/remember/understand.", "He isn't from around here, how can we trust him?", "He doesn't know us."). Possibly, he ran afoul of some deal, picked the wrong resource or contractor, made the wrong friends, was unable to gain the trust he needed.
In the meantime, he established quality standards, reasserted the end-user responsibility in requirements analysis, brought a new methodology and new talent in.
And then he was out.
Not of his own choosing.
A few words to the wise:
- never take leadership for granted ;
- there is no excuse ;
- learn the game before playing it ;
- listen carefully ;
- talk sparingly but, for God sake, *say* something.
Posts
No comments:
Post a Comment