Topics Pioneers Insight Method Author
Back

Will Wu: Top Five Product Lessons from Creating Snapchat "Discover" and "Chat" | E1111

·20VC

Rendering the long image…

Topics Mindset and Psychology of Tech Founders Consumer UI Design and Innovation Management Commercial Shifts in Mobile Recommendation Algorithms
Pioneers Parag Agrawal

Summary

  • The transcript is internally inconsistent on identity: Harry addresses the guest as “Will,” while several later passages are explicitly labeled “Parag Agrawal”; no surname or job title is supplied for Will. The summary below preserves those speaker labels rather than asserting “Will Wu,” Match CTO, or former Snap VP.
  • Speaker 1’s path into product began with IRC and engineering. He spent his early teens learning cybersecurity, cryptography, networking, and video encoding from strangers online, then joined Snap in late 2013 after Evan saw him as more than an engineer. He says LinkedIn records nine years and two months at Snap.
  • Placement can decide a product’s fate more than a year of design work. Discover launched at the far right of Snapchat and was hard for users to find until a one-screen-left move beside friends’ Stories “completely changed the fate of Discover.”
  • Parag Agrawal’s product thesis is that product is “equal parts art and science.” His ASL team at Match Group reflects that belief. Zero-to-one work often requires instinct and a leap of faith; data can guide later iteration, but human-centered design can be lost when teams lean on data too heavily.
  • Parag recommends separate teams for revenue generation and innovation. Innovation may require sacrificing revenue temporarily, so the product leader must create communication pathways, shared information, and personal trust between the teams.
  • On AI, Parag says new tools can accelerate design but rejects the claim that AI makes UI irrelevant. Speaker 1 says generative-AI hype is warranted but worries about companies built only on prompt engineering over models everyone can access.
  • For the Match business discussed by Speaker 1, success can mean never seeing a user again because they found a lasting relationship. The broader competition is for limited attention against games, TikTok, and other mobile experiences. Speaker 1 highlights Tinder’s AI photo-selection feature as a potential way to remove a weeks-long onboarding friction.
  • Hiring advice is split across the labeled speakers: Parag emphasizes examining what candidates have built and avoiding paid mercenaries; Speaker 1’s quickfire answer identifies slow removal of poor culture fits as the biggest founder mistake. A Snap Games acquisition example involved Crash Club, an Australian studio, and a flight to Brisbane the next day.

Deep dive

1. The “Will” passages: from IRC to Snap product work

  • The transcript addresses Speaker 1 as Will, but supplies no surname or job title. Speaker 1 says LinkedIn records nine years and two months at Snap and describes work on Discover and Snap Games; the transcript does not mention Chat in this account.
  • Speaker 1’s formation: from age 12 he lived on IRC every night, learning cybersecurity, cryptography, networking, and video encoding from strangers he imagined were “middle-aged computer scientists who had literally invented computers, the internet, and everything else.” At 13 he bought a used satellite dish on Craigslist, drilled it into his parents’ roof, and tried to decrypt a TV signal. “Technology was my playground growing up.”
  • In late 2013, a mentor introduced him to Evan, Snap’s co-founder and CEO at the time. Over lunch, Speaker 1 described camping “26 straight hours” outside a Cingular Wireless store for the original iPhone. A product-designer offer arrived later that day, despite his having “literally no idea what a product designer was.” He credits Evan with helping him see himself in a new light.

2. Discover and Snap Games: placement decides fate, imposter syndrome is fuel

  • Discover took more than a year of painstaking design and launched at the far-right side of Snapchat, where it was difficult for users to find. Moving it one screen left, onto the screen with friends’ Stories, “completely changed the fate of Discover.” The lesson is to understand current traffic patterns and place new functionality in the parts of the interface users already use.
  • Speaker 1 describes Snap Games as one of his most stressful periods: Snap’s first keynote, thousands of attendees, his first time speaking to reporters, an unproven technology, and five game developers across continents and time zones. He says he was not eating or sleeping well.
  • The experience built confidence and changed his view of imposter syndrome. He now intentionally enters uncomfortable situations that trigger it because they push him to learn and grow. His quickfire advice is to get reps building products—even personal projects—and embrace imposter syndrome.

3. Parag Agrawal: product is equal parts art and science

  • Parag says he is building a new Match Group team called ASL; one meaning is Art and Science Lab. The name reflects his view that innovative products emerge when artistic and scientific or technological disciplines work together to solve human problems.
  • His sequencing rule: taking a product from zero to one requires instinct because “no amount of data or market research” can say exactly whether it will work; iteration beyond that can use data to inform instinct. Human-centered design can be lost when teams lean on data too heavily and fail to consider how a change affects users and the problems they are trying to solve.
  • Parag defines human-centered design as keeping end users at the forefront from need-finding and empathy through prototyping, feedback, iteration, and launch. He cites the Apple Watch’s fall detection and Double Tap as examples of technology addressing concrete human problems.
  • His first negative example is Concur, though he repeatedly caveats that it is a phenomenal and successful enterprise product. Harry, not Parag, calls it terrible. Parag’s narrower point is that enterprise products serve a different buyer and may not be designed from the ground up around the end user.
  • His method is scrappy: identify target users, build empathy, and talk to people directly. For dating products, that means understanding the difficulty of choosing an app and the awkwardness of representing yourself with photos and text to potentially millions of strangers in a romantic setting.

4. Start simple, earn complexity, and launch something you are proud of

  • Simple is not always better. For a novel product, however, “simplicity is paramount” to making it easy to use and easy to grow. Parag uses the original iPhone’s skeuomorphic iconography as an example of grounding new interactions in familiar physical analogies.
  • If a simple core product finds product-market fit, teams can layer in complexity over time and expand the design language to solve new problems. Feature-creep prevention requires the right level of abstraction: a product should not expose users to hundreds of toggles while still offering depth to power users.
  • Parag favors rapid iteration through hundreds or thousands of mockups, plus real software prototypes rather than only clickable Figma files. User studies and informal testing help determine whether an experience is approachable.
  • On speed versus polish, he says perfection takes forever and can lead to years of building the wrong thing. But a launch should still be something the team is proud of because first impressions matter. Rapid prototyping is complementary: it accelerates the path toward a credible, vision-consistent product.

5. Brainstorm mechanics: couches, half-jokes, and a five-person cap

  • For creative and design brainstorming, Parag prefers being in person, in a relaxed setting such as a couch, with enough psychological safety for people to offer unconventional ideas. Half-jokes can contain an important edge and become strong product features.
  • He caps the group at roughly five people. Larger groups create “too many cooks in the kitchen” and too many people able to shoot down ideas, which he considers especially harmful to creativity. Participants should be trusted and bring different perspectives, such as design, engineering, fine art, fashion, or architecture.
  • He sees agendas as a tension: structure keeps a group on task, but too much structure can stifle creativity. His ways of generating useful disorder are to bring together genuinely diverse perspectives and to travel, observe target customers in person, and understand their environments.

6. Revenue versus innovation, and how the labeled speakers assess hires

  • Parag recommends separate teams for revenue generation and innovation. A new feature may temporarily deteriorate revenue while the company tests an idea; placing both incentives in one team can create a conflict that paralyzes development. The teams still need shared notes, communication processes, and personal trust.
  • Parag evaluates product candidates primarily through products they have built or imagined: “someone’s actual work” reveals more than a few interviews. He does not personally rely on case studies or brain teasers, comparing them to standardized tests that measure only one kind of thinking.
  • In the Snap Games acquisition story, Parag says Snap lacked game-development expertise, so he searched globally for a studio. Crash Club appealed because it was real-time multiplayer, colorful, energetic, and used a novel spinning 3D-box menu; it came from the creators of Fruit Ninja. After one introductory call to assess culture fit, he flew to Brisbane the next day to pitch an acquisition.
  • Parag looks for growth-minded people who are open to change, learning, and intellectual curiosity. He asks about long-term ambitions and says he does not want a “paid mercenary” who is only there for money; he believes profound products come from deep passion. He also acknowledges giving people a long leash because he tries to see the best in them.

7. AI adds tools, but the UI-is-dead thesis is wrong

  • Parag says designers on his team already use Midjourney and DALL-E for UI and visual concepts. He is also experimenting with large multimodal models that can work with language and images.
  • He expects a near-term tool that provides instantaneous user feedback: a founder could hand a prototype to an AI and ask for reactions as if it were an 18-year-old man in Los Angeles or a 55-year-old woman in New York. He says understanding AI’s capabilities and limitations will be important to product design.
  • Parag rejects the claim that AI will make UI irrelevant. ChatGPT introduces a new conversational interaction paradigm, but command-line interfaces and graphical user interfaces persisted after newer interfaces appeared. He expects screen-based interfaces and language interaction to coexist.
  • In the later Speaker 1 passage, the speaker says generative-AI hype is warranted but questions the defensibility of companies doing only prompt engineering on top of the same accessible model. The bullish case is that models trained on much of the world’s information can broaden access to intelligence as inference costs fall.

8. Match’s paradox: success means never seeing the user again

  • Speaker 1 calls it a major success if the company never sees a user again because that person found a relationship they are happy with for life. That creates an unusual business challenge: continually reaching people coming of dating age.
  • Speaker 1 frames competition less as a battle among dating apps and more as a fight for limited attention against casual games, TikTok, and other mobile experiences. He describes partnering with other apps and brands, including companies within the Match Group portfolio.
  • His most-impressive recent example is Tinder’s AI feature for quickly surfacing the best photos from a user’s camera roll in a privacy-safe way. Speaker 1’s original idea was to train a model on high-performing Tinder photos; the transcript presents that as a proposed model, not a confirmed description of how the feature was trained. Choosing profile photos once took him weeks, so he sees the feature as a potential friction remover.
  • His quickfire rule is to listen to users unless a request conflicts with a core product value. Even then, he says not to ignore the request: understand the underlying problem and solve it in a way consistent with the product’s values.
  • The setup details are deliberately nerdy: an Apple Pro Display XDR, an Insta360 Link webcam, and a Leopold FC660C with Japanese Topre switches in a custom housing by Ryan Norbauer. Speaker 1 says he could do an entire podcast about the setup.