PM Blog from my company postings

This is one of the blogs i had posted in my company site specifically to my team:

Saying “Hello”
Managers job is to get the job done. So whatever it takes he has to do build that good relationship and keep it up with the team to get the job done. One of the key aspects in that context is saying “Hello” to stay in constant touch with the team members. Saying Hello does not stop at Hello, How are you? What did u eat for the day? It is goes to the next level of Hello! How are you doing what you are doing. Getting to know quickly on what he is doing and provide necessary guidance, priorities if required. If not just listen, appreciate and move on. It could happen in corridor or over coffee or at water cooler.
Some folks are great in managing their work, link responsibility, driving others and getting their job done. But they might feel shy of regular status reporting whatever format – email, verbal, messenger whatever. Too modest to feel that I’m tom-taming my work or advertising or spamming my bosses mind and emails. Fair enough, say Hello in the corridor, you feel better. Visibility is as important as hard work.
We sometimes hesitate to talk work over lunch or over coffee. Yes I understand it too much of work related talks. But what the heck, it is interesting topic as well. And that’s where good ideas flow through your free mind and discussing with like minded people.

Leads expectations:
However large team you are heading you would always have 10-12 direct reportees only at max. Because you would have put a hierarchy structure to manage things. And the important thing is to insist on your direct reportees to stay in touch with their team members constantly daily however busy you are. Leads and managers need to carve out 25%-40% of daily time for interaction.
Technical leads and newly promoted leads are likely to be solo workers. They are efficient, intelligent, knowledged in individual contribution. But their expectation is to lead the team and get the job done and increase fellow workers knowledge of the system and application. Lot of inhibition exist to interact, direct, guide others. And they take shelter under the excuse of working on some important project related things solo. Important things yes, no doubt and appreciate the hard work but they still have to carve out that 25-40% time on mentoring, guiding their team members. No excuse there.
There might be some smart chaps out there in your team who question your authority, knowledge. But you have pushed yourselves there, or has been put there and you got to manage them taking their confidence in and there is no looking back now. And there is a management backing for you to stay and do good there anyway.

Team member’s expectations:
You should always look up for growth and don’t be content with what you are doing. Can not constrain yourself to doing XLS or XML work alone if your job demands only that. No actually company demands a lot more because our IT company is a knowledge pool company. And we have to build technical knowledge in the forming years. You got to gain that knowledge like a child. There is a lot to cover on technology, process, client interaction, business, application knowledge. First is to start with what you are assigned and then wondering what this assignment has got to do with this application. And then wondering what this application is all about. There is lot of help, men, material available to gain that knowledge and ask questions.
It is like coming to Bangalore first time and knowing home to office way first week. But by the end of 6 months you would know MG Road, Brigades, Forum, all entertainment hubs and places. Same here in 6 months you got to gain that application knowledge, in and around your module and assignment deeply well. Just go a little beyond that job assignment given to you step by step.