Building a 1:1 culture in a distributed team

The in-person 1:1 has a particular texture. Silences aren't uncomfortable. You read body language. The conversation sometimes spills into the hallway afterward. In remote, all of that disappears. It's not better or worse — it's different. And if you apply exactly the same practices as in-person, you miss what makes the distributed 1:1 effective.

The specific challenges of remote

The first challenge is the absence of the informal. In the office, you have dozens of micro-interactions per week that build the relationship without conscious effort: morning coffee, hallway chats, shared lunch. In remote, those moments don't exist by default. The 1:1 often becomes the only space for real contact — which puts additional weight on it.

The second challenge is reading context. In person, you can sense when someone is off before they've said anything. In remote, you work with fewer sensory cues. An engineer can be exhausted, stressed, or going through something difficult — and you won't see it if you don't create the space for it to be said.

The third challenge is asynchrony. In a team distributed across time zones, work rhythms differ. Commitments made in 1:1s can get lost in the flow of a week where nobody is ever available at the same time.

Format and frequency

The ideal frequency of remote 1:1s is slightly higher than in-person — not because people need more managing, but because the informal interactions that compensate for a missed 1:1 don't exist. Two weeks without a 1:1 in remote creates a relational void that can easily be interpreted as disinterest.

Duration can be shorter. 30 minutes of real conversation in remote is often worth more than an hour that drifts because both participants are tired of looking at each other on a screen. Better dense, well-prepared sessions than long, shallow ones.

On video: the camera should be the norm, not the exception. Not to monitor — to recreate the human dimension that remote erases. A camera-off conversation is functional. A both-cameras-on conversation is relational.

Concrete adjustments

Start with non-work news

In person, the first minutes of a 1:1 often involve talking about something else — a game, the weekend, something personal. In remote, those few minutes are even more important. They signal that the space is human, not functional. Don't cut them in the name of a tight agenda.

Ask about the experience, not the tasks

"How are you experiencing the sprint right now?" rather than "have you made progress on the feature?" In remote, the risk is defaulting to status meetings. The experience question opens conversation about what the person is actually feeling, not just what they're delivering.

Document systematically

In remote, what isn't written disappears even faster than in the office. Commitments made in 1:1s must be captured during or right after the meeting. A short summary message at the end ("just to note, we decided X, I'll look into Y by Friday") creates continuity that compensates for the absence of informal reminders.

Alternate formats

Some 1:1s work better while walking — an audio-only walking meeting changes the dynamic and loosens conversation. Others work better with a shared doc open to co-build something in real time. Don't confine yourself to the "two faces on Zoom" format — explore what works for each relationship.

Building trust at a distance

Remote trust is built on consistency even more than in person. Canceling a 1:1 in the office happens and is easily recovered — the hallway fills the void. Canceling a 1:1 in remote often means the only substantial interaction of the week disappears.

The most effective managers in distributed environments share one characteristic: they're predictable. Their 1:1s happen. Their commitments are tracked. Their availability is known. This predictability creates a sense of safety that compensates for much of what remote can't naturally offer.

Predictability also means arriving prepared. When your team members see that you know their recent context even from a distance — that you know what they've been working on, that you remember previous conversations — you send them a strong message: you're present, even when you're not in the same room.

Moston is built for EMs in distributed teams. AI briefs aggregate context regardless of geography, commitments are captured and surface automatically, and the 1:1 history remains accessible whatever the frequency of interactions. Because in a distributed team, managerial memory isn't a luxury — it's the infrastructure of trust.