|
|
|
|
|
by qq66
3637 days ago
|
|
Product decisions can never be solely by consensus. At some point, barring massive groupthink, there will be a disagreement on some product decision (what color should this icon be?) but the icon will ultimately be assigned a color. There is some process by which that decision is made. |
|
i.e. when it comes down to the icon, your group should agree to trust the designer, and then trust the designer. The benefits are numerous: 1) People get to make the decisions within their realm of expertise, 2) No aimless debate, products are built faster, 3) If there was a bad decision, there is one person who made the decision, but the whole team should share accountability since they all agreed to trust the person who made that decision.
The process by which that decision is made is the process by which you select a person to make that decision. Ideally, that happens at the hiring level, so once, for example, a designer is assigned to your team, you already know that s/he is good enough to pick the right color. You don't have to engage in office politics to discover whether or not you can trust him/her, and you don't have to engage in office politics to allocate praise/blame in the event of particularly good/bad decisions.