Six weeks into lockdown I noticed something. Our standups were efficient. Our code reviews were thorough. Our sprint velocity was steady. And I was pretty sure at least two people on the team were quietly falling apart. Not because the work was hard. Because they hadn't had a genuine human conversation with a colleague in weeks.
What You Need to Know
- Remote work solves the logistics of collaboration but kills the ambient human connection that teams depend on
- Culture doesn't transfer to video calls automatically. It has to be redesigned for the medium.
- Small, deliberate rituals matter more than big gestures
- Watching for withdrawal is a leadership skill that remote work makes essential
The Design Problem
I think about this the way I think about any design problem. You have users (the team) with needs (connection, belonging, psychological safety) using an interface (remote tools) that wasn't designed for those needs. The interface is optimised for task completion. It's terrible for the ambient social layer that makes a group of professionals feel like a team.
In the office, connection happens by accident. You overhear a conversation and join in. You sit next to someone at lunch who you don't normally work with. You notice when someone's having a bad day because you can see their face.
Remote work strips out all the accidental connection. What's left is intentional connection, and most teams aren't building any.
55%
of remote workers reported feeling disconnected from colleagues during NZ lockdown
Source: AUT NZ Work Research Institute, Wellbeing & Remote Work Survey, 2020
What We Tried
The Non-Work Check-In
Every morning, before the standup, we spend five to ten minutes talking about anything that isn't work. What people watched last night. What they cooked. How their kids are handling it. Whether their flatmate is driving them mad.
This felt inefficient at first. It's not. It's the minimum viable version of the hallway conversation, the coffee queue chat, the before-meeting small talk that creates social bonds. Without it, your team becomes a group of contractors who happen to use the same Slack workspace.
Virtual Coffee (Randomised Pairs)
Once a week, we randomly pair two team members for a twenty-minute video call. No agenda. No work topics required. Just two people having a conversation. Some of these are awkward. Most aren't. A few have been genuinely meaningful, connecting people who rarely interact in their normal project work.
You can't design spontaneity. A random pairing with no agenda and no expectation is about as close to a hallway encounter as remote work gets.
Rainui Teihotua
Chief Creative Officer
Show and Tell (Fridays)
Every Friday, someone shares something. It doesn't have to be work-related. One developer showed us his sourdough starter. Another walked us through a personal coding project. Our project lead shared a te reo Māori lesson she'd been doing online.
The point isn't the content. It's the vulnerability of sharing something personal with colleagues. That vulnerability builds trust faster than any team-building exercise I've encountered.
The Camera Convention
We settled on a rule: cameras on for meetings, cameras optional for focus work calls. The distinction matters. Meetings are social. You need faces. But when two developers are pairing on a bug, forcing cameras adds nothing except self-consciousness.
What I'm Watching For
The Quiet Withdrawal
The biggest risk in remote teams isn't conflict. It's withdrawal. Someone who stops contributing in discussions. Someone who turns their camera off more often. Someone whose Slack messages get shorter and less frequent.
In an office, you'd notice. You'd see the body language. You'd catch them staring at their screen with that specific kind of blankness that means they're not thinking about code. Remote makes withdrawal invisible until it's serious.
I've started paying attention to participation patterns the way I pay attention to design patterns. Who spoke in the meeting? Who didn't? Has someone gone quiet who's normally engaged? These signals aren't metrics. They're design cues for the team experience.
The Overwork Trap
Some people respond to isolation by overworking. They fill the loneliness with tasks. They stay online late because there's nothing else to do and working feels productive. From a delivery perspective, this looks great. High output. Always available.
It's not great. It's someone substituting work for human connection, and it's unsustainable. When we see someone consistently online past hours, the response isn't praise. It's a conversation. Usually that conversation reveals something worth knowing.
Design Principles for Remote Culture
After six weeks, I've landed on a few principles that feel right:
Make the implicit explicit. Everything that happened naturally in the office needs a deliberate mechanism remotely. Connection, mentoring, feedback, recognition, none of it happens by default anymore.
Design for the introverts. Not everyone thrives in video calls. Some people connect better through writing, through shared documents, through async collaboration. A remote culture that only values speaking up in meetings will lose its quieter contributors.
Rituals beat events. A weekly random coffee pairing builds more connection than a monthly virtual quiz night. Frequency and consistency matter more than novelty.
Watch for silence. In a remote team, silence isn't golden. It's a warning sign. Someone who goes quiet needs a check-in, not space.
We're learning this as we go. I don't think anyone has it figured out. But treating team experience as a design problem, with the same rigour we apply to user experience, feels like the right frame.