The Twenty Minute VCSnap's VP of Product Jack Brody: The Future of AR; Snap Glasses; Evan Spiegel's Product Mind | E1006
CHAPTERS
- 0:00 – 2:34
Jack Brody’s path to product design: turning “jack of all trades” into a strength
Jack traces his early academic experience of being broadly capable but not exceptional in one area, and how that insecurity led him to product design. He explains why design’s interdisciplinary nature clicked for him and how a brief detour into mechanical engineering confirmed where he was strongest.
- •Felt “okay at everything” in school and envied peers with a clear specialty
- •Discovered product design as an interdisciplinary craft of synthesis
- •Reframed breadth as a design superpower rather than a weakness
- •Pursued mechanical engineering for technical depth, then realized design was the right fit
- 2:34 – 5:00
How Evan Spiegel recruited him: the one-hour internship
Jack recounts interviewing with Snap when it was still tiny, including a walk-and-talk interview with Evan. He accelerates graduation to join as an intern—only for Evan to convert him to full-time within an hour on day one.
- •Interviewed with Snap in 2013 when it had ~25 people
- •Evan’s conviction and the company’s vision (turning down acquisition) attracted him
- •Accelerated his master’s timeline to graduate before starting
- •Converted from intern to full-time in about an hour—likely Snap’s shortest internship
- 5:00 – 6:19
Evan Spiegel’s product mindset: questioning everything to innovate
Jack describes what makes Evan exceptional at product: an intrinsic drive to do things differently and challenge default assumptions. He frames this as a cultural engine—starting from the top—that keeps Snap from merely copying incumbents.
- •Evan’s differentiator is his desire (not just willingness) to do things differently
- •Relentless questioning of “the way it’s always been done”
- •Underdogs must innovate to avoid perpetual catch-up
- •This mindset becomes an organization-wide innovation culture
- 6:19 – 10:11
How to challenge conventions without breaking what works: rapid de-risking via prototypes
The conversation shifts from “question everything” to how you do it responsibly. Jack outlines how Snap reduces decision cycles by choosing the right prototype fidelity—from quick internal demos to longer-running market tests—so conventions are validated or invalidated quickly.
- •Innovation requires challenging conventions, but not all conventions are worth it
- •De-risk by answering the question quickly through experiments
- •Prototype fidelity spectrum: mocks → internal prototypes → production code + market tests
- •Use experienced intuition informed by many experiments to guide decisions
- 10:11 – 12:50
When users hate change: conviction, internal dogfooding, and longer A/B tests
Harry asks how to tell good change (initially hated) from bad change. Jack explains why users resist habit shifts and how Snap builds confidence by living with changes internally, running longer experiments, and calibrating rollout pain to the team’s conviction.
- •Consumers generally dislike change due to habit disruption and friction
- •Dogfooding helps predict the frustration-to-value curve over time
- •Longer A/B tests (weeks/months) can be necessary for high-risk changes
- •Conviction determines how much short-term pain you’ll accept for long-term direction
- 12:50 – 15:06
Best vs. worst Snap product calls: Stories, Snap Map, and winding down Games
Jack gives concrete examples of initially unpopular features that became successes—especially Stories and Snap Map—plus a major effort that was later wound down. He distinguishes failure from strategic focus: sometimes a product is viable, but the path is too long given constraints.
- •Stories took months to gain adoption but reshaped the industry
- •Snap Map faced privacy concerns; designed with opt-in and close-friend graph assumptions
- •Map inspiration: users posting location “hit me up” snaps then deleting once friends arrived
- •Games platform showed promise but was deprioritized to focus on bigger opportunities
- 15:06 – 19:11
Handling copycats and keeping differentiation: motivation, not resentment
Asked about competitors copying Stories, Jack says Snap has grown comfortable with imitation and even finds it validating. The key is to keep innovating and double down on what remains unique about Snapchat’s usage norms and social graph.
- •Copying validates that Snap hit a real human behavior
- •Imitation increases urgency to keep innovating
- •Snapchat Stories remain more raw/authentic than other platforms’ versions
- •Close-friend graph enables differentiated features others may struggle to replicate
- 19:11 – 22:21
Is product art or science? Product as an adaptation of the scientific method
Jack rejects the binary framing and argues product is closer to science due to its hypothesis/experiment/iteration loop. The “art” enters when creating net-new solutions through human creativity, cultural understanding, and imagination.
- •Product can’t be purely art or purely science
- •Design thinking mirrors the scientific method: problem → hypothesis → prototype → iterate
- •Difference: science aims for understanding; product/design aims for new solutions
- •Creativity supplies the “net new” leap; he frames it as roughly 80/20 science-to-art
- 22:21 – 26:49
Building repeatable innovation: creativity, diversity of thought, and psychological safety
Jack breaks down the ingredients for sustained innovation. He defines creativity as merging distinct ideas and argues that diverse lived experiences increase the odds of novel combinations—if the culture supports speaking up without fear.
- •Creativity = combining distinct ideas into something new
- •Diversity of thought and lived experience increases idea recombination
- •Psychological safety is required to make “talk cheap” and idea-sharing abundant
- •Leaders must reward risk-taking and dissent publicly to reinforce safety
- 26:49 – 29:38
Prioritization and common product mistakes: impact, cost, gut, and problem-first thinking
Jack lays out how to choose among constrained options using a three-bucket framework—impact, cost, and instinct—plus the execution probability Harry adds. He then highlights a frequent failure mode: teams fixate on a solution before deeply defining the problem.
- •Prioritization buckets: opportunity/impact, engineering cost/time, gut feel for strategic fit
- •Execution probability and opportunity cost matter in practice
- •High impact + low cost + strong conviction should ship immediately
- •Biggest mistake: overcommitting to solutions instead of deeply defining the problem
- 29:38 – 33:32
Managing product teams: performance, real-time feedback, and the hard conversations
They discuss when to keep supporting someone versus letting them go. Jack emphasizes intent as the first filter, then frequent candid feedback, clear expectations, and the belief that moving on often helps the person find a better fit.
- •Separate bad intent (act fast) from good intent (coach and give time)
- •Deliver feedback in real time; set a clear bar for “good enough”
- •Candid feedback is easier when the relationship is grounded in good intentions
- •Letting go can ultimately benefit the person by pushing them toward a better fit
- 33:32 – 35:43
Personal operating system: perfection pressure, guilt tradeoffs, and parenting priorities
Harry probes Jack’s self-expectations and how he balances work and family. Jack describes learning to accept “not perfect,” feeling constant tension across roles, and how becoming a parent clarified his focus and reduced restlessness.
- •Doesn’t identify as a perfectionist; success requires accepting imperfection
- •Experiences guilt when not fully present at work or with family
- •Reframes failure as learning and incremental improvement
- •Parenthood clarified priorities: work when working, family when with family
- 35:43 – 41:08
Hiring product teams: define the problem first, then build a disciplined interview loop
Jack treats hiring as a design-thinking problem: understand what the organization truly needs before writing a JD or sourcing candidates. He explains Snap’s typical funnel (screening then loop) and the importance of cross-disciplinary, diverse interview panels for PM roles.
- •Step “-1” in hiring: define the organizational problem and skill gap precisely
- •Sometimes issues can be solved via reorgs/process changes instead of hiring
- •Typical process: short screen to avoid costly full loops, then structured interviews
- •Interview panels should be diverse across disciplines (PM, eng, design) to assess collaboration
- 41:08 – 43:37
Hiring mistakes and success rates: act fast on mis-hires and expect role evolution
Jack argues the biggest hiring mistake is not hiring the wrong person, but failing to address misfit quickly once it’s clear. He notes hiring is imperfect, suggests 50% “right” is realistic, and reframes outcomes as role tweaks rather than total failures.
- •Interviewing isn’t a perfect science; mis-hires happen on both sides
- •Worst mistake: letting a misfit linger and anchor team performance
- •You usually know quickly if someone won’t meet the role’s needs
- •~50% may require role changes/tweaks over time even if people remain valuable
- 43:37 – 47:41
Snap in the developing world: rebuilding Android and “local product, globally”
Jack describes Snap’s strategic push to improve accessibility worldwide, anchored by the 2018 decision to rewrite the Android app from scratch. He explains the goal of making Snapchat feel like it was made for you anywhere, while acknowledging true UI universality is impossible.
- •2018 Android rewrite addressed tech debt and poor performance outside iPhone-heavy early markets
- •Improved accessibility drove accelerated global adoption
- •Strategy: build a ‘local product globally’ so users feel the app fits their context
- •Can’t optimize one UI for all cultures; localize cheaper layers (language, teaching) while keeping core value universal
- 47:41 – 51:22
Geography, competition, and Stories’ origin story (including the Kakao question)
Jack identifies Japan as a market with strong potential despite entrenched competitors like Line. He denies copying KakaoStories and explains Stories’ origin: users wanted ‘send to everyone,’ but Snap solved the underlying need without diluting the intimacy of one-to-one snapping.
- •Japan seen as a strong fit for Snap’s visual, playful, AR-driven communication
- •Market is saturated by Line, but Snap differentiates via visual conversation format
- •Stories emerged from a user need to broadcast without diluting personal Snaps
- •Design lesson: focus on implicit needs (problem) vs. explicit requested solutions (faster horses)
- 51:22 – 56:08
The future of AR and Snap Spectacles: from playful lenses to utility and glasses form factor
Jack frames Snap’s core innovation as redefining the camera from a capture tool into a communication interface, which naturally led to AR. He predicts AR’s future is increased utility through environment understanding, with glasses as the long-term ideal form factor; Spectacles are iterative steps toward that vision.
- •Snap turned the camera into a communications medium used many times per day
- •AR began as playful expression lenses, evolving toward utilitarian capabilities
- •Future AR: more utility driven by understanding the environment around you
- •Glasses can move tech into the background; Spectacles’ early versions weren’t ‘iPhone moments’ but informed the roadmap
- 56:08 – 1:02:16
Quick-fire: startup mentality, vulnerability, impostor syndrome, and product heroes
In rapid questions, Jack shares concise beliefs: keep a startup mentality at any scale, define problems early, avoid over-specialization in early product hires, and get vulnerable fast in new roles. He also names Spiegel and Jobs as product exemplars and highlights OpenAI’s unconventional ‘tech-first’ strategy as a special case for AI.
- •Angel investing reinforces maintaining a startup mentality
- •Career advice: define the problem well; let solutions follow
- •Leadership advice: get vulnerable fast; share insecurities to create learning space
- •Impostor syndrome is persistent; great teams let you lean on others’ strengths
- •Respects OpenAI’s strategy: AI can justify tech-first investment due to broad applicability
