The Jean-Michel Lemieux Playbook for Speed, Quality, and Waste Elimination

Companies Die from Indigestion, Not Starvation

Jean-Michel Lemieux doesn't believe in the cult of process. After scaling engineering teams at Shopify and Atlassian—two of the world's most successful B2B platforms—he's landed on a heretical position: most companies overplan by 100x. His current startup operates without Scrum, standups, TDDs, or any of the ceremonies that dominate modern software teams. Instead, he measures exactly one thing: what shipped this week.

"Companies are going to die from indigestion before they die of starvation," Lemieux says. "We all have way too many ideas in our brain and our instinct is to give everyone everything and it's really hard to say no." The implication cuts against every growth playbook that prescribes more features, more experiments, more optimization. Lemieux's thesis is simpler: narrow your scope, polish half of what you ship to perfection, and ship the other half fast enough to maintain momentum.

Give people a couple of things that are really, really good and then buy you time to figure out what the next things are.

— Jean-Michel Lemieux

His current experiment is deliberately constrained: build a multimillion-dollar business with the least amount of people possible. That means technical foundations get time—security, payments, architecture—but everything else is subject to weekly time-capping debates. "Either it's shipping this week or we're going to discuss a direction of something that we have to exchange some ideas, but it's time capped," he explains. The culture shock is real. Teams expect politeness, roadmaps, alignment. Lemieux offers none of it. Code talks, bullshit walks.

Shopify Ships on Quality, Atlassian Ships on Speed

The Venn diagram of Shopify and Atlassian overlaps in exactly two places: founders playing the long game and founders who are brilliant at marketing. Both Toby Lütke and Harley Finkelstein at Shopify, and Scott Farquhar and Mike Cannon-Brookes at Atlassian, understood early that you don't build a product—you build a movement. Atlassian rallied around open source and easy software 20 years ago, running campaigns like "cash for clunkers" aimed at Joel Spolsky. Shopify aligned with Tim Ferriss and The 4-Hour Workweek, wrapping itself around the movement of entrepreneurship, not e-commerce software.

Where the diagram diverges is execution philosophy. "Shopify will ship on quality, Atlassian will ship on speed," Lemieux says flatly. Atlassian's product page is a sprawling empire of acquisitions and SKUs. Shopify's is austere by comparison. "At Shopify, we spent a lot more time on doing less things," he notes. Tobi would stop initiatives based on quality alone—a discipline Lemieux saw less frequently at Atlassian, where the priority was monetization velocity and customer pool leverage.

You don't build a product, you build a movement.

— Jean-Michel Lemieux

The trade-offs are real. Lemieux believes Shopify could be 10x its current revenue if it had adopted Atlassian's aggressive pricing optimization and product expansion playbook. "Shopify could be 10x the revenue if you look at how much value is being provided," he argues. But that extractive posture might have broken the movement. Atlassian, conversely, was "a crazy good business"—Scott Farquhar had spreadsheets in 2010 projecting what 2020 would look like, and they nailed it. Shopify raised Plus pricing only recently, leaving years of revenue on the table in service of long-term product love.

Both companies succeeded wildly, but Lemieux's takeaway is that the first 10 years should prioritize one metric above all: do people love your product enough to tell their friends about it? Monetization levers can wait. If you spend too much time in the spreadsheets, you forget priority number one.

Time Horizon Friction Is Killing Your Velocity

Lemieux has identified a pathology he calls "time horizon friction." It's the organizational drag caused when different people or teams operate on incompatible planning cycles—some optimizing for quarterly OKRs, others for weekly sprints, still others for multi-year roadmaps. The result is endless process designed to reconcile those horizons: planning meetings, alignment docs, story points, retrospectives. All of it is waste.

"I believe that one of the things that slows teams down the most is what I call time horizon friction," he explains. "Time horizon friction is caused by a lot of process, and that process is you have a lot of people who want to put plans in place and they feel comfort." The antidote is radical simplification. At his current startup, the only valid time horizons are "this week" and "directional future." If it's not shipping this week, the team discusses direction briefly and moves on. No grooming, no estimation, no ceremonies.

Code talks and bullshit walks, which is I see what we're shipping. Is it good?

— Jean-Michel Lemieux

This approach has been "culturally jarring" for his team, Lemieux admits. Engineers and PMs are conditioned to be polite, to accommodate every stakeholder's timeline, to build consensus. Lemieux refuses. "I just don't want to talk about that much. That doesn't matter. And no one does that. Everyone's way too polite." His measure of progress is visceral: he looks at the pull requests, the code shipped, the weekly hum of output. Not lines of code—there's magic in one line sometimes—but the consistent cadence of meaningful work hitting production.

Do Something You're Good At, Not Something You Love

Lemieux fell into technology sideways. He was a fine arts and music student in high school in 1988, oscillating between drawing, painting, band class, and math. When his parents bought him a computer, he discovered MIDI and convinced his band teacher to let him replace the entire high school band for a Les Misérables and Phantom of the Opera medley. He recorded multiple tracks, played one live, and pulled it off. His guidance counselor nudged him toward computer science. He resisted—he knew no one who did it for a career—but she was right.

"People always say, do something you love. And I'm like, do something you're good at," Lemieux says now. "There's kind of no wrong path if you keep doing something you're good at." He's never seen computers as an end in themselves. They're a tool, a copilot for creativity. That instrumental mindset—computers exist to make cool shit happen—has defined his entire career. From band class to CTO of Shopify, the throughline is pragmatism: find what works, eliminate what doesn't, ship relentlessly.

I've always seen computers as a tool. Computer is like a companion, a copilot for creativity. I was not like a programmer. I was like, a computer is like a tool that can make really cool shit happen.

— Jean-Michel Lemieux

His advice to graduates entering the workforce echoes that philosophy: the safe path is never as safe as you think, and the risky path is never as risky as you think. Competence compounds. If you're good at something, lean in. The movement will find you, or you'll build it yourself. Just don't waste time on process you don't need, plans you won't execute, or roadmaps designed to make people comfortable. Ship half your work polished to perfection, ship the other half fast, and let the code do the talking.