Lenny's PodcastVision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product, Figma)
CHAPTERS
Why Mihika is so highly regarded: strengths-first PMing and her hybrid background
Lenny sets up the episode as an “archaeology” of Mihika’s product craft, sharing how often she was cited as a top PM. Mihika frames her style as strengths-led (not “check every box”), grounded in her CS + visual arts background and a growth mindset.
- •Lenny’s outreach surfaces vision as Mihika’s standout superpower
- •Mihika’s path: CS major + visual arts minor → engineer/designer → product
- •PM as a generalist role with different ‘spikes’ depending on entry path
- •Lean into strengths while actively developing weaker areas
The core PM attribute: building a vision that survives messy reality
Mihika argues vision is the anchor that keeps teams moving through chaos, pivots, and setbacks. She explains that strong visions aren’t created in isolation—they require deep user connection and cross-functional synthesis.
- •Vision answers: ‘If we do our job, what does the world look like?’
- •Product development is chaotic; vision prevents discouragement during pivots
- •Great vision requires tight coupling with users and the team
- •Cross-pollination across research, design/prototyping, and engineering feasibility
- •Using a unified narrative rather than a linear handoff process
How Figma sells vision internally: prototypes, proof points, and one shared artifact
Mihika breaks down how to communicate vision inside a detail-oriented, visual culture: make it tangible and emotionally legible. Instead of separate research/design/product readouts, the team rallies around a single combined deliverable.
- •Words alone are limited—visuals and prototypes create belief
- •Pitch structure: pain point → solution → proof point (repeat)
- •Combine user testimonials with mocks/prototypes to make pain felt
- •Create one shared artifact (often a deck in Figma) to unify team ownership
- •Figma’s ‘see to believe’ bias: prototype before a project is fully greenlit
Case study: the vision behind FigJam meetings—making work more democratic
Using FigJam’s pandemic-era rise, Mihika shares how the team expanded from “brainstorming tool” to a broader vision for how meetings should work. The insight: brainstorms feel democratic, and that generative energy can become the norm across meeting types.
- •Pandemic dislocation created demand for shared collaborative spaces
- •Key observation: brainstorms are the most common FigJam meeting behavior
- •Figma internally used FigJam for far more than brainstorms—gap to external usage
- •Brainstorms as democratizing: ideas from anywhere, not dominated by loud voices
- •Vision becomes concrete via rituals/templates and features like music and voting
Delivering a vision without design/engineering skills: AI + ‘just ask people’
Lenny probes how PMs can “make it real” without prototyping chops. Mihika points to AI lowering the barrier and emphasizes high-agency recruiting: walk around, ask for collaborators, and use hackathons to assemble a team and momentum.
- •AI is lowering the floor for building prototypes and demos
- •Replit as ‘technical co-founder’ analogy; future tooling as ‘designer co-founder’
- •Use internal hackathons (Maker Week) as a forcing function for reality
- •Don’t let missing skills block you—recruit help aggressively
- •Momentum can start with one yes, then compound into a team
Conviction and momentum: strong opinions, weakly held
Mihika explains conviction as a momentum engine—most software decisions are reversible, so it’s better to put a stake in the ground than wait for perfect certainty. Conviction comes from relentless user curiosity and pattern recognition across many conversations.
- •Momentum is a PM’s job; many decisions are ‘two-way doors’
- •Conviction is fueled by intuition built through constant user conversations
- •Build a ‘library’ of anecdotes to draw on for decisions
- •Put out an idea (even wrong) to trigger reactions and converge faster
- •Balance conviction with agility: ‘kill your darlings’ when evidence shifts
Directness without toxicity: make confidence explicit and keep feedback two-way
Mihika shares how her direct communication style can land well when it’s paired with clarity and reciprocity. She operationalizes it by explicitly stating confidence levels, inviting disagreement, and making feedback a continuous, actionable exchange.
- •Explicitly label confidence: strong vs medium vs ‘I defer’
- •Set norms early: tell teammates you want pushback and candor
- •Directness only works if it’s two-way; otherwise it becomes intimidating
- •Start feedback by asking: ‘Do you have feedback for me?’
- •Act on feedback quickly to reinforce the ‘feedback is a gift’ loop
Building hype (internal and external): demos, big forums, and emotional resonance
Mihika distinguishes internal hype (buy-in inside the company) from external hype (users celebrating with you). She describes using high-leverage moments—like SKO keynotes and product anniversaries—to create surprise, visibility, and delight.
- •Zero-to-one requires the champion to manage the room’s emotional temperature
- •Leverage big forums (SKO, Maker Week, Config) to ‘show, don’t tell’ via demos
- •Put work in front of people earlier than feels comfortable to get signal
- •FigJam anniversary launch: in-product Easter egg ‘birthday presents’
- •Hype must match product brand—delight looks different for different products
Immersing in user insights: talk to users—and especially non-users
Mihika explains how she stays close to user reality, which underpins vision and conviction. A key tactic is seeking out non-users to understand adoption friction, perception gaps, and onboarding needs—especially for expanding beyond core audiences.
- •Different products require different user-access strategies
- •Ask non-users why they aren’t using the product—often most revealing
- •Broaden perspective beyond your product to users’ full toolchain/workflow
- •Example: non-designer barriers in FigJam led to easier ‘getting started’ experiences
- •For niche/enterprise products: rely on customer-facing orgs and targeted outreach
Operationalizing user insights: cadence with sales, artifacts, and backlog capture
Lenny pushes for tactics: how insights get turned into action. Mihika details recurring loops with sales, creating shareable artifacts (like a “week in FigJam” Loom), and lightweight systems to capture and groom feedback at scale.
- •Set recurring touchpoints with sales to exchange signals both ways
- •Use sales input to prioritize/deprioritize roadmap decisions
- •Create evangelism artifacts that help customers see new use cases
- •Store non-immediate feedback via Slack→Asana capture and weekly grooming
- •Operationalize insights without losing the nuance of real conversations
Caring deeply and finding passion: scope is bigger than your current project
Mihika connects passion to shared assumptions and belief in the underlying why. For people not excited by their current work, she urges stepping back to the company vision, seeking a problem you genuinely care about, and considering founding internally or externally.
- •Disagreements often come from different assumptions (Julie Zhuo lesson)
- •Passion follows belief—don’t execute a roadmap without understanding its assumptions
- •Reframe: your scope isn’t the current project; ‘your scope is the world’
- •Anyone can ‘found’—inside a company (distribution/platform) or outside (autonomy)
- •Choose based on risk tolerance and where your passion can realistically live
Culture as a PM lever: Hot Seat, FIGGIES, and making teams durable
Mihika shares specific rituals she initiated to build trust and fun—especially important in remote-first realities. Culture, for her, is not fluff: it creates durable teams that rally together when roadmaps and priorities inevitably change.
- •Hot Seat: rapid Q&A game to learn what motivates teammates
- •StrengthsFinder as a team bonding and self-awareness catalyst
- •FIGGIES: scrappy Oscar-style awards to celebrate quirks and contributions
- •Figma’s ‘Play’ value legitimizes investing time in team joy
- •Passion comes from both the vision and the people—culture builds trust
Pivoting with grace: Design Nation and high-agency adaptability
To illustrate adaptability, Mihika tells the origin story of Design Nation—built from scratch after initial institutional support fell through. The story highlights scrappiness, reframing priorities (fundraising vs speakers), and making progress without formal backing.
- •Design’s rise in tech wasn’t reflected in university curricula
- •Initial plan to build within an existing org failed → rebuilt independently
- •Cold emailing using a .edu address to recruit supporters and speakers
- •Adapt resourcing and priorities as constraints change
- •Design Nation’s mission: democratize design education for design-driven students
Weaknesses and the ‘shadow’ of strengths: conviction, scrappiness, detail-focus
Mihika names how her strengths can create downsides—especially early in relationships. She emphasizes self-awareness and building balanced teams that cover blind spots while letting individuals remain ‘spiky.’
- •High conviction can trigger skepticism without established trust
- •Scrappiness can frustrate others (last-minute decks, late starts)
- •Detail-immersion is useful but can delay decisions when tradeoffs are needed
- •Every superpower has a shadow; manage it intentionally
- •Hire to create a well-rounded team even if individuals are specialized
0→1 inside a company: the flame-keeper model and a 3-step playbook
Mihika explains why companies must stay entrepreneurial to remain competitive and how Figma’s values and hackathons enable that. She offers a simple framework: right idea, buy-in, and internal spread—framed through a ‘keeper of the flame’ metaphor.
- •Entrepreneurship is required for long-term competitiveness
- •Figma ‘run-with-it’ culture + hackathons produce major launches (widgets, JamBot, etc.)
- •Flame metaphor (Hestia): keep the hearth burning and help it spread
- •Three steps: right idea (empathy), secure buy-in (vision), spread internally (wildfire)
- •Great ideas require user empathy plus alignment to company goals
From pitch to company-wide momentum: hackathon demos, staging, and shared ownership
Mihika details how persistence and iteration made her new-product pitch finally “stick,” especially via Maker Week. She also explains how long dogfooding/staging cycles both improve quality and create internal advocates who feel they shaped the product.
- •‘Optimism bordering on delusion’: translate ‘no’ into ‘not yet’
- •Use company-wide forums to convert a solo pitch into peer-driven evangelism
- •Hackathon tactic: make small UI changes that dramatically increase believability
- •Figma’s extended staging/dogfooding: feedback improves product and builds investment
- •People who see their feedback implemented become champions of the launch
Closing guidance + lightning round: motivations, books, and personal operating principles
Mihika closes with advice on broadcasting unique insights and tailoring collaboration to individual motivations. The episode ends with a lightning round covering books, media, favorite products, and a motto about expectations.
- •If you see something others don’t, it’s on you to ‘shout from the rooftops’
- •Team effectiveness depends on understanding individual motivations
- •Ask directly: how much someone wants to be involved in product decisions
- •Lightning round highlights: Harry Potter, Pachinko, Creativity Inc; Severance; Dune
- •Motto: ‘Life is a game of expectations’—avoid trailers/back covers to reduce bias
