Latest / The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org / How GitLab Runs Engineering Async
Transcript
- Lucas: GitLab runs one of the most extreme remote engineering orgs in the world. Not just remote-first — fully asynchronous, no fixed hours, no video-call standups. And they've been doing it since 2011, way before the pandemic made it normal. Luna: I've read their handbook. It's like 3,000 pages. But the part I find fascinating is how they make decisions without anyone being in the same room — or time zone. Lucas: That's the core challenge. The entire operating system is built on written documentation. Every decision, every rationale, every technical spec — it goes into a merge request. The discussion happens in comments. And the default is, you write it down before you speak it. Luna: That feels like it would slow things down. I mean, typing a proposal takes longer than just saying it in a meeting. Lucas: It does take longer upfront. But GitLab's argument is that it scales better. If you record a meeting, no one watches the recording. If you write a decision down, it becomes part of the permanent record — searchable, linkable, reviewable by anyone in any time zone. And it forces clarity. You can't hand-wave in a written document the way you can in a hallway conversation. Luna: So what replaces the daily standup? That's usually the first ritual companies try to replicate remotely. Lucas: They don't have one. Instead, they have an 'async standup' — a written update in a shared document or issue tracker. Everyone posts what they worked on, what's blocked, what's next. And you read it when you start your day. It's not synchronous. You don't all show up at 9 a.m. Pacific. Luna: But don't you lose the serendipity? The quick 'hey, can you look at this' that happens when you're side by side? Lucas: Absolutely you lose that. GitLab acknowledges it. Their fix is that every conversation should happen in a public issue or merge request — so it's visible to everyone. If you need a quick sync, you can schedule a video call, but the default is text. And the call gets summarized back into the issue. Nothing is allowed to live only in a meeting. Luna: That's a hard discipline to enforce. What happens when someone just jumps on a Zoom without documenting? Lucas: It's culturally discouraged. The handbook literally says 'if it's not in the handbook, it doesn't exist.' That's a phrase you hear inside GitLab. And it's taken seriously. When they were preparing for their IPO, they had to write down processes that had been implicit for years — because the SEC requires documented controls. And GitLab actually found that the async discipline helped, because they already had a written record of how engineering decisions were made. Luna: That's a good point. Most companies scramble to document controls before an IPO. GitLab already had them. Lucas: Exactly. Their S-1 filing actually highlighted their 'handbook-first' culture as a strength. And if you look at how they maintained velocity while scaling from 100 to nearly 2,000 employees, the async documentation is a big part of it. New hires don't need to shadow someone for weeks — they read the handbook and the relevant issue threads. Luna: But doesn't that onboarding feel isolating? Reading a handbook instead of talking to people? Lucas: It can. GitLab addresses that with 'social calls' — optional, no agenda, just hang out. But yeah, isolation is a real risk. The trade-off is autonomy. You can work when you're most productive, and you don't have to align your schedule with 15 other people to get information. The blocker is rarely 'I need to wait for someone to wake up.' Luna: So how do they measure productivity? Without hours tracked or standups, how does a manager know work is getting done? Lucas: They look at merge request cycle time, issue velocity, and contribution volume. But the bigger cultural signal is that everyone is expected to communicate progress in writing. If you're not updating your issues, that's visible. And because everything is in the open, managers can look at the board and see what's moving. It's not perfect — there's still a risk of people gaming metrics — but it's more transparent than most orgs. Luna: I've heard critics say that async favors native English speakers and penalizes non-native speakers who take longer to write. Is that fair? Lucas: It's a real concern. GitLab has tried to mitigate it by encouraging clarity over speed, and by having a 'no blame' culture around editing. But the reality is, if your communication is primarily written, people who write more fluently have an advantage. GitLab's own research shows that async can be a barrier for some groups. They've made changes — like allowing video recordings as an alternative to written updates — but it's an open problem. Luna: Let's talk about something I think about a lot: we deliberately don't run ads on this show. It's a choice that keeps the conversation clean. If you find episodes like this valuable for what you're building, and you want to support that choice, the link is buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a simple thing. No sponsors, no product pitches. Just the conversation. And listener support is what keeps it that way. Luna: So back to GitLab — what's one thing a traditional engineering org could borrow from them without going fully async? Lucas: The merge request culture. Even if you have standups and meetings, you can adopt the discipline of writing down the decision and the rationale before you start coding. It doesn't have to be long — a paragraph about why you're making a change, what alternatives you considered. That alone saves enormous rework. Luna: And it creates an audit trail. Six months later, someone can look at the MR and understand why that function exists. Lucas: Exactly. That's the hidden ROI. GitLab's system isn't just about remote work — it's about building an institutional memory that doesn't walk out the door when people leave. And for a CTO, that's the real win. Luna: Yeah, I think that's the takeaway. You don't have to be all-in on async, but the documentation discipline is worth stealing. Lucas: And it's free. It's just a habit. But it takes leadership to enforce it. If the CTO writes the first comment in a merge request that says 'what's the rationale here?', the team gets the message.