| So... I don't know how much other experience you have leading, in the sense that it requires negative feedback to team members, changing existing patterns and such. Assuming this is relatively new to you, my advice is to focus time (2-4 weeks perhaps) on how the team/people operate. Worry less about the task, more any about the team... for that period. Break bad habits and form better ones. Realise that negative feedback is tough, and treat it as your current problem. Like other hard tasks, it can't be done well while other things are getting top priority. There are people who can't really perform at a job. It probably doesn't matter what you do in these cases. More commonly, these are bad patterns. In all honesty, a lot (most?) jobs are about putting the ball in another's court, having a talking point ready for the daily standup and such. Relatively few jobs are about "genuine work." That's not going to change if you work for CitiBank. A peppy team lead won't change that (for long). It's how the process of incentives and culture work at a proverbial Citibank. Last... The truth is a lot of employees really suck. It takes some experience to tell a from b from c... so don't jump to conclusuons. If that's the reality, realise it. Programming is one of the most unprofessional professions, culturally. People pretend to know more than they do. "I can figure it out" counts as "I know." That leaves a lot of unacknowledged lies in the game. It's very possible that members of your team are missing crucial knowledge/understanding and hiding it, like a fox hides an injury. |