Jean-Michel Lemieux: Three Product Decisions Every Team Needs to Make | E1129

Both Shopify and Atlassian deliberately built communities and narratives—around entrepreneurship and team collaboration—so customers felt part of a movement, which made distribution, word-of-mouth, and long-term loyalty far easier than product alone.

Founders shouldn’t choose speed or quality in aggregate; instead, they should decide which features must be world-class and shareable, and which can be good-enough, recalibrating those buckets monthly to maintain momentum without sacrificing key experiences.

Over-planning drags builders into endless meetings about work months away, creating friction between planners and coders; Lemieux combats this with a clear 3-year vision, one-month planning windows, and a single one-hour weekly team meeting focused on what’s shipping now and next.

He evaluates leaders by asking what their teams shipped and how they rank the work (good vs. great), and in his own work he tracks progress via PRs and code shipped—“code talks and bullshit walks”—rather than story points or process adherence.

True autonomy only works after leaders and new hires have ‘pair-programmed on leadership’—co-shipping a few critical initiatives together, exchanging feedback frequently (often daily via Slack) to build a shared quality bar and decision-making model.