The Twenty Minute VCKaz Nejatian: How Shopify Built a $90BN Business to Last 100 Years | E1189
CHAPTERS
- 0:00 – 1:01
Shopify’s PM credo and the backlash against “Lean Startup” shipping
Kaz opens with Shopify’s definition of a PM’s job and argues that “Lean Startup” thinking is widely misapplied. He draws a sharp distinction between iterating on a complete V1 versus shipping unusable, incomplete software that burns user trust.
- •PMs should build the right thing, the right way, at the right time
- •Kaz argues Lean Startup is often misunderstood and leads to bad software in production
- •Users don’t want to feel like they’re being tested on with broken products
- •A good V1 can be constrained but still complete and usable
- •Vision matters: you can iterate while still aiming at an end state
- 1:01 – 2:11
Takeaways from Keith Rabois (and Max Levchin): hunger, aggression, and ambition
Harry asks for Kaz’s biggest lesson from working with Keith Rabois. Kaz describes Keith (and Max) as uniquely aggressive in execution—kind, but relentlessly ambitious—and says their defining trait is perpetual hunger.
- •Keith and Max pair kindness with extreme executional aggression
- •High ambition shows up in pace and intensity, not just strategy
- •Kaz’s key takeaway: stay perpetually hungry
- •Aggressiveness can be a competitive advantage when channeled well
- 2:11 – 6:35
Vision vs iteration: why ‘complete products’ win
Kaz explains why a strong vision is necessary even if it evolves over time. He uses analogies (chairs, woodworking, movies) to argue that software must be coherent and complete to be lovable, and that ‘ship-to-see-what-happens’ without a vision produces junk.
- •Vision can change, but you need one to build anything great
- •Complete vs incomplete: shipping ‘three-legged chairs’ isn’t acceptable
- •Software is closer to craftsmanship (woodwork) than people admit
- •Great products often require the whole ‘movie’ to work
- •Iterating is fine when V1 is a constrained version of the final vision
- 6:35 – 8:29
Working with Tobi Lütke: priority stack and an unusually high quality bar
Kaz shares what he’s learned from Shopify founder Tobi: a clear, unwavering priority order and a deep commitment to product quality. He argues that Shopify’s tendency to ‘overbuild’ only makes sense if you’re optimizing for decades, not quarters.
- •Shopify’s priority stack: build great products → make money → reinvest to build more
- •Maintaining that stack is hard as a large public company
- •Shopify holds back what many companies would ship
- •Overbuilding looks inefficient short-term but pays off over long horizons
- •Time horizon (discount factor) changes what “efficient” means
- 8:29 – 12:27
Why Shopify builds internal tools (and why Excel is the real villain)
Harry challenges Shopify’s decision to build many internal systems instead of buying tools like Jira/Linear. Kaz argues tools shape how organizations think and operate, and that duct-taped SaaS plus CSV/Excel workflows create false certainty and bad decisions.
- •“First we build our tools, then our tools build us”
- •Internal tools can encode a company’s unique operating philosophy
- •Shopify’s internal GSD tool supports prioritization and stakeholder management
- •Excel creates false certainty; headcount plans become wrong immediately
- •Integrated internal systems reduce brittle CSV-export decision-making
- 12:27 – 20:44
Truth-seeking culture: disagreeability, learning, and hiring for capability over pedigree
Kaz describes Shopify as a place where candid disagreement is normal and useful, in service of truth. He reframes “learner mindset” as a real tradeoff against pure experience, and explains why Shopify expects even non-engineers to be technical and self-sufficient.
- •Shopify values honest disagreement as part of truth-finding
- •“Learner mindset” can conflict with experience-first hiring models
- •Some companies ‘cosplay’ as learners while forbidding questions
- •Shopify expects marketers to use GitHub and write some code
- •Technical literacy (SQL, basic coding) is part of being effective at Shopify
- 20:44 – 23:16
Lessons from Mark Zuckerberg & Meta: risk-taking, News Feed, and AR/VR persistence
Kaz argues Meta and Mark Zuckerberg are underappreciated, especially in risk calibration. He cites foundational product pivots like News Feed and the Like button, and defends Meta’s long-term AR/VR investments as increasingly validated by real product progress.
- •Zuck’s standout skill: understanding and taking risk appropriately
- •Meta made massive early product changes others would fear today
- •AR/VR bets required backbone amid public ridicule
- •Ray-Ban smart glasses are framed as near ‘iPhone moment’ progress
- •Judge risk decisions by process, not just outcome
- 23:16 – 24:48
Meta’s biggest miss: reputation, storytelling, and educating the outside world
Asked about Meta’s worst bet, Kaz points to communications and reputation management rather than product strategy. He argues Meta let misleading narratives spread, creating regulatory and public backlash, despite its outsized contribution to founder creation.
- •Execution focus came at the cost of external narrative control
- •Failure to educate outsiders led to reputational and regulatory pain
- •Kaz believes the long-run impact will still be massive
- •Meta has produced an exceptional number of successful founders
- •Reputation is an asset that needs intentional investment
- 24:48 – 27:48
Why great PMs ‘blame themselves’: user outcomes and the primacy of “how”
Kaz explains product management as a modern role responsible for user outcomes, not just roadmaps. He emphasizes Shopify’s triad—right thing, right way, right time—and argues most organizations overfocus on “what” while underestimating “how,” including technical placement in the stack.
- •PM role: represent users’ best outcomes, not just wishes
- •If users aren’t better off, the PM must own the failure
- •Shopify optimizes for right thing + right way + right time
- •Kaz would trade off ‘right thing’ before ‘right way’
- •PMs must understand how code is written to make better stack-level decisions
- 27:48 – 30:18
The real cost of talk: meeting economics, writing things down, and AI-era workflows
Harry challenges the idea that ‘talk is cheap’; Kaz argues listening time is expensive and Shopify makes meeting cost visible. He advocates shifting communication to written artifacts and code, noting that written traces also become valuable training data for AI systems.
- •Talk isn’t cheap because other people pay the listening cost
- •Shopify calculates and displays the cost of meetings in invites
- •Preference for written communication over live meetings
- •Written work creates reusable organizational memory
- •LLMs benefit from documented reasoning and decision trails
- 30:18 – 34:00
Remote work: why Shopify made it work (and why most companies shouldn’t try)
Kaz takes a contrarian stance: remote work is a bad idea for most companies. He says Shopify succeeds remotely only because it invested heavily in systems, tools, and deliberate practices—and warns that ‘YOLO remote’ will fail for most organizations.
- •Kaz discourages most companies from going remote
- •Shopify invested heavily in tooling and process to support remote culture
- •Remote transition initially failed for 6–12 months
- •Shopify often succeeds with strategies that would be bad for others
- •Two core values: thrive on change and maintain a true learner orientation
- 34:00 – 37:20
Shopify’s toughest changes: committing to remote and reinventing compensation
Harry asks what change Shopify struggled with most; Kaz names remote transition and a major compensation redesign. He details how Shopify ‘burned the bridges’ to avoid backsliding and describes the operational/legal complexity of letting employees allocate a compensation “pile” across instruments.
- •Remote shift broke prior in-person cultural mechanics
- •Shopify reduced optionality by giving up leases and hiring away from hubs
- •Compensation: employees allocate a total package across salary/equity options
- •Implementation involved legal constraints (especially in Europe)
- •Painful transitions can yield durable differentiators once stabilized
- 37:20 – 48:42
Shopify’s growth and “enterprise”: an operating system, not bespoke services
Kaz explains Shopify’s growth as a portfolio of merchants—many fail, some become huge—and why that’s hard to model. He also reframes Shopify’s enterprise move as ‘stopping saying no’ once the product was ready, while refusing bespoke “if enterprise” code and ‘party trick’ demos.
- •Shopify grows as merchants start businesses and Shopify shares in their upside
- •Hard to model like venture outcomes: cohort success is uncertain
- •Shift to enterprise framed as readiness, not a new identity
- •“No party tricks”: don’t demo features that only work in narrow conditions
- •No bespoke enterprise branches in the codebase; build good software that scales
- 48:42 – 53:57
Information flow as a superpower (and Kaz’s biggest recurring mistake)
Kaz says his biggest mistakes come from restricting information flow through hierarchy rather than sharing openly. He argues that default-open communication prevents duplicate work, improves decision quality via opposing views, and builds trust—while acknowledging some information must be controlled for legal reasons.
- •Recurring failure mode: information constrained by org chart routing
- •Default should be public sharing; bosses can learn with everyone else
- •Open debate surfaces opposing views earlier and improves outcomes
- •Values only matter when a reasonable opposite exists (e.g., Apple secrecy)
- •Transparency reduces duplicate builds and increases alignment across teams
- 53:57 – 1:00:18
Marriage, success, and the ‘third entity’: caring for the relationship itself
In a personal turn, Kaz defends marriage using research on health, wealth, and happiness outcomes (especially for men). He emphasizes that a marriage requires caring for three things—self, spouse, and the marriage—and shares practical habits like frequent date nights even with four kids.
- •Don’t model life after ultra-rare $100B+ outliers and their divorce stats
- •Divorce stats are skewed by repeat divorces; first marriages fare better
- •Research links marriage to better health, wealth, and survival outcomes
- •Marriage requires caring for the marriage as its own entity
- •Practical discipline: weekly-ish date nights even amid busy family life
- 1:00:18 – 1:05:47
Quick-fire: hiring pipelines, career advice, politics media diet, and admired strategies
Kaz closes with rapid responses: Meta as a strong leadership training ground, the difficulty of industry-switch hires, and career advice to optimize early for shipping. He mentions changing his mind on the gold standard, advises a low-frequency approach to political news, and praises Microsoft/OpenAI, ExxonMobil, Canva, and Figma’s resilience post-acquisition collapse.
- •Best leadership source: Meta (strong training program)
- •Industry switching is harder than most people expect
- •Early-career advice: optimize for reps/at-bats and shipping, not titles
- •Politics: check weekly, avoid horse-race obsession
- •Admired strategies: Microsoft+OpenAI, ExxonMobil optimization, Canva craft, Figma’s post-deal momentum
