Showing a fixed product beats promising one, mostly
During a backlash, a working fix says more than any statement. In the same week, Facebook found that silence while building it reads as indifference.
I’d like to show an improved product rather than just talk about things we might do.
In the spring of 2010 Facebook faced the worst criticism in its history. At its developer conference in April it had announced features that shared more user information with outside websites, on top of privacy changes made the previous December that had already confused many users. Newspapers ran charts of the site’s growing maze of privacy settings, some users organized a day to quit, and regulators in Europe and the United States began asking questions. Mark Zuckerberg’s line comes from a message he wrote in the middle of that storm, around May 23, when he said the company would soon be ready to talk about what it had built.
The instinct is a sound one for product people. Promises are cheap and everyone knows it. A statement about future improvements invites skepticism; a working change can be judged directly. Engineers often distrust announcements for this reason: a plan in words commits the company to something that may change in the building.
On May 26 Facebook released simpler privacy controls, and the backlash eased over the following weeks. The fix did more than any statement could have.
But Facebook did talk, too. On May 24 Zuckerberg published an opinion piece in The Washington Post admitting the company had made mistakes and promising simpler controls. That was the right call. In a crisis of trust, silence while the fix is built looks like indifference, and people need to hear that the problem is understood before they will look at the solution. The line, taken alone, undervalues that step.
Inside a company, the preference for showing over telling is easier to defend. A prototype settles arguments that memos cannot, which is why many software firms hold hack days where engineers build rough versions of ideas instead of proposing them.
The practical reading is to talk briefly and specifically about the problem, and then let the product carry the argument about the solution.