Remote First

The episode surfaces a few operational details worth noting - the 24-hour async resolution window before escalating to a meeting, the squad-leader empowerment model, and the internal 'have we gone too far' recalibration at Doist - but the bulk of the runtime is conversational filler, mutual validation, and restatement of basic async definitions that any remotework-adjacent reader would already know.

“if we can't come to a solution within 24 hours, then let's create a meeting and try to tackle it that way”

“seeking perfection in an asynchronous environment, I think can be really dangerous. Like, you almost never really arrive at perfection. And so if you get to 80 or 90%, like you ship it”

The async-vs-sync debate and 'async-first, sync as backup' framing are thoroughly recycled concepts; there is one mildly interesting admission that Doist internally questioned whether it had overindexed on async, but this thread is never developed into a genuinely counterintuitive argument or framework.

“have we gone off the deep end? Have we gone too far with this async thing?”

“I think we even had like a couple, maybe a year or two years ago, we had like a mentality, uh, shift internally”

Chase Warrington is a genuine practitioner who has operated inside a well-known async-first company (Doist) at 100+ employees for years, which gives his comments operational credibility; however, his role and seniority are never clearly stated, and the insights he delivers don't fully demonstrate depth commensurate with someone who has solved these problems at meaningful scale.

“I've always worked remotely but so for the last, what, 12 years I've worked remotely”

“we have this project management system we call the DO system and every month we're working in four week sprints”

There are some concrete operational details - Todoist and Twist as the tool stack, four-week sprints, squad-leader accountability, Dropbox Paper postmortems, and an anecdote about a 150-person company enforcing three-hour timezone overlaps - but no hard metrics, outcome data, or before/after figures are provided to substantiate any of the claims.

“I met this CEO recently who's got like a team of about 150 distributed around the world and he says they make their teams work with a three hour overlap”

“the squad leader will write a spec postmortem spec just to kind of say like here are the outcomes. Usually that's done in like a Dropbox paper or Google Doc”

The host occasionally pushes back with genuine friction - questioning the productivity of a 15-person call and raising the non-English-speaker blind spot - but questions are frequently vague or self-answering, follow-ups rarely press for data or mechanism, and long stretches devolve into both parties agreeing with each other.

“I'm surprised. Fifteen people on a call to me is not productive”

“You only use written communication because I'm keep hearing that you are, you know, writing a lot. But then because you're hiring in many different countries, not everyone has English as their first language”