Lenny's PodcastHow to foster innovation and big thinking | Eeke de Milliano (Retool, Stripe)
CHAPTERS
- 0:00 – 3:57
Minimum viable process: why process reduces variance (and can dull top performers)
Eeke opens with a core tension of process: it raises the floor by reducing variance, but can also pull exceptional, creative performers down toward the mean. She frames why bigger companies naturally add more process and why that tradeoff must be managed intentionally.
- •Process is designed to reduce variance and standardize outputs
- •Standardization can unintentionally suppress creativity and high performance
- •The bigger the company, the harder it is to rely on “process-free” execution
- •Great teams need mechanisms to preserve high-end creativity while scaling
- 3:57 – 8:57
From early Stripe AE to foundational products: Connect and Radar
Eeke recounts joining Stripe in 2013 (around 50 people) before PMs existed, starting as the first account executive and spending her days in customer conversations. Those insights helped drive major products like Stripe Connect for marketplaces and Stripe Radar for fraud prevention.
- •Stripe had no PMs when Eeke joined; she started in a customer-facing role
- •Marketplace payments created new, complex regulatory and payout needs
- •Stripe Connect evolved to serve two-sided marketplace payment flows
- •Stripe Radar combined ML fraud detection with explainability and customer controls
- 8:57 – 11:04
Why Stripe (and Retool) added PMs late: building for developers, then scaling complexity
Lenny and Eeke explore Stripe’s late adoption of product management (around ~100 employees) and why it worked early on. The inflection point came as customer types expanded and the company became more matrixed across countries, compliance, and product lines—work that PMs help coordinate.
- •Developer-focused products can succeed longer without traditional PM structure
- •Early on, engineers can effectively do much of the PM work
- •PMs become essential as ICPs diversify and organizational complexity increases
- •Payments products add cross-functional overhead (legal, compliance, country expansion)
- 11:04 – 12:22
PM reality check: influence without authority (and why the job isn’t for everyone)
Eeke shares a candid take on product management as a career choice. She emphasizes that the job is largely cross-functional influence work and can surprise people who expect direct control, similar to misconceptions about becoming a manager.
- •PM work is heavy on coordination and influencing without direct reporting lines
- •Many people enter PM expecting control; reality is negotiation and alignment
- •Sales experience can be an unusually strong foundation for PM skills
- •Being sure you enjoy the “messy middle” is crucial before switching careers
- 12:22 – 19:00
Stripe’s culture guide: opinionated culture, rigorous thinking, and strong writing
Eeke describes creating Stripe’s culture guide to help candidates self-select into (or out of) Stripe’s ways of working. She attributes Stripe’s success less to one magic decision and more to consistently making many high-quality decisions, supported by first-principles thinking and a writing-heavy culture.
- •Culture guide was designed for candidates: attract the right people, repel the wrong ones
- •Stripe prized rigorous thinking and first-principles reasoning in everyday decisions
- •Writing (memos, reviews, strategies) was central to communication and clarity
- •High velocity decision-making required balancing rigor with speed
- 19:00 – 21:23
Operating principles: urgency, users first, and “micro pessimists, macro optimists”
Eeke shares memorable Stripe operating principles and how they shaped behavior. She highlights the practical use of “one-way vs two-way door” decisions, plus the importance of choosing carefully on true trapdoor decisions like titles.
- •“Move with urgency and focus” as a startup advantage against time
- •“Users first” as a guiding heuristic for product choices
- •“Micro pessimists, macro optimists” to balance long-term belief with day-to-day rigor
- •Using one-way/two-way door framing to decide when to move fast vs slow
- 21:23 – 24:52
Why innovation stalls: fear of failure, constant fires, and lack of time to think
Eeke reframes the innovation question: most people want to do meaningful work, so what blocks big thinking? She points to fear of failure, getting buried in urgent debt/instability, and the genuine difficulty of strategic creativity without explicit “permission to think.”
- •Innovation requires accepting the cost: sometimes you’ll fail
- •High operational load (bugs, incidents, debt) prevents strategic work
- •Thinking big is hard and needs protected time, not just encouragement
- •Leaders must deliberately create structures that invite bigger thinking
- 24:52 – 27:28
Systematizing big ideas: Crazy Ideas doc + planning prompts that unlock creativity
Retool uses lightweight rituals to encourage ambitious thinking: a yearly “Crazy Ideas” doc and explicit “Think Bigger” sections in team charters. The goal is low-pressure idea generation that still yields real shipped outcomes, not just feel-good brainstorming.
- •Annual “Crazy Ideas” doc invites high-upside, low-probability ideas org-wide
- •Retool revisits last year’s list and often executes 3–8 ideas from it
- •Team charters include a “Think Bigger” prompt (e.g., with 20% more time)
- •Less structure can increase participation and reduce intimidation
- 27:28 – 31:53
Creating a failure-safe space: normalize learning and broadcast the follow-ups
Eeke focuses on what happens after something fails: the follow-through determines whether failure becomes fear-inducing or learning-rich. She recommends sharing learnings publicly in the same forums typically reserved for wins, turning setbacks into organizational knowledge.
- •Normalize failure by shining light on it in public forums
- •Use retrospectives to emphasize learning over blame
- •Share “what we learned” write-ups broadly (emails, all-hands)
- •Lower stakes by shortening feedback loops and reducing time-to-customer-input
- 31:53 – 35:20
Launching three products in one year: Workflows, Mobile, and Database
Eeke outlines Retool’s three major launches and what each added to the platform. She reflects on the tradeoffs of launching multiple products in parallel, including organizational headspace and the potential benefits of better sequencing.
- •Retool Workflows: scheduled/triggered tasks with visual building + code
- •Retool Mobile: build native mobile apps for non-desk/field workflows
- •Retool Database: managed Postgres with a friendly UI integrated into Retool
- •In hindsight, staggering launch narratives might have reduced cognitive load
- 35:20 – 38:00
How Retool shipped in parallel: tiny teams, internal VC model, and deliberate isolation
Retool started each new product with minimal staffing and scaled investment only after clear customer signal. Eeke explains an internal “Retool as VC” model and a deliberate choice to keep early teams separate from core processes to preserve speed—then later invest to integrate products well.
- •Start with 1–2 people per initiative; fund only after proving “there there”
- •Treat new products like startups: prove ROI in engagement/revenue to earn resources
- •Keep early teams insulated from core-product constraints and process drag
- •Isolation accelerates learning but creates later integration costs across products
- 38:00 – 45:37
Scaling process without killing creativity: escape hatches, charters, goals, and roadmaps
Eeke introduces “minimum viable process” and argues for explicit escape hatches in templates and rules. She suggests every level of the org needs three core artifacts—charter, goals, and roadmap—while the time horizon of those documents should expand as the company matures.
- •Process reduces variance but risks “averaging down” top performers
- •“Minimum viable process” + explicit permission to break templates when needed
- •Core artifacts: charter (mission/vision/strategy), goals, and roadmap
- •Start planning top-down; early-stage horizons can be ~3 months vs multi-year later
- 45:37 – 50:59
Product craft mental models: best users, scooter-not-axle MVPs, and 70/20/10 allocation
Eeke shares practical heuristics for building and prioritizing. She advocates designing early for the best-fit users, delivering end-to-end value with a “scooter” MVP, and managing resources with a 70/20/10 portfolio—while acknowledging the perennial difficulty of making space for maintenance.
- •Build for your best users early; don’t over-optimize for edge-case abuse
- •“Build the scooter, not the axle”: deliver complete value in a smaller slice
- •Use 70/20/10 to balance core product, strategic initiatives, and bets
- •Maintenance/bugs are tricky; approaches vary by team (bug bashes, continuous polish)
- 50:59 – 56:13
Customer closeness at Retool + sales-led vs product-led: tight GTM feedback loops
Eeke explains why Retool PMs stay unusually close to customers: customer-facing backgrounds, technical depth, heavy Slack-based collaboration, and dogfooding Retool to run internal operations. She then contrasts sales-led and product-led dynamics, emphasizing crisp interaction mechanisms with sales/support and experimenting with a “science fair” roadmap format.
- •Many PMs come from customer-facing roles, sharpening value/ROI intuition
- •High technical fluency helps PMs engage deeply with users’ real workflows
- •Customer Slack channels provide rapid, candid feedback loops
- •In sales-led contexts, success depends on tight bidirectional communication with GTM teams
- 56:13 – 1:02:55
Building a product talent portfolio + lightning round highlights
Eeke describes the “product talent portfolio” approach: building complementary teams instead of hiring clones of yourself. She closes with a lightning round covering books, podcasts, interview questions, favorite tools, and where listeners can find her.
- •Avoid hiring in your own image; balance complementary PM strengths
- •Mix homegrown culture carriers with experienced external PMs for rigor
- •Run periodic audits of team strengths/weaknesses and hire to fill gaps
- •Lightning round: writing/management books, curiosity-driven podcasts, interview question, favorite tools, and how to reach her
