Growth can require a difficult redesign of the core experience
Looking ahead to Twitter’s second-quarter results in 2014, this note considered a growth challenge it shared with Foursquare. Each service had been shaped by highly engaged users whose habits did not necessarily resemble those of the much larger audience the companies hoped to reach.
That gap can force a product transition. A service built around specialist behaviors may need to become easier to understand on first use, more immediately useful, and less dependent on learning a vocabulary of features. Yet the people most invested in the original product can experience those changes as a loss.
Foursquare’s split showed the trade-off clearly
Foursquare separated recommendations from check-ins, placing the latter activity in a distinct app. The broad strategic aim was understandable: recommendations could appeal to people who had no interest in routinely broadcasting where they were, while committed check-in users retained a dedicated tool.
But the transition made familiar tasks feel more fragmented for some of the service’s most active users. The competitive and social routines that had defined their experience became harder to access. The lesson was not that a niche product should never evolve; it was that implementation matters as much as the strategic direction.
- Dividing one established activity across multiple apps can add friction.
- Removing social or competitive features can weaken the habits of the most active audience.
- A move toward a broader use case needs a clear reason for existing users to remain engaged.
At the time, public information about Foursquare’s scale and revenue was limited. That made the strategic issue more important, not less: a recommendation-led product could broaden the potential audience, while the data generated through use remained a meaningful part of the service’s longer-term value.
Twitter faced a related problem
Twitter’s experienced users were accustomed to lists, tags, direct messages, account mentions, dashboard tools, and large follow lists. For a new user, the same set of conventions could make the product appear difficult before it delivered a useful result.
The path to wider adoption therefore involved making the first session more legible: helping people find relevant material quickly and reducing the amount of setup required to build a useful feed. Product discussions at the time included more algorithmic approaches to feed presentation and ways to make specialized notation less central to the visible experience.
That approach carried a particular risk. Twitter depended on highly engaged contributors to create much of the material that attracted less active readers. A redesign that made the service friendlier to newcomers still needed to preserve the tools and incentives that supported its most committed participants.
The broader archive lesson
Companies can scale a focused product into a broader service, but the change is often consequential. The original experience may have been ideal for a small but highly motivated group; the next stage may demand a product that is simpler, more guided, and less specialized.
The hard work is to operate both models at once: protect the value created by established users while creating a credible path for people who do not share their habits. That is a product decision, a retention decision, and ultimately a business-model decision.