Overview

This episode of ハイパー起業ラジオ dissects the critical product decisions that transformed Facebook from a simple college profile site into the social media giant that rewired human connection. Hosts 尾原和啓 (Kazuhiro Obara) and けんすう (Kensuu) argue that Facebook's success was not merely a function of network effects, but of meticulously timed feature launches—specifically the photo tagging function in 2005 and the News Feed in 2006—that exploited users' fear of missing out (FOMO) and gradually shifted the platform from a "come see my page" model to a "here's what your friends are doing now" model. The conversation has the feel of two seasoned internet veterans trading war stories, complete with digressions into failed startups, the perils of mistiming product launches, and the delicate art of knowing when a user base is ready for a radical change.

---

0:06The Core Question: Beyond Network Effects

The episode opens by framing the stakes. Obara and Kensuu had previously discussed how Facebook's early growth relied on network externalities and "atomic networks"—building one university at a time to create preferential attachment. But that alone, Obara insists, was not enough. The real story is the "painstaking accumulation of features" that kept users engaged. The central question becomes: what specific product decisions made users *want* to stay, and why did those decisions work when they did?

Obara introduces a crucial framing device: timing is everything. He argues that two factors determine whether a feature will succeed: the state of communication infrastructure (bandwidth, device capabilities) and the degree to which users have developed the *habit* of sharing information online. These two factors must converge. A feature can be technically brilliant, but if users aren't psychologically ready to use it, it will fail. Kensuu reinforces this with a vivid example: YouTube launched its upload function roughly 15 years before mainstream celebrities began using it en masse. The feature existed; the cultural habit took a decade and a half to catch up.

---

5:17The Photo Tagging Revolution: Activating FOMO

Obara makes a bold claim: the single most important innovation in early Facebook was not the News Feed, but photo tagging, introduced in 2005. This was a feature built with astonishing speed—roughly two weeks to a month of development—but its impact was outsized.

To explain why, Obara introduces the AARRR framework (Acquisition, Activation, Retention, Referral, Revenue), a model for thinking about the stages of user engagement. He argues that while Facebook was already strong on acquisition (thanks to network effects), the critical battleground was Activation—making users feel that they *had* to be on the platform. Photo tagging was the perfect activation tool.

The mechanism was psychological: FOMO (Fear of Missing Out) . When a user saw a photo of their friends at an event, with everyone tagged except themselves, it triggered a visceral anxiety. "Why wasn't I there?" The feature didn't just let people share memories; it created a social pressure to stay connected. Kensuu notes that in the mid-2000s, before smartphones, uploading photos was a heavy, deliberate act. People used digital cameras, transferred files to PCs, and only uploaded images from special events. This made tagged photos even more potent—they captured "ceremonial" moments (Obara uses the Japanese concept of *hare*, or special occasions, versus *ke*, everyday life). The fear of being left out of these significant events was a powerful motivator to remain active on the platform.

---

11:26The "Hare vs. Ke" Design Principle and Timing Disasters

Obara expands on the *hare* (ceremonial) versus *ke* (everyday) design concept. He argues that getting this balance wrong leads to spectacular failure. He cites Clubhouse as a cautionary tale. Clubhouse launched at a perfect macro moment—the COVID-19 pandemic, when everyone was isolated and desperate for conversation. The technology (audio streaming) was ready. But Clubhouse's design leaned too heavily on the *hare* side: it created intense FOMO around exclusive, live conversations with interesting people. This worked brilliantly at first, but it was exhausting. Users felt pressure to constantly be speaking or listening. When people started to burn out and leave, the platform experienced a negative network effect: "Oh, that person I wanted to talk to isn't here? I'll leave too." The platform collapsed under the weight of its own intensity.

Kensuu shares a personal anecdote about a failed startup called Sunny, a photo-sharing app he built that was conceptually similar to BeReal (which launched years later). Sunny was too early. Users weren't yet tired of polished, curated social media, and the core audience for "authentic, intimate sharing with close friends" was too small. He also tried a short-video dance app two years before TikTok took off—and it "slipped like crazy." The lesson is brutal: having the right idea is not enough. You either need to hit the exact moment when technology and user habit converge, or you need the stamina to "small-pivot" and wait for that moment, as TikTok and its predecessor Musical.ly did.

---

18:18The News Feed: From "Come See Me" to "Here's the World"

The conversation finally pivots to the News Feed, which Facebook launched on September 5, 2006. Obara frames this as a fundamental shift in the platform's philosophy: from a "pull" model (users had to visit individual profiles to see updates) to a "push" model (the platform brought updates to the user in a single, scrolling feed).

Before the News Feed, Facebook was a collection of profile pages and "Walls" (a bulletin board on each user's page). To see what a friend was up to, you had to click on their name. The News Feed aggregated all of that activity into one place. This seems obvious today, but at the time, it was a radical and controversial change. It represented a shift from a "guidebook" model to a "transmission" model—from users seeking out information to the platform broadcasting it.

Obara notes that Twitter had launched six months earlier, in March 2006, with a fundamentally different premise: public, broadcast-style status updates ("What are you doing right now?"). While Facebook's team was surely aware of Twitter and may have felt pressure, Obara and Kensuu argue that the two products had different design philosophies. Twitter was built for public broadcasting from the start. Facebook had to *integrate* a broadcast feed into a system built around private, profile-based connections. This made the News Feed a much harder sell internally and externally.

---

21:55The Privacy Backlash and Zuckerberg's Gutsy Call

The News Feed launch triggered a massive user backlash—a full-blown "flame war." Users were horrified that their activity (profile changes, new friends, photo tags) was now visible to everyone without them explicitly choosing to share it. The core complaint was: "It's fine if people come to my page to see this, but I don't want it broadcast to people who weren't even looking."

Obara and Kensuu compare this to the early days of online shopping, when people feared their credit card information would be stolen. The human brain, they argue, defaults to negative imagination when confronted with unfamiliar technology. The privacy concerns were real and intense.

But Mark Zuckerberg made a critical decision: he did not roll back the feature. He believed that the News Feed was essential to realizing Facebook's true value—the ability to continuously see what your friends are doing. Instead of retreating, he doubled down on granular privacy controls. Facebook introduced detailed settings that let users control exactly who could see each type of activity: "friends only," "friends of friends," or "public." The strategy was to start with tight, conservative defaults and then gradually loosen them as users became more comfortable. This was a masterclass in managing a controversial product launch: acknowledge the fear, give users control, but don't abandon the core vision.

---

28:21The Broader Context: A Perfect Storm of Technology

The hosts step back to note that the 2005–2010 period was a whirlwind of technological change. Broadband internet became widespread. Photo and video sharing exploded. The iPhone launched in 2007, ushering in the mobile era. Facebook's features—the News Feed, photo tagging—were remarkably well-suited for mobile, even though they were designed for desktop. This was partly strategic foresight and partly luck. Kensuu points out that Twitter was also a natural fit for mobile, but for years, the company relied on third-party apps to deliver that experience. Facebook, by contrast, built its own mobile experience, which gave it more control.

The hosts caution against a "just-so story" where every success was part of a master plan. Facebook also made major mistakes, particularly in mobile, which they promise to cover in a future episode. The key lesson is that success is often a combination of good design, good timing, and the ability to recognize and correct errors.

---

31:05Teasing the Next Episode: The "Like" Button and Growth Hacking

The episode ends with a tantalizing preview of the next installment. Obara reveals that the "Like" button was not introduced until three years after the News Feed, in 2009. Even more surprising, the name "Like" was not chosen by Facebook's designers—it was the result of a user vote. This leads into a discussion of how Facebook created the conditions for great features to emerge, rather than dictating them from the top. The concepts of Growth Hacking and "1-Rollout" (a deployment philosophy that emphasizes rapid, iterative testing) are introduced as the organizational backbone that allowed Facebook to evolve so quickly. This sets up the next episode as a deep dive into Facebook's internal culture and engineering practices.

---

Conclusion

What stays with the listener is the profound importance of timing and user psychology over raw technical capability. The episode argues that Facebook's genius was not in inventing entirely new concepts, but in knowing *when* to introduce them and *how* to frame them to overcome user resistance. Photo tagging worked because it tapped into a primal fear of exclusion. The News Feed worked because Zuckerberg was willing to weather a firestorm of criticism to push users toward a more connected experience. The episode matters because it provides a framework for thinking about product design that goes beyond features and metrics: it forces you to ask whether your users are *ready* for what you're building, and whether you have the conviction to push through the inevitable backlash.

---

要点

• Facebook's critical early innovation was photo tagging (2005) , which activated users by exploiting FOMO—the fear of being left out of social events.
• The AARRR framework (Acquisition, Activation, Retention, Referral, Revenue) shows that Facebook focused on Activation and Retention over pure user acquisition.
• The News Feed (September 5, 2006) represented a paradigm shift from a "pull" model (users visit profiles) to a "push" model (the platform delivers updates), and it launched despite massive user backlash.
• Mark Zuckerberg's decision to keep the News Feed and add granular privacy controls rather than roll it back was a pivotal strategic choice.
• Timing is everything: a feature can be technically ready, but users must also have the habit and comfort level to adopt it (e.g., YouTube took 15 years for mainstream adoption; Clubhouse failed because its "ceremonial" FOMO was too exhausting).
• Twitter launched six months before Facebook's News Feed, but the two products had fundamentally different design philosophies (public broadcast vs. private network integration).
• The 2005–2010 period was a unique technological window (broadband, photo sharing, iPhone launch) that rewarded features designed for mobile, even if they were built for desktop.
• The "Like" button was introduced three years after the News Feed, and its name was chosen by user vote, not by Facebook's design team.