Lenny's PodcastVision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product, Figma)
CHAPTERS
- 0:00 – 7:32
Why Mihika stands out: background, strengths, and “lean into your spikes”
Lenny sets up the episode by sharing how often Mihika was named the best PM people have worked with. Mihika explains her non-checklist PM style, how her CS + visual arts background shaped it, and why leaning into strengths (while still growing) matters.
- •Lenny’s outreach reveals Mihika’s reputation for vision and influence
- •Mihika’s “scope is the world” mindset and high-agency orientation
- •How CS + visual arts led her to product as a bridge between disciplines
- •Why PMs should lean into unique spikes while maintaining a growth mindset
- 7:32 – 12:24
Crafting product vision: anchor the chaos with a future-state narrative
Mihika breaks down why vision is essential for surviving the messy product-development cycle. She explains how strong visions emerge from tight user + team proximity, and how cross-functional “cross-pollination” produces better, more feasible bets.
- •Vision keeps teams oriented through pivots, highs/lows, and ambiguity
- •Start with: “If we do our job right, what does the world look like?”
- •Vision can’t be created in a vacuum—stay inseparable from users and team
- •Cross-pollination across research, design, product, and engineering drives innovation
- •Balance aspiration with feasibility even during the vision phase
- 12:24 – 17:06
The FigJam vision story: making meetings more democratic (and more fun)
Using FigJam’s pandemic-era rise, Mihika shares a concrete example of vision formation: expand the democratizing magic of brainstorming to all meetings. This vision then maps to specific features (music, voting) and template-driven rituals that make participation easier.
- •Remote work exposed the need for shared, collaborative spaces
- •Brainstorming worked best because it democratizes participation
- •Vision leap: make the “generative brainstorm” the norm for other meeting types
- •Bridge internal “FigJam on steroids” usage to external customer behavior gaps
- •Feature and template bets that support flow and inclusive contribution (music, voting, rituals)
- 17:06 – 18:25
How Figma sells the future internally: one artifact, prototypes, and proof points
Mihika explains how to communicate vision in a detail-oriented, visual culture: make it tangible early with prototypes and a single shared artifact. She also outlines a persuasive pitch structure that alternates pain points, solutions, and proof points.
- •Create one combined deliverable the whole team owns (not siloed readouts)
- •Figma leans into “see to believe”: prototypes before formal green lights
- •Pitch rhythm: pain point → solution → proof point (repeat)
- •User testimonials layered on prototypes can beat words-only narratives
- 18:25 – 21:26
Delivering a vision without design/engineering: AI, asking for help, and hackathon teaming
For PMs without strong design/engineering skills, Mihika offers two levers: the rising accessibility of building via AI tools, and the straightforward tactic of recruiting collaborators. She shares how Maker Week becomes a vehicle to form teams and turn a pitch into something real.
- •AI is lowering the floor to prototyping and building (agents, tools like Replit)
- •Treat tools as “co-founders” (technical or design) to bring ideas into existence
- •Don’t let your skill gaps block you—go ask people directly for help
- •Hackathons aren’t just for engineers: anyone can pitch and form a team
- •Momentum often starts with walking around and getting one “yes”
- 21:26 – 26:36
Building conviction fast: momentum, intuition from user conversations, and “strong opinions weakly held”
Mihika describes conviction as a tool for creating forward progress, especially because most software decisions are reversible (two-way doors). She explains how constant user conversations build a durable intuition, and why sharing an early hypothesis beats starting from nothing—while staying ready to kill your darlings.
- •Momentum is a PM’s job; most product decisions are two-way doors
- •Meta’s PM model: product sense (intuition) + execution
- •Build intuition through relentless user conversations and anecdote libraries
- •Put out an opinion early to trigger reactions and faster convergence
- •Maintain agility: strong opinions, weakly held; pivot when evidence changes
- 26:36 – 32:48
Direct communication without steamrolling: signaling confidence and making feedback two-way
To avoid strong opinions becoming domineering, Mihika advocates explicit “confidence labeling” and clear norms about disagreement. She shares a practical feedback approach—ask for feedback first, then give yours—and emphasizes acting on feedback to reinforce trust.
- •Strong conviction can backfire if others interpret it as immovable
- •Explicitly state confidence level: strong/medium, hypothesis vs. decision, defer when needed
- •Set expectations: invite disagreement and normalize pushback
- •Directness only works if it’s two-way; avoid one-direction feedback dynamics
- •Operational feedback habit: ask for feedback first, then share yours, then act on it
- 32:48 – 42:19
Building hype that actually moves work: internal moments, external delight, and brand-aligned excitement
Mihika frames hype as the PM’s responsibility—especially for bottoms-up, 0→1 ideas that need oxygen to survive. She shares tactics for internal visibility (surprise demos at big forums) and external hype (FigJam’s “birthday” Easter-egg launch), emphasizing that hype must match the product’s personality.
- •PMs must track team sentiment and proactively create excitement
- •Use big moments (SKO, Maker Week, Config) to show—not tell—the future
- •Scrappy visibility creates learning: more eyes yields more product signal
- •External hype can be driven through delight rituals (Easter egg hunt presents)
- •Hype should align with brand: FigJam playfulness vs. Figma’s pro power-user delight
- 42:19 – 47:16
Staying inseparable from users: talk to users and non-users, and partner with sales
Mihika explains how she keeps a constant pulse on users across contexts—from casual dinners to formal sales calls. She stresses the unique value of talking to non-users (perception and onboarding barriers) and outlines how user access changes depending on product type and company stage.
- •Immerse in the circles where your users are; make it a daily habit
- •Non-user conversations can be more insightful than user conversations
- •Adoption depends on perception/positioning—not just product quality
- •Early-stage: PMs/founders must source user conversations directly
- •Larger companies: build tight loops with sales; join calls to cross-pollinate pain points
- 47:16 – 51:34
Operationalizing insights: roadmap signal, sales enablement artifacts, and structured feedback capture
Lenny pushes for the “what do you do with what you hear” layer, and Mihika shares concrete systems. Insights influence roadmap priority, become enablement artifacts (like a ‘week in FigJam’ Loom), and get stored and groomed via lightweight tooling integrations.
- •Set recurring cadences with sales to exchange insights and upcoming plans
- •Turn real usage into teachable artifacts that help sales evangelize (Loom walkthroughs)
- •Use sales/customer input to prioritize and de-prioritize roadmap items
- •Capture feedback at scale via Slack→Asana workflows and weekly grooming
- •Accept that not all feedback is immediately actionable—store it for later
- 51:34 – 58:27
Caring deeply and finding passion: align assumptions, expand your scope, and “found” inside or outside
Mihika ties passion to shared assumptions: disagreements often come from mismatched underlying beliefs. For listeners stuck on uninspiring work, she recommends zooming out to company vision, treating scope as expansive, and considering ‘founding’ either internally (distribution/platform advantages) or externally (more autonomy).
- •Julie Zhuo insight: strategy disagreements often stem from different assumptions
- •Passion is more natural when you truly believe in the idea and its assumptions
- •Don’t confuse current project with your scope—“your scope is the world”
- •Founding inside a company: distribution/platform advantage, lower risk, but more buy-in needs
- •Founding outside: different team-building and decision-making dynamics
- 58:27 – 1:07:07
Culture as a PM superpower: Hot Seat, FIGGIES, and making trust durable in a remote world
Mihika shares two culture rituals she helped popularize at Figma: Hot Seat (rapid-fire personal Q&A) and the FIGGIES (a playful internal awards show). She argues culture is not fluff—it's a trust-building mechanism that increases team durability when roadmaps and priorities inevitably change.
- •Hot Seat: two-minute Q&A per person; builds understanding of motivations and backgrounds
- •StrengthsFinder and personality tools as accelerators for team bonding
- •FIGGIES: scrappy Oscar-style awards celebrating quirks and contributions
- •Culture creates trust; passion comes from both vision and people
- •Remote-first makes intentional togetherness and “Play” rituals even more important
- 1:07:07 – 1:16:06
Pivoting with grace: Design Nation, adaptability under constraints, and high agency
To illustrate adaptability, Mihika tells the origin story of Design Nation—created to democratize design education when universities lagged behind industry shifts. When institutional support fell through, she pivoted to scrappy cold outreach and fundraising, showing how resourcing priorities must shift as reality changes.
- •Design’s rise as a differentiator (Airbnb/Pinterest era) wasn’t reflected in curricula
- •Design Nation formed from the gap: bring students and industry leaders together
- •Loss of expected backing forced a pivot to building from scratch
- •Cold emailing and scrappy legitimacy-building (landing pages, fundraising) as survival skills
- •Adaptability = re-prioritizing the bottleneck (speakers vs. funding vs. credibility)
- 1:16:06 – 1:29:15
0→1 inside a company: keeper-of-the-flame, idea→buy-in→wildfire, and spreading via dogfooding
Mihika lays out her 0→1 framework using the “flame” metaphor and the Greek goddess Hestia as the keeper of the hearth. She explains the three essentials—right idea, leadership/team buy-in, and internal spread—and shows how staging/dogfooding turns the whole company into co-builders through feedback ownership loops.
- •Companies must stay entrepreneurial to remain competitive; Figma’s run-with-it culture supports this
- •Three pillars: right idea (empathy), secure buy-in (vision), spread it (wildfire)
- •Pitching requires “optimism that borders on delusion”: translate “no” into “not yet”
- •Hackathons as forcing functions: make it feel real via selective scrappy believability
- •Staging/dogfooding spreads adoption: feedback → implemented change → personal ownership → more investment
- 1:29:15 – 1:40:40
Final takeaways and lightning round: motivations, books, and Mihika’s operating principles
Mihika closes with advice to evangelize unique insights loudly and to tailor collaboration to individual motivations by asking directly what people want involvement in. The lightning round covers influential books, favorite media, admired onboarding, AI product thoughts, and her motto about expectations.
- •If you see an insight others don’t, it’s your job to bring people along
- •Understanding motivations is key to leading cross-functional teams; ask explicitly
- •Lightning round picks: Harry Potter, Pachinko, Creativity Inc; Severance; Dune
- •Great onboarding reference: Arc; AI product reflection: Pika and “de-black-boxing” outputs
- •Life motto: manage expectations (e.g., don’t watch trailers/read back covers)
