4 ms·
Actually, doing that means everyone getting a balanced say. Two way street. If you make it one way, it is all on you, and when that team says that, you get al
by ddingus 8y ago
Actually, doing that means everyone getting a balanced say.
Two way street.
If you make it one way, it is all on you, and when that team says that, you get all the credit. Good or bad, and the team knows it. Will definitely throw you under a bus, given cause.
If you make it a balanced discussion, everyone taking shared ownership, then it is on everyone.
The difference shows up in two places:
One, bad call. The team can come together, own it, and letting the bad call go is not so rough. The follow on discussion is rational and productive.
The other one is getting that different point of view. Having that discussion sets great expectations. Being challenged, getting better, all that is welcome. A team that does this successfully tends to congeal and do extremely well.
Play it how you want to play it, but I definitely prefer to have it all on the table, open, team discussion, frank, high value.
Mix in a reluctance to blame and shame, favor choices outcomes and data and you get a team that can weather the good and bad, everyone helping everyone too.
The lead is responsible for cultivating that culture, empowering people, resolving conflicts, etc. Also owns team business meetings, data, all that.
Just saying.
- wolco 8y agoI've been in both situations and places inbetween. If the team lead owns it they should take the blame and give credit to the team. If the team kind of owns it then everyone is off the hook or on. It also invites the owner/vp to talk directly with the programmers which undermines the lead. No one mentions this but the lead in development is one of the rockier jobs. You rarely have power to hire/fire without a manager, all development problems come your way, credit goes to developers. You have very little power compared to other industries.