Twitter's Spectacularly Awful 24 Hours
Twitter just went through an awful 24-hour stretch. It included taking away a feature some people loved, probably being misleading about it, getting a huge amount of backlash, halfway bringing the feature back, and getting railed by the press for it all …
Context & Ripple Effects
Twitter spent May 13–14, 2009 living through a textbook product-reversal cycle: it removed a feature some users loved, drew heavy user backlash and pointed press criticism, then walked half the decision back inside a day. TechCrunch's report also flags — as an unconfirmed charge — that the company may have been less than straightforward about why the feature disappeared.
What makes the episode more than a routine complaint thread is the speed and breadth of the response: Twitter published its own 'We Learned A Lot' note on the company blog the same day, effectively conceding the rollout was mishandled. For a service whose users conduct their arguments in public and in real time, the backlash loop ran at a speed traditional software companies never had to plan for.
First-order effects
- Users who depended on the removed feature get a partial restoration within 24 hours, while Twitter's own team is pulled into same-day damage control on its blog.
Second-order effects
- Press coverage turns a quiet settings change into a credibility test for the young company, raising the cost of every future unannounced or poorly explained product change.
Third-order effects
- If the pattern holds, feature changes on real-time consumer platforms stop being private engineering decisions and become public accountability events, forcing companies like Twitter to build communication and rollback practices around community reaction rather than release schedules.
The trend: Real-time social platforms are learning that user-facing feature changes are judged within hours by their own networks, making rapid reversal and public explanation part of shipping.