10 ms·
First, massive disaffection with typical management is what leads to schemes like this. Especially when it comes to non-technical management, they are not equip
by watwut 7y ago
First, massive disaffection with typical management is what leads to schemes like this. Especially when it comes to non-technical management, they are not equipped to do any of what you wrote. Not that technical management would be great or something. I am not fan of "everyone is leader" organization, but I am aware that contemporary management is not capable of all that much.
> Team members don't need to be "heard," or need sympathy from managers
I do actually want my opinions, ideas and preferences to be heard. If I think that I am not being heard, I prefer to change the team so that I am heard. If I don't change team and I am not heard, I work in more checked-out mode - which is pretty normal. It is doing somebodies domain, I cant take full responsibility if all decisions are somebody elses. thinking more about them just frustrates, so it is natural adaptation to avoid doing that.
> Taking direction or orders from a manager is only ever stressful if that manager doesn't take accountability for their decisions and directions.
Not true. For me, I am actually more stressed when I cant make own decisions, cant influence what affects me or dont have autonomy. Even when management takes responsibility for decisions and directions, purely top down management or micromanagement is stresor and demotivator.
> they need confidence that their leadership understands the environment they work in, takes responsibility for decisions, and gives them direction based shared competence
Leadership that does not hear people who work on the projects, can not understand the environment those people work in. Nor I see space for "shared competence".
- klenwell 7y ago> I do actually want my opinions, ideas and preferences to be heard. If I think that I am not being heard, I prefer to change the team so that I am heard. I think this is a valid expectation. At the same time, it can lead to conflict and confusion if not itself managed effectively. One thing we've done with our team that I think has addressed this pretty well is RFCs (Request for Comments). This is mainly for team practice stuff but also can address important technical questions. We use a Trello board where anyone on the team can add a card and then team members can comment on cards. Team leads then review the board in a 30-min meeting every couple weeks to make sure cards get acted on or otherwise resolved to everyone's satisfaction. Each RFC card is also assigned an owner from the team, a practical example I suppose of everyone being a leader.
- watwut 7y agoThe scheme described in the article does much more. It gives you not just ability to express yourself on card, but also ability to make decisions in limited area and have responsibility for them. I don't think being assigned task or issue is same as "being leader". In article it is more about subprojects themselves having responsible people - and people having responsibility for subprojects. So there is not one team leader responsible for everything, but various people responsible for their smaller parts and changing teams. It is not about everyone agreeing with everything and having all they want. It is much more about autonomy and accountability - which are the core motivators in normal people management theory and there is not reason to think IT people are so different that they don't need them.