A caution against over-weighting the loud, unhappy reaction of a vocal minority when rolling out a product change, since the people who complain publicly are rarely representative of the (larger, often silent) future user base the change is designed for. The recommended balance: hold the design decision on behalf of the larger future population, but pair it with authenticity and transparency about why the change is happening, and give the affected minority real time and choice to migrate rather than forcing an abrupt cutover.
This sits opposite Absence of Complaints ≠ Absence of Problems (Survivorship Silencing) (silence isn't safety) — together the two say that neither the presence nor the absence of vocal feedback should be read at face value; what matters is who the feedback sample actually represents. It also complements Overcommunication Tactic for Unpopular Changes, which covers the communication mechanics referenced here (authenticity, transparency, transition time).
Reported by Tamar Yehoshua (Glean/Slack).
The flip side of not over-indexing on vocal complainers is a deliberate sizing principle: the number of people using a product today is usually much smaller than the number who will use it in the future, so redesigns and feature removals should be weighed against the larger future user base rather than the smaller, more vocal set of current users. Slack's Calls-to-Huddles transition was framed this way — the complainers were disproportionately the existing, invested user base, while the product was being designed for a much larger group who hadn't adopted it yet. See Authentic, Transparent Change Communication for Unpopular Product Decisions for how this kind of unpopular change was communicated once the design decision was made.
Из тем: Stakeholder Power and Trust