Mar 20, 2024 · 1h 10m · news
Jean-Michel Lemieux: Three Product Decisions Every Team Needs to Make | E1129 · 20VC with Harry Stebbings
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview, former Shopify and Atlassian CTO Jean-Michel Lemieux shares tactical wisdom on streamlining software development by eliminating bloated processes and prioritizing shipping velocity. He outlines strategic alignment models, structured hiring frameworks, and explains how AI and hard-tech innovations will shape the future of product engineering.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Harry holds 19.3% of the talking time here. How this is scored →
Harry as informed peer 3.7 Guest teaching 3.3 Guest disagreement 1.7 Harry pushing back 3.0
speaking balance: gold is Harry, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 33:30 Guest calling host naive
Jean-Michel bluntly rejects Harry's hands-off trust battery stance, calling his approach 'a bit naive in a sense' when pushing the Susan Scott decision tree framework.
Hardest push from Harry ▶ 31:47 Host rejecting daily Slack updatesHarry forcefully pushes back on Jean-Michel's practice of sending daily decision updates to the CEO, asserting that highly paid executives should make decisions without constantly messaging their boss.
Biggest teaching moment ▶ 46:40 FBI hostage negotiation lessonWhen Harry argues that founders cannot wait months for a hire, Jean-Michel schools him using FBI hostage negotiation techniques from Chris Voss to demonstrate how to buy time.
Harry holds his own ▶ 1:01:50 Host challenging startup valuations and GTMHarry demonstrates strong venture capital expertise by dismantling the economics of Equals.com, questioning its $35M valuation and highlighting messy product-marketing ACV friction.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| Falling in Love with Product and Tech | 1 | 1 | 0 | 0 | Harry opens with an inviting question about falling in love with tech. Jean-Michel shares his background using MIDI and Cubase in 1988 to compose music for a high school musical. | |
| Career Advice for Graduates | 2 | 2 | 1 | 1 | Harry asks for career advice for graduates on safe vs. risky paths. Jean-Michel slightly reframes the 'do what you love' cliché into 'do something you're good at.' | |
| Quality vs. Speed: Differences Between Shopify and Atlassian | 5 | 3 | 1 | 2 | Jean-Michel turns the question back on Harry to compare notes on founders. Harry offers sharp observations on Harley Finkelstein vs. Scott Farquhar before Jean-Michel contrasts Shopify's quality focus with Atlassian's speed focus. | |
| The Power of Narrowing Your Ideal Customer Profile (ICP) | 4 | 2 | 1 | 2 | Harry quotes his own tweet about narrowing ICP to build customer love. Jean-Michel agrees, noting that companies die of indigestion rather than starvation. | |
| Time-Capping and Focusing on the Present | 3 | 3 | 1 | 2 | Harry asks about non-negotiable shortcuts like security. Jean-Michel explains his philosophy on time-capping meetings and focusing strictly on immediate shipping rather than distant future planning. | |
| Measuring Progress Through Shipping Velocity | 3 | 4 | 2 | 3 | Harry references Jean-Michel's tweet about retiring from process like Scrum and standups. Jean-Michel elaborates on 'time horizon friction' where planning meetings devour actual building time. | |
| Alignment, Unprogramming School Habits, and Scaling | 3 | 4 | 1 | 2 | Harry asks if process-free execution breaks at scale. Jean-Michel explains the need to unprogram employees from school-instilled homework habits that discourage asking for help or taking shortcuts. | |
| Evaluating Team Quality Based on Output | 5 | 4 | 2 | 5 | Harry challenges how to evaluate performance without process and quotes Jean-Michel back to himself regarding 'hire great people and get out of the way.' Jean-Michel details his critique of complete autonomy. | |
| Pair Programming on Leadership and the Power of Micro-Alignments | 6 | 3 | 4 | 7 | Jean-Michel advocates daily micro-alignment Slacks to CEOs. Harry strongly pushes back, arguing that high-paid executives shouldn't bother him with daily updates under a 'full trust battery' model. | |
| The Decision Tree: Root, Trunk, and Leaf Decisions | 4 | 6 | 5 | 4 | Jean-Michel outlines Susan Scott's Decision Tree and calls Harry's hands-off management stance 'a bit naive.' Harry humorously calls out being labeled naive while enjoying the disagreement. | |
| The Three-Step Hiring Process and the Hardest Thing Question | 2 | 4 | 1 | 1 | Harry asks for Jean-Michel's executive hiring framework. Jean-Michel walks through his 3-step process: the Snowboard Test, deep-dive teaching mode, and 'what is the hardest thing you've built?' | |
| Growth Mindset Over Specific Industry Experience | 2 | 3 | 1 | 2 | Harry asks if industry domain experience matters when hiring. Jean-Michel explains why growth potential and full-stack debugging skills outweigh specific background experience. | |
| Taking the Pressure Off: How to Handle Resignations | 2 | 3 | 1 | 4 | Harry asks about personal hiring mistakes. Jean-Michel admits to rushing when under pressure and details how he now takes stress off by reassuring the remaining team when an executive leaves. | |
| Hostage Negotiation Tactics: Buying Time to Build a Talent Network | 4 | 5 | 3 | 5 | Harry presses that founders often cannot wait six months for a key hire. Jean-Michel invokes Chris Voss's FBI hostage negotiation strategies on buying time and outlines continuous candidate networking. | |
| The Future of Coding: How AI Co-pilots Empower Small Teams | 3 | 3 | 1 | 2 | Harry asks about AI's impact on software engineering team sizes. Jean-Michel shares that AI writes 80% of his code, allowing developers to focus on higher-level architecture. | |
| The Incumbent Advantage and the Shift to Hard Tech | 7 | 3 | 3 | 6 | Harry presents a strong case regarding tech incumbents' unprecedented speed, data moat, and massive free cash flow ($350M/day at Microsoft). Jean-Michel reframes the discussion toward building country operating systems. | |
| Platform Companies and De-risking Hard Tech | 4 | 4 | 1 | 3 | Harry asks if base foundation model layers will commoditize and why great product teams lose momentum. Jean-Michel proposes using 'pace bunnies' to benchmark internal performance against outside peers. | |
| The Zero-to-One Grind: Loneliness, Highs, and Lows | 2 | 2 | 1 | 1 | Harry asks about the hardest part of going back to zero-to-one building. Jean-Michel opens up about founder loneliness and praises Equals.com as a product he loves. | |
| VC Valuations vs. Supporting Hard Product Startups | 7 | 2 | 2 | 6 | Harry critiques startup seed valuations using Equals.com ($35M valuation) as an example, citing GTM and ACV friction. Jean-Michel concede Harry's investor acumen. | |
| Quick-Fire Round: Go-To-Market, Hiring Speed, Support, and Team Tension | 5 | 4 | 2 | 4 | Harry runs a quick-fire round covering CEO errors, hiring pace, and team tension. When Jean-Michel identifies product/design/engineering triad as highest friction, Harry pushes back asking why sales isn't higher. | |
| Inside Shopify's Product Strategy: Volume, Complexity, and Target Customers | 3 | 5 | 1 | 2 | Harry asks how Shopify managed the tension between catering to small bakeries vs. massive enterprise clients like Kim Kardashian. Jean-Michel breaks down the volume vs. complexity matrix. |
Statements from this episode (37)
Lemieux: Excessive process and time horizon friction slow software teams down
“I believe that one of the things that slows teams down the most is what I call time horizon friction. And time horizon friction is caused by a lot of process.”
Lemieux: Choose a career based on strength rather than passion
“You know, like people always say, do something you love. And I'm like, maybe I've heard this. I'm like, do something you're good at, you know? So You know, in some ways my guidance counselor was like, hey, it looks like you're good at it. There's kind of no wr…”
Lemieux: Shopify intentionally positioned itself as a movement, not a product
“Shopify wasn't about the product. It was about a movement of like, let's build this thing around entrepreneurship. And it's not like that was accidental. We had meetings about, you know, I think, you know, we have to create a movement around entrepreneurship a…”
Lemieux: Shopify prioritizes shipping on quality, while Atlassian prioritizes speed
“And I think the non-overlapping I saw the most from the inside was Shopify will ship on quality. Atlassian will ship on speed.”
Lemieux: Product love must take priority over monetization spreadsheets in a startup's first decade
“When you build a company, You have one thing to do is, like, build a product that people can use, and they love it, and they tell their friends about it, right? Like, you can, and you have 10, if you do that for 10 years, and you figure out how to monetize it …”
Lemieux: Early startups die from indigestion of ideas, not starvation
“I think in your first couple of years, absolutely. And I think whoever said this, I'm not sure where this comes from, but you know, companies are going to die from indigestion before they die of starvation. Which means that we all have way too many ideas in ou…”
Lemieux: Polish half your features to perfection and rush the rest
“The good decision is every month pick, you know, half the things that have to be polished, like they're, like the best things on the planet, and half of them don't have to be. You know, and that's where you actually get long-term momentum”
Lemieux: Discussing initiatives months in advance kills company execution speed
“Often companies, the way that they lose time and get slow is not just about, like, what to do fast or slow, but they end up talking about too much stuff that won't happen for three or four months.”
Lemieux: Time-Capping Team Meetings Preserves Execution Speed and Quality
“One of the ways you get speed and quality is by time capping things and then deciding as a team, again, what has to be polished, what doesn't have to be.”
Lemieux: Shopify measured engineering progress strictly by pull requests and shipped code
“And I literally just look at the PRs and the code that we ship and how, how, You know, how much time we spend on that. And that's literally all the progress. And that's the exact same measure I had at Shopify, by the way.”
Lemieux: Software team relies on only one weekly meeting
“And we have one, a one hour meeting a week on Who's stuck? That's it. That's literally all we do, and we ship, and you write code, like, you just, you write your product, we ship it, we run builds”
Lemieux: Shipping software reduces risk far more than planning
“We've all been, I think, indoctrinated into planning reduces risk, and I think shipping reduces risk. So as a company, your job is to reduce the most risk possible. And I just really believe shipping does that.”
Lemieux: Tobi Lütke is actively cutting process overhead at Shopify
“If you look at, I believe Toby at Shopify is implementing this exact same thing. I think we're doing it in parallel universes and we will have beer every summer and compare notes. But I just trying to believe that some of the shift at Toby and Harley have been…”
Lemieux: Tech leaders must unprogram workers from school-style solo homework habits
“So you've, we've got, like, 21 years indoctrinated in getting a homework assignment, going away, and coming back. And then we're like, we throw you into the workforce, and we're like, by the way, now your job is to cheat as much as you can. I'm gonna give you …”
Lemieux: VP of Engineering reviews should focus on shipped code
“I think in a, you know, a, you know, a review of, you know, your VP of engineering, you should be looking at the code that that team shipped.”
Lemieux: 'Hire great people and get out of the way' is flawed advice
“Hiring great people and get out of their way is like, is basically an, it is assuming that everyone is magically going to have the same understanding of the world, is magically going to have the same quality bar, is magically going to be aligned on how they do…”
Lemieux: Tech Companies Dogmatically Over-Index on Autonomy Over Alignment
“I think a lot of companies, they feel that any premise of command and control is like, is, is like a religious faux pas now, right? Like if you don't like pray to the autonomy pulpit and church, you're almost burnt at the stake these days, right?”
Lemieux: A CEO's Primary Fear Is Teams Running in Different Directions
“The only thing on the CEO's mind right now is everyone running off in different directions, and not being able to kind of understand what kind of decisions we're making.”
Lemieux: Dream job questions reveal how candidates act when unsupervised
“I've got so many jobs open. You could do anything here. What's your dream job at Atlassian, at Shopify? What is it? And could you know, could you talk to me about why that is for 10 minutes, right? So, so that question for me is like the ultimate snowboard tes…”
Lemieux: Asking for candidate's hardest project reveals internal quality bar
“I love this one question, which is what's the hardest thing you've built before. Cause I want to know if someone's got a cool, like an internal quality bar, you know? So I'm going to like, and I'm on it again. I want to know what, like what they would put on t…”
Lemieux: Tech leaders must hire 'full-stack debuggers' across all company layers
“That you need someone who, you know, has the, has like the ability to like see and address things that every layer Of your company, right? From the code to the emotions, and seeing that, like, you're basically hiring people who are full stack debuggers of thin…”
Lemieux: Tech leaders must talk to a potential hire every week
“So the other thing that I thought was really important was like, if I did not talk to a candidate every week, and I don't even call them candidate. If I did not talk to someone that I'd love to work with every week, as part of like my ongoing networking, I was…”
Lemieux: AI tools currently write 80% of my code
“And the way it helps me personally is, you know, it writes 80% of my code.”
Lemieux: AI Will Increase Software Jobs by Expanding Developers Into Healthcare
“And you know, what's going to happen is we have a lot more software to write. And that's what people don't realize. Like, is there jobs in software development? Holy shit. Like healthcare agriculture et cetera, like educate, like all these places that need tec…”
Lemieux: AI will unbloat tech teams and redistribute engineers to critical sectors
“I think companies are going to unbloat and we're going to distribute programmers, right? Like there's, we've got a global, you know, lack of procreation happening. We're going to have less and less people who can build technology where we need it. Like we need…”
Stebbings: Microsoft generates $350 million per day in free cash flow
“They don't have the cash flow capabilities of Microsoft doing three hundred and fifty million dollars a day in free cash flow.”
Lemieux: A company building a country OS will become the world's richest
“If someone could come up with a country operating system is probably the next biggest like planet will be the richest company on the planet”
Stebbings: Software VCs will get burned investing in hard tech
“Having software investors invest in hard tech is a very different game. It is like you wouldn't have your sales team Write code. And it's the same thing. It's a very different mindset. So I think a lot of people will get burnt there”
Stebbings: Missed AI foundation models expecting commoditization
“I've missed investing in a lot of the foundational model companies, always believing that that would be just a layer of commoditization there.”
Lemieux: Platform startups face two main exit outcomes
“It's actually a lot harder and you've got two exits, right? Someone's gonna buy you because you're gonna build a layer and someone else wants it or it's gonna take you 20 years before you scale.”
Lemieux: Leaders must benchmark externally to maintain high team performance
“So I think a really good tool for, I think leaders is build a pace bunny process of some sort where you can talk to enough people where you build kind of an internal model of what great looks like.”
Stebbings: Equals raised its seed round at a $30M-$35M valuation
“I think I saw that first round, but it was at some egregious price cause they're out of intercom. And I mean, they're obviously very talented people, but it was like a 30 or a thirty five million start.”
Lemieux: Co-founders for new startup venture are YouTube celebrities
“My co-founders are YouTube celebrities. So I'm like, okay, I've got that. I've got that part nailed so I can go to market quickly.”
Lemieux: Wait until systems break before adding team headcount
“I always wait till things break a couple of times before I add people.”
Lemieux: New hires should start their first month in customer support
“I turned out to be an expert user of Shopify and I would recommend that everyone starting a new jobs would literally start on the phones.”