In business mythology, the word “pivot” sounds very dramatic—an all‑or‑nothing leap from one idea to another when the original plan doesn’t succeed. But the most interesting pivots aren’t impulsive; they’re disciplined decisions to walk away from a particular line of business in order to protect a more robust one. The companies that eventually define a category are often the ones that can accept, sometimes reluctantly, that their first idea was the wrong vehicle for the right goal.
Consider a few names that now feel as ubiquitous as Kleenex: Netflix as streaming, Instagram as social photography, Slack as workplace messaging, Airbnb as peer‑to‑peer lodging. None of them started out where they ended up. Each began in a different business—DVD rental, a crowded multi‑feature app, an online game, temporary beds for conference overflow—and then made a conscious choice to abandon that original line of work in favor of the opportunity customers were actually pulling toward. The pivot was a change of route.
This article looks at those moments of walking away as an art, not just a survival tactic. We’ll trace how several well‑known companies recognized when a single feature had become the real product, when a new medium could serve the same value better, or when a side experiment deserved to become the core business. More importantly, we’ll distill the patterns behind those choices—how teams treated sunk costs, what signals they paid attention to, and what questions they were asking before committing—so that leaders facing their own “should we let this go?” decisions can do so with more clarity.
One of the clearest patterns in successful pivots is the moment when a single feature outgrows the product it lives inside. The original idea may be broad—a multi‑purpose app, a rich game world, a full stack of tools—but users gravitate toward one capability in particular and largely ignore the rest. Companies that go on to thrive treat that behavior as a signal rather than a nuisance: the feature that keeps pulling attention becomes the business.
Instagram is a textbook example. Before it was a global photo‑sharing platform, it was Burbn, a crowded application that combined check‑ins, points, and photos into a single experience. In theory, Burbn allowed people to document where they were, earn rewards, and share pictures. In practice, data showed that most users did one thing: they took and posted photos. The creator eventually described Burbn as a “false start” and made a stark choice—strip away almost everything, keep the photo‑sharing core, simplify the interface, and relaunch as a much more focused product. What could have looked like an admission of failure at the app level was, in reality, a recognition that the real opportunity was narrower and more powerful than the initial concept.
Slack’s story follows a similar arc but from a different starting point. The company behind Slack began life as a game studio, investing years in building an online game that never found a large enough audience to be commercially viable. During development, the team built an internal messaging tool to coordinate work—channels, search, a way to keep conversations organized. When the game stalled, they noticed something important: other teams were more excited about the tool than the game. The “side feature” designed just to help the studio operate was solving a much more widespread collaboration problem. Rather than insist that the game remain center stage because of the sunk effort, leadership pivoted completely. The internal tool became the product; the struggling game became the sunk cost they were willing to accept.
Flickr offers still another version of this same dynamic. It started as part of an online game where players could upload and share images inside the game environment. The game itself never caught on, but the image‑sharing mechanism did. Users wanted a way to store, tag, and share photos more than they wanted to explore the game’s world. Recognizing that, the founders separated the photo feature from its original context and built a dedicated photo‑sharing site. Once again, the pivot was less about inventing something new than about acknowledging what users had already decided the product was for.
Across these cases, teams watched actual user behavior instead of clinging to their original narratives. They treated features that attracted disproportionate engagement as the truest expression of demand, even when those features were not the ones they had planned to build a business around. And they were willing to walk away from substantial creative and technical investment—the game worlds, the extra app functionality, the original brand stories—once it was clear that the path to a durable company ran through a narrower, more focused capability. For operators, the practical question is simple: if one part of our offering is doing most of the real work with customers, are we prepared to let it become the company, even if that means admitting the rest was a “false start”?
Next week we’re looking at some examples of companies that should have pivoted–but didn’t.
