For my years as software developer, I often wonder why a good boss is so hard to find. Lately I have been lucky enough to work with the best boss I have seen. Just like the difference between a so-so software developer and a brilliant developer, the difference is huge and matters even more, since a manager is responsible not only for his/her work, but the work of the whole team (or organization). So what makes the difference? I know it's not "technical" because the managers I have seen or worked with all mastered the "technical" side of management (project planning, resource planning, scheduling, etc, stuff required for the PMP certificate). I know it's not related to intelligence either. (True, my current boss is super smart, but I had worked with an excellent manager before whose intelligence caliber is not on par with my current boss but still makes a very good manager.) Some star performers, once promotion often become micro-managers and stay mediocre. Nor is it related to how "nice" the person is. A "nice" manager often become wimpy and let the team run amok.
So what is it then? As usual, when I am baffled by a question I start to read about it. One thing I soon find out is, most management books are bad (and boring). For those not so bad nor so boring ones, some are too strategic and too theoretical, some are just plain Machiavelli rehash. I forgot how I ran into this book (probably from Amazon recommendation). It had stayed in my book pile for a while. I started reading it last night (you can tell I get more free time in my current job). A few pages into it I was hooked. It answered my question why a good boss is so hard to find. I have yet to see if the advices in this book will make someone a better one, but I am secretly thinking of sending a copy to my current boss (who always lamented she was not a good enough manager, a sign she's actually fairly good simply because of the awareness). It will be really fun.
No comments:
Post a Comment