Office productivity tips – Beware of a Hero in your office

I was reading a nice article  on office productivity, written by Alex  and tweeted by Pallav.  Well said that for small offices you should be beware of a hero there. Almost every office has a hero who works late at night, who comes early in the morning, proactively jumps into various critical works and he is no doubt very enthusiastic with a flair of leadership.

But the problem arises when you have other teams in office and he is a part of some team. His heroic acts can demotivate others from their work and if managers appraise or reward the hero publicly in a different note, then there is obviously an adverse effect on others. Rather being motivated, they feel more isolated and not related to their work. Everybody starts depending on the hero and the team cohesiveness starts degrading. When a team can rely on a hero, they don’t need to grow and learn collectively. They don’t need to get better. They can coast along, which serves no one in the end.Your quality of product or service will degrade gradually and in handling your customer relationship, your team will be reluctant. Office politics and office gossip will increase. Customer will be unhappy, angry and ultimately your revenue will suffer.

So it would be wise not to praise and motivate one hero rather it would be wise to motivate the whole team without discriminating anyone specific. Involve everybody, distribute responsibility evenly in team and set measurable metrics for everybody so that everybody can relate themselves with the vision, mission and goal of the company. Appreciation should be there but it should be in a way that others can take it from heart and get the zeal to do more for the organization.

It is wiser to keep 10 all-rounders rather keeping one hero in your office.

Interesting insight here – http://al3x.net/2010/01/09/dont-be-a-hero.html

Related articles by Zemanta

• Don’t Be A Hero (al3x.net)

post [with Zemanta]" href="http://reblog.zemanta.com/zemified/76bb8fd1-843d-4f70-8cb1-8cb56b54fda9/">

Users who found this post were searching for:

No related posts.