← All Questions
Culture
4 guests 6 episodes 2,285 words

The Office Is a Tool, Not a Religion: What Actually Works for High-Performing Teams

Should companies be remote-first, in-office, or hybrid?

Shopify has 10,000+ fully remote employees and limits ICs to three hours of meetings per week. Automattic has operated with 1,700 people across 90 countries for 19 years. Meanwhile, the back-to-office narrative has every CEO from Jamie Dimon to Elon Musk insisting physical presence is non-negotiable. Who's right?

The work location debate has become the most ideologically charged topic in tech, with partisans on both sides cherry-picking evidence to confirm their priors. Remote advocates point to flexibility and global talent pools. Office advocates point to serendipity and culture. What neither side acknowledges is that the answer depends less on the location and more on the systems you build around it.

Is remote, hybrid, or in-office work best for building high-performing product teams? And what practices make each model succeed or fail?

The 4 Positions

1 / 4
01

Fully Remote Works at Scale -- With Intentional Intensity Systems

Farhan Thawar (VP and Head of Engineering · Shopify)

Advocates: Farhan Thawar (VP and Head of Engineering, Shopify)

Farhan Thawar oversees engineering for 10,000+ fully remote employees at Shopify, previously ran the largest pair programming shop in the world at Xtreme Labs/Pivotal, and has worked directly with billionaire founders across three decades of his career. His central argument is that remote work does not inherently reduce productivity -- what matters is intensity per unit of time, not the physical location of work.

"Everyone says, 'Oh yeah, work hard and do more hours when you're young, whatever.' I'm like, 'What if you just did more per minute?'"

Farhan Thawar
▶ 00:00:24

This intensity philosophy translates into concrete practices at Shopify. Individual contributors average only three hours of meetings per week, while managers hover around six to seven hours -- numbers that are remarkably low for a company of Shopify's scale.

"We're at something like three hours of meetings per week for an individual contributor at Shopify, which is phenomenal. Three hours a week is amazing. I think managers is not that bad. I think it's six or seven hours per week."

Farhan Thawar
▶ 00:39:12

This meeting discipline is not accidental. It stems from a culture of constant deletion. Shopify has a Delete Code Club that regularly finds over a million lines of code to remove, and this same deletion mindset extends to meetings, processes, and unnecessary overhead.

"We have a Delete Code Club. We can always almost find a million-plus lines of code to delete, which is insane."

Farhan Thawar
▶ 00:00:37

Pair programming serves as the primary intensity mechanism. Thawar calls it the most underutilized management tool in engineering. Two engineers work on one computer, and the throughput limiter is not hands-on-keyboard but rather finding the elegant solution. Tobi Lutke and the CTO would pair program with a one-hour timer, deleting all code and keeping only tests if they did not finish -- reasoning that the inability to articulate a solution in one hour signaled the wrong design.

"Pair programming is the most underutilized management tool in engineering, bar none."

Farhan Thawar
▶ 00:22:30

The six-week review cycle creates additional intensity through Parkinson's Law at scale: every team walks through their roadmap, resourcing, and progress with leadership and Tobi himself. The GSD (Get Shit Done) tool requires weekly company-wide updates, creating a natural cadence of accountability that replaces hallway check-ins.

When This Applies

  • works at Shopify (10,000+ employees), Automattic (1,700 across 90 countries), and companies where deep focus work dominates the week, where you are competing for talent globally, or where you have strong writing practices and asynchronous communication norms. Requires: meeting discipline, documentation culture, explicit alignment rituals, and pair programming or similar collaboration mechanisms.
02

Distributed Teams Need Explicit Alignment Rituals and Periodic In-Person Gatherings

Nikita Miller (SVP and Head of Product · The Knot Worldwide)

Advocates: Nikita Miller (SVP and Head of Product, The Knot Worldwide)

Nikita Miller has worked exclusively with remote and distributed teams across her entire career spanning Shanghai, Europe, Latin America, and five years leading growth and retention at Trello/Atlassian -- products specifically built to enable distributed collaboration. Her perspective is distinctly pragmatic: remote work is not inherently better or worse, but it demands different muscles than co-located work.

Her first principle is documentation as a deliberate practice.

"Documentation. It's a thing. Asynchronous communication, everyone just has to get used to it and better at it, so increasingly just being better communicators, whether it's on a video or written."

Nikita Miller
▶ 00:43:23

Her second principle addresses a specific failure mode she has observed in post-COVID teams: many distributed employees have never met their coworkers, never onboarded in person, and rarely have offsites. This creates a trust deficit that shows up precisely when it matters most -- during hard strategic debates.

"Solving a hard problem remotely with folks that you haven't spent in-person time with, that you haven't broken bread with, that you haven't disagreed with in person and built that trust is just really hard. In fact, it's much harder."

Nikita Miller
▶ 00:44:43

When The Knot Worldwide faces a particularly gnarly strategic problem -- such as a change in strategy requiring major build decisions -- Miller waves the flag and brings the team together for 48 hours with a tight pre-set agenda. In one such offsite, the unlock was simply giving the data person the floor to educate everyone, resolving misalignment that had festered for weeks over asynchronous documents and comments. At Trello and Atlassian, her team established mandatory overlapping work hours while preserving flexibility -- a practice she calls one of the most impactful for distributed teams. She also advocates strongly for in-person onboarding of at least one week, noting that so much of her own early career learning happened in person and she has "no idea how we're going to replicate that in a non-office setting." Her cross-functional triad model (PM, engineering manager, data scientist, designer) with explicitly mapped shared responsibilities becomes even more critical in distributed settings where role ambiguity festers without the natural clarification that comes from proximity.

When This Applies

  • works at The Knot Worldwide, Trello/Atlassian, and companies where teams span multiple time zones but face occasional hard strategic problems that benefit from in-person resolution. Requires: budget for periodic offsites, mandatory overlapping work hours, in-person onboarding (at least one week), and explicit cross-functional role definitions.
03

Remote-First Creates a Writing Culture That Compounds

Brandon Chu (VP of Product · Shopify)

Advocates: Brandon Chu (VP of Product, Shopify)

Brandon Chu is a seven-year Shopify veteran who joined at IPO, a widely recognized product management writer whose Medium posts shaped industry thinking, and leads product acceleration including Shopify's investment portfolio. His core argument is that being remote from founding creates a fundamentally different organizational DNA than companies that transitioned to remote during COVID.

"When I joined, all project management was just in GitHub, just commenting on pull requests and even marketers in order to augment or upload a blog post, you'd have to commit and deploy it. So there was no breaks given for folks that didn't want to touch code."

Brandon Chu
▶ 00:09:20

This technical foundation made writing and asynchronous communication natural rather than bolted-on. Writing forces clarity of thought in ways verbal communication does not. In a remote-first culture, ideas must stand on their written merits rather than winning through charisma, proximity to decision-makers, or the social dynamics of conference rooms.

"We don't actually put the product org on a pedestal as the only people that can have an opinion about the product or should be listened to when we think about what should be built. There's sort of an understanding at Shopify that everyone at the company from engineers to support, to sales, everyone's responsible for product thinking."

Brandon Chu
▶ 00:09:59

Shopify's egalitarian approach works in remote because written proposals create a level playing field -- a support agent's written insight about merchant pain can carry as much weight as a VP's if the reasoning is sound. Chu also highlights that 30-40% of Shopify's PM team are ex-founders (through failed startups or acquisitions), which brings versatility, grit, and entrepreneurial empathy that is especially valuable in remote settings where self-direction is essential. His own career trajectory from bootstrapped startup founder to VP was accelerated by his writing, demonstrating that remote-first cultures reward communication skill as much as any other competency.

When This Applies

  • when your team is in the exploration phase of a new product (high ambiguity, rapid iteration), when mentoring junior team members is a priority, or when the work requires high-bandwidth real-time collaboration (hardware, physical design, high-stakes creative work). Requires: genuine collaboration spaces, not just rows of desks where people Zoom from the office.
04

Fully Distributed With Radical Delegation and Clear Authority

Matt Mullenweg (CEO and Founder · Automattic)

Advocates: Matt Mullenweg (CEO and Founder, Automattic)

Matt Mullenweg has operated a 1,700-person fully distributed company across 90 countries for 19 years -- the longest-running large-scale experiment in remote work in tech -- while growing WordPress to power 40%+ of all websites, 10x the next competitor (Shopify at approximately 4%).

"That's now grown to be over 1,700 people in actually 90 countries so we've actually been fully distributed and remote and asynchronous from the start, which I think is one of our superpowers."

Matt Mullenweg
▶ 00:07:04

His key insight is counterintuitive: distributed work requires more explicit power structures, not fewer. WordPress is maintained by hundreds of daily volunteers and contributors making autonomous decisions, but there is ultimately a hierarchy.

"There has been a radical delegation. However, there's ultimately a hierarchy, and I'm the CEO, so I'm like the final final decision-maker."

Matt Mullenweg
▶ 01:02:24

Mullenweg points to the Gutenberg block editor as evidence that this structure works. Had the community voted on whether to build Gutenberg, the majority would have opposed it. But a small group of core contributors made the conviction call that it was the future, knowing it would be painful for the first three or four years. After 200+ releases on a strict biweekly schedule, Gutenberg now underpins WordPress's continued relevance. The distributed structure works because asynchronous-by-default eliminates the awkward hybrid-ness that plagues companies where some people dial in remotely to meetings designed for in-person attendees. When everyone is remote, the playing field is level.

"Is great software ever created by committee or does it more often reflect a vision of a leader?"

Matt Mullenweg
▶ 01:02:24

Marc Andreessen initially challenged Mullenweg on this exact point during an early fundraise, grilling him for an hour on how distributed work could never build a great company. He invested the next day -- battle-testing the idea was his evaluation method.

When This Applies

  • when different work modes dominate different phases of your project cycle -- in-person for kick-offs, brainstorms, and reviews; remote for execution. Requires: being intentional about what in-person time is for, not just mandating days in the office.

Evidence from the Archive

Shopify

Shopify's GSD (Get Shit Done) tool requires weekly company-wide updates creating Parkinson's Law at scale

Shopify's Delete Code Club regularly finds 1M+ lines to remove, extending the deletion mindset to meetings and processes

Farhan Thawar · VP and Head of Engineering ▶ 00:39:12
The Knot Worldwide

At The Knot Worldwide, Nikita convened a 48-hour offsite to resolve a strategic direction debate that had stalled...

At Trello/Atlassian, the team established mandatory overlapping work hours while preserving flexibility -- a practice Nikita calls one of the most impactful for distributed teams

Nikita Miller · SVP and Head of Product ▶ Watch
Shopify

Shopify's early culture required even marketers to commit and deploy blog posts through GitHub -- no exceptions for...

Shopify's early culture required even marketers to commit and deploy blog posts through GitHub -- no exceptions for non-technical roles

Brandon Chu · VP of Product ▶ Watch
Automattic

Automattic operates across 90 countries with 1,700 employees, making it one of the largest and longest-running...

Automattic operates across 90 countries with 1,700 employees, making it one of the largest and longest-running distributed companies in tech history

Matt Mullenweg · CEO and Founder ▶ 01:02:24

The Synthesis

The remote-vs-office debate is a proxy for a deeper question: does your team's success depend on synchronous serendipity or asynchronous clarity?

The debate is a proxy for: does your team's success depend on synchronous serendipity or asynchronous clarity? Some work genuinely benefits from co-located collision of ideas. But most work -- the 80% spent writing code, crafting strategies, analyzing data -- benefits from uninterrupted focus, not co-location.

Stop asking 'remote or office?' and start asking 'what practices make our team effective, and which location best supports those practices?' The real problem is usually too many meetings destroying deep work, not people being in the wrong room.

Survey data shows hybrid workers are the happiest, remote workers are doing well, and in-office workers have hidden frustrations that challenge the back-to-office narrative. The data does not support the claim that office work is inherently superior for productivity or satisfaction.

Which Approach Fits You?

Answer 3 questions about your situation. We'll match you to the right approach.

Question 1

What type of work dominates your team's week?

Question 2

Where is your team located?

Question 3

How strong is your team's writing culture?

Notable Absences

The Bottom Line

The practical takeaway: stop asking "remote or office?" and start asking "what practices make our team effective, and which location best supports those practices?" Shopify's three-hour-meeting cap works because it addresses the real problem (too many meetings destroy deep work) rather than the proxy problem (people are not in the same room).

The non-obvious insight from Lenny's newsletter survey data: hybrid workers are the happiest, remote workers are doing well, and in-office workers have hidden frustrations that challenge the back-to-office narrative. The data does not support the claim that office work is inherently superior for productivity or satisfaction.

Sources

  1. Farhan Thawar — "How Shopify builds a high-intensity culture | Farhan Thawar (VP and Head of Eng)" — Lenny's Podcast, December 19, 2024
  2. Nikita Miller — "Driving alignment and urgency within teams, work-life balance, and the changing PM landscape | Nikita Miller (The Knot, Trello)" — Lenny's Podcast, April 6, 2023
  3. Brandon Chu — "Brandon Chu on building product at Shopify, how writing changed the trajectory of his career, the habits that make you a great PM, pros and cons of being a platform PM, how Shopify got through Covid" — Lenny's Podcast, June 27, 2022
  4. Matt Mullenweg — "The creator of WordPress opens up about becoming an internet villain, why he’s taking a stand, and the future of open source | Matt Mullenweg (founder and CEO, Automattic)" — Lenny's Podcast, March 2, 2025

Search the Atlas

Guests, questions, and picks

Loading search…
↑↓ navigate←→ filter↵ openesc close