Remote and hybrid teams don’t lose culture when they lose the office. They lose many of the accidental mechanisms that helped culture form: hallway encounters, informal learning, weak ties, shared jokes, spontaneous collaboration, and everyday social connection.
But none of those mechanisms actually require a building.
Drawing on anthropology, engineering leadership, and years of leading distributed teams, this session examines what thriving online communities already know about building culture without physical proximity - and how engineering leaders can intentionally design the digital spaces where trust, identity, learning, and community can grow.
In this session, a software engineering leader with formal training in psychology and anthropology challenges one of the most persistent assumptions about remote work: that meaningful culture requires physical proximity.
The needs behind that assumption are real. Teams need informal interaction, mentorship, shared identity, spontaneous collaboration, belonging, and access to information. But offices satisfy many of those needs accidentally - through hallways, overheard conversations, shared spaces, and proximity.
Remote and hybrid teams have to satisfy them by design.
Using seven common return-to-office arguments as a starting point, this session separates the human need from the physical mechanism traditionally used to meet it. From hallway conversations and brainstorming to onboarding, coordination, and belonging, attendees will explore how distributed teams can intentionally reproduce - and sometimes improve - the functions we once relied on the office to provide.
Then we'll borrow one of anthropology's oldest tools: cross-cultural comparison.
Open source communities and online gaming cultures have built strong distributed identities for decades, often among people who have never met in person. Their success reveals practical lessons about weak ties, shared language, rituals, symbols, informal spaces, and cultural artifacts.
Finally, we'll bring those lessons back to engineering teams through real examples from remote organizations Robert's led: digital watercoolers, team totems, custom dialects and emojis, collaborative art, onboarding artifacts, recognition rituals, and the deliberately designed spaces where culture can take root.
The core idea is simple:
The office gave us cultural infrastructure by accident. Remote teams have to build it on purpose.
Participants will leave with:
• A framework for separating the human needs of a team from the physical mechanisms traditionally used to meet them
• Practical ways to create low-friction digital spaces for spontaneous interaction and weak-tie formation
• Design principles for building shared identity through language, rituals, humor, art, and artifacts
• Concrete examples they can adapt to strengthen culture on remote and hybrid engineering teams
• A new diagnostic question: if the building disappeared tomorrow, what about your culture would still be there next month?
This session is grounded in anthropology, systems thinking, and more than two decades of engineering leadership, and is designed for leaders who want remote and hybrid teams to do more than function - they want them to feel like communities people genuinely want to belong to.
Robert N. Harris is the Founder of Coded2Lead, a coaching practice dedicated to transforming software engineers into emotionally intelligent leaders. A 4x software engineering executive based in Houston, TX, Robert draws on 20+ years of pragmatic leadership experience - alongside a unique academic background in psychology and anthropology - to tackle the toughest problems in technology: the human ones.
His claim to fame is helping small engineering teams punch above their weight. He’s helped companies shrink product cycles from months to weeks, launch new products in months instead of years, and scale revenue by 10x.
He’s mentored tech leads, managers, and founders across industries, blending technical rigor with surreal metaphors, visual storytelling, and deeply empathetic insight. Whether he's refining a brand identity or helping a developer navigate imposter syndrome, Robert’s approach is iterative, creative, and always human-centered.
When he’s not coaching, you’ll find him in the garden, under the stars, or behind the wheel - using race cars, astronomy, and nature as unexpected mirrors for leadership growth. His mission: to help engineers debug themselves, lead with courage, and build systems where people thrive.
If a business is willing to invest in software engineering, he’ll make sure they get the most out of that investment.
More About Robert »