The Data-Backed Benefits of In-Person Development Teams — Open Source CXO Ep. 20 | Active Logic
The remote work debate in software engineering has largely been settled by personal preference rather than evidence. In this episode of Open Source CXO, Geoff Vandegrift, CTO of Ad Astra, takes a different approach — presenting research-backed arguments for why co-located teams tend to outperform remote teams in software development contexts.
This isn’t a blanket condemnation of remote work. It’s a nuanced look at where physical proximity creates advantages that are difficult to replicate through Zoom calls and Slack messages — and what that means for how you structure your engineering organization.
Key Insight: High-Bandwidth Communication
The most compelling argument Geoff makes centers on communication bandwidth. In-person communication carries information that digital channels strip away: body language, tone, facial expressions, spontaneous whiteboard sessions, and the casual hallway conversations that surface problems before they become crises.
Research from MIT’s Human Dynamics Lab has shown that the most successful teams aren’t characterized by individual brilliance — they’re characterized by communication patterns. Specifically: equal participation in conversations, high levels of face-to-face interaction, and frequent short exchanges rather than fewer long meetings.
These patterns are easier to sustain in person. Not impossible remotely — but easier, and more likely to happen organically rather than requiring deliberate orchestration.
Key Insight: Social Cohesion and Trust
Geoff draws on Daniel Coyle’s Culture Code to argue that trust — the foundation of high-performing teams — builds faster and more durably through physical proximity. Shared meals, casual interactions, and the small moments of vulnerability that happen naturally in an office create bonds that remote work struggles to replicate.
For development teams specifically, trust has direct engineering implications. A developer who trusts their reviewer will respond to code review feedback constructively rather than defensively. A team that trusts its architect will align on technical decisions faster. Trust reduces the friction in every engineering interaction.
Key Insight: Organizational Design Matters More Than Location Policy
Drawing from Team Topologies by Matthew Skelton and Manuel Pais, the conversation evolves into a broader discussion of organizational design. Geoff argues that the question isn’t simply “remote vs. in-person” — it’s about how teams are structured, how they communicate, and how work flows between them.
Well-designed team structures can make remote work effective. Poorly designed structures can make even co-located teams dysfunctional. The location policy is one variable among many — and it’s not the most important one.
For organizations evaluating their team structure, the priority should be: define clear team boundaries and ownership, establish communication protocols that work for your model, and then choose the location policy that best supports those structures.
Key Insight: The Kansas City Advantage
Geoff makes a practical case for Kansas City as a development hub — a perspective that resonates with Active Logic’s own experience. The Kansas City metro offers a combination that’s increasingly rare: strong engineering talent, reasonable cost of living, a growing tech community, and a central time zone that enables collaboration with both coasts.
For companies that want the benefits of co-located teams without Silicon Valley costs, secondary tech hubs like Kansas City represent a compelling alternative.
Key Insight: Hybrid Models and Their Challenges
The conversation doesn’t shy away from the complexities of hybrid work — the model that most companies have landed on. Geoff identifies the primary challenge: hybrid creates two classes of employees. The people in the office get the high-bandwidth communication benefits; the remote workers get the flexibility benefits. Neither group gets both.
The practical recommendation: if you’re going hybrid, be intentional about which activities happen in-person versus remote. Use office days for collaboration-heavy work (design sessions, planning, retrospectives, pair programming). Use remote days for focused individual work (deep coding, writing, research).
Recommended Reading
The episode references several books that shaped Geoff’s thinking:
- Culture Code by Daniel Coyle — on building trust and belonging in teams
- Team Topologies by Matthew Skelton and Manuel Pais — on organizational design for software delivery
- Radical Candor by Kim Scott — on direct, caring communication in leadership
- Holacracy by Brian J. Robertson — on self-managed organizational structures
Takeaways
- Communication bandwidth matters for engineering quality. In-person interaction carries information that digital channels don’t.
- Trust builds faster with physical proximity. Shared experiences create bonds that accelerate team performance.
- Organizational design outweighs location policy. Fix your team structure before optimizing your remote work policy.
- Secondary tech hubs offer real advantages. You don’t need Bay Area costs to build a world-class team.
- Hybrid requires intentional design. Don’t let it happen by default — choose which activities benefit from which modality.
