Ideally every team should maintain a bell curve. That being said, this was a recent discussion I had with one of the seniors. ‘Freshers are lenient, reckless & lack professionalism/experience’ he said. But that is the whole point. Everyone was a fresher once. Freshers are enthusiastic to embark on their professional journey, are not bounded by professional processes, can think out-of-the-box. Just that they need proper guidance, relevant training & due diligence.
Micro Management kills the trust. Or it proves that there is no trust at the first place. And Freedom breeds innovation. It is when you give people the power & the freedom that ideas originate. And one out of five/ten ideas works out to be superb. It is when you trust in your team that they perform. When they know you are backing them. You believe in them & in their work. In their potential. A strong manager have full trust is his/her team – it is about the tasks, work and the value-adds, innovation. It is not about ‘controlling’, it’s about ‘managing’. Ever had a micro-management incident in your team? How did it impact the team morale? Or how a strong manager built the trust & team pulse?
A strong manager backing the team is the foundation to a successful team. A team succeeds when you entrust them to deliver & have full confidence in their caliber. It’s like a family, no one should point at your team for weakness 😉 at the same time internally you might need to introspect & keep improving. What say?
For some projects we should rename the ‘Onshore-Offshore’ model to ‘Manager-Worker’ model 😛 Where Offshore team is taken for granted. Additionally Offshore team is at the back-foot by default. But why? We should learn to ‘prioritize’ the work items and respect each other’s personal time. Learning to say ‘No’ in a constructive way is an art you learn via experience.
Why are some developers not aware of the functional flows? It’s like I am coding this module, why should I know the complete flow. My module is working fine. But you have to have a complete understanding of the system. Isn’t it? It works like that in every sphere – look at the bigger picture. Where do you fit, or where does your code/module fit in the overall flow. System architecture and System’s User perspective go hand-in-hand. Everyone in a project should have a clear understanding of these two aspects.