|
|
|
|
|
by antonvs
1923 days ago
|
|
> "Build Consensus" - hah, the words of an org chart climber. Not necessarily. You want to convince your team or other teams to adopt a new tool or practice? You need to build consensus. It's a good skill to have if you want to be able to shape your workplace to your liking. It doesn't necessarily have to involve org chart climbing at all. |
|
"let's have an endless, design by committee approach where the backend dev with no knowledge on UI decides how the UI should look rather than letting the UI designer create a few samples and iterate and everyone else giving feedback like a user would"
or
"we already decided this is going to happen, but for the sake of formality we want you to agree with it so we can feel good about ourselves bullshitting one another into believing everyone has a say, so give us the ok or we'll pester you until you do"
It also stimulates the idea that disagreements are inherently wrong and nothing should happen while a disagreement is in place. Sometimes, it's ok to disagree with someone else and see what happens. Some might call this a form of consensus, though I've had managers get uncomfortable when I didn't vehemently agree with the plan, but was willing to keep my nose out of it and focus on my own things so others could take the risk.