4 ms·
This is a lesson I learned the hard way. When I was a first time manager I had the naive idea that I was going to build consensus for everything and get everyon
by Aurornis 1y ago
This is a lesson I learned the hard way. When I was a first time manager I had the naive idea that I was going to build consensus for everything and get everyone to come to an agreement naturally.
It worked at first with a good team. Then later I inherited a fragment of another team with some older know-it-all engineers who thought everything modern was garbage and we should be doing everything like they did 25 years ago. I wasted too much time letting them stonewall everything while thinking we’d eventually reach a consensus.
Then at some point you realize you have to put your foot down and pick a direction after they’ve had a chance to state their position.
- wahnfrieden 1y agoYou could learn from consent based decision making, a hallmark of sociocratic worker coops that is underrated and can be applied elsewhere. Hierarchy and coercion isn't necessary for avoiding decision paralysis in organizations. It appears to be the practical route but has all sorts of harmful and counterproductive consequences. https://www.sociocracyforall.org/consent-decision-making/ https://www.sociocracyforall.org/consent-decision-making/
- AnimalMuppet 1y agoInteresting. For that to work, though, it has to be true consent, not "it's the boss's idea and I don't dare to object out loud". But I guess, if that's the environment you're in, then you're stuck with autocratic leadership (no matter what label it claims for itself), and your only choice is to leave or not.
- wahnfrieden 1y agoYou can also try to organize your peers in those environments (or even from the outside if so inclined)
- cowthulhu 1y agoI don’t think that is a practical framework for situations where people aren’t already very closely aligned. What happens when a few people are very vocal (and firm) in opposition to basically every change? Having dissenting views is valuable, but not when they have veto power. Additionally, I think that framework is vulnerable to what I refer to as “death by yes but” - when everyone is just piling on amendments and precursor conditions, oftentimes conflicting, that result in a decision taking months (maybe even years) to make or scuttle. I’m basing these comments out of experience - one example is a workgroup/committee operating under a similar model that was completely unable to do anything due to decision paralysis. The committee grew significantly more effective when we reformed the decision making process to have a small group of owners to handle pitching and (potentially) implementing the decision, then had approval be a simple yes/no majority vote.
- wahnfrieden 1y agoYes it only works when participants have a shared aim In full sociocracy, it... > honors the circle’s ability to freely make decisions within its domain. This is key for the organization to remain effective. But it comes at the cost of members not having “consent rights” to every decision the organization makes. Each member will only have those rights for the circles they are a part of. So it's not necessary to allow people outside that working group to veto or require compulsory followup through objection There's no perfect solution to organization, everything is a tradeoff. I've also been part of working groups (made of people whose job description is to manage the scope of changes they're proposing) where everyone and the workers impacted by the decisions are in agreement and no impact on cost etc., but the exec decides no change can be made due to personal preference despite disastrous consequence. Or where an exec who abstains from checking in on a working group's efforts nonetheless counters it with shifting and contradictory demands whenever it comes time to take action, requiring going back to the drawing board repeatedly until people simply give up or leave the organization. Or where the exec asks for more data for a proposal, and then doesn't evaluate the data once gathered, leaving no recourse but to give up or leave the organization. We all have stories like this. Hierarchical organizations are also susceptible to paralysis.
- AdieuToLogic 1y ago
- homeonthemtn 1y agoIt's not autocratic, it's not a form of government at all. Each role is a module to take in inputs, process them, and produce outputs. it is effectively a program. Define your roles, and expectations of each role, then run the program and edit as needed.
- DrewADesign 1y agoRight, and some people’s role is to organize people and orient the group’s efforts by taking in big-picture problems and outputting direction. There’s rarely a single correct answer— lots of good solutions have trade-offs— but there are often various wrong answers. Do the best you can to avoid the wrong answers, and when you inevitably run into the business end of one of your trade-offs, take comfort in knowing the other good options probably also had trade-offs, and tell the smug know-it-alls to cram it. People working effectively towards a non-optimal solution is far more useful than sitting around arguing about the best way to do it.
- gmfawcett 1y agoI've often taken inspiration from RFC 2418, "IETF Working Group Guidelines and Procedures" [1], a rare RFC that defines a human protocol ("rough consensus") rather than a technical one. [1] https://www.rfc-editor.org/rfc/rfc2418.html https://www.rfc-editor.org/rfc/rfc2418.html
- tracerbulletx 1y agoYou can build consensus around the decision making process and build a culture where the outcome of that process is widely accepted. As long as people have the time and pathways to make their case and input, and understand there will be some verdict that may or may not align completely with their opinion. Then its just the decision makers duty to synthesize things in good faith but probably has bought themselves some leeway.
- brandall10 1y agoOne thing I like to do with sr+ engineers who will feel burned by a decision - esp. those very publicly against it - is to lead with some sort of concession... maybe a project they expressed interest in, greenlight for a week to research some POC. Whatever it is, it tends to be considerably less value to the business than the decision itself, but it directly acknowledges their discontent and allows them to get something out of the process besides platitudes, (perceived) public embarrassment, and frustration.
- YZF 1y agoWhat are the odds that the older know-it-all engineer actually knows better than you? I would say they're pretty good. That's not to say that consensus always works. But it does mean the group needs to understand the objections and make decisions the team can live with. The most toxic of engineering situations is the manager making decisions without understanding consequences and without taking responsibility for the outcomes. Sometimes there is time pressure or difficult people but the base assumption should be that people actually want to make the right decision, being difficult generally makes your life harder. Who would be responsible for executing on the decision and who would be responsible for the outcome? What are the consequences of strong arming the team into solutions they don't agree with?
- atoav 1y agoChances based on my experience? 50:50 Old engineers will say things that are hard learned lessons like "don't reinvent the wheel, when your thing is running on a system that comes with wheels". So, good solid advice that rookies will ignore, because of course they do. But sometimes old engineers will say things that are more of the quality of: "30 years ago went deep into this topic, discovered the truth and haven't updated my judgement since, despite the world having changed a lot". The problem is that unless you really know things inside out or know the hard held opinions of your older collegue well, it can be hard to tell the two apart. In that case it only helps to talk about it in more detail and try to get to the root of where the judgement comes from. Then it could come to light that the warning to use PHP comes from a bad experience with PHP version <1.0 or that there is a number of bad experienced that are really useful for deciding the direction of a project. In the end many decisions are about taste. And nothing is as good as a way to keep arguing than matters of taste. Weigh all the pros/cons and make a choice.
- bruce511 1y agoI'll second this. Unfortunately experience is a two-edged sword. I deal with a lot of old programmers and I continually hit the "fact" that was true in 1999 but is false today. For example, I started in DOS (as did many older folk). Memory was severely constrained. So we developed habits to use memory (and disk space) very efficiently. Like using bits in a byte, or a byte as an ID field. Or quibbling over the length of a Name field. All those habits proved to be bad in the long run. And today memory (and disk space) are abundant. But these old habits are hard to break. And that's before we talk about "modern" techniques, like version control etc. Experience is great. I'm a fan. But all too often experience is also "there was a bug I windows 95, so that API call is unreliable ".
- smrtinsert 1y agoThe know it all engs were probably right though and you just added the self imposed productivity, performance, and TCO tax that everyone else adds by default