In a physical office, culture speaks before anyone does.
You walk into a building and immediately sense something. The lobby might be stark and quiet. Or warm and bustling. There may be closed doors along a hallway, or long tables meant for shared work. You can feel whether the space expects focus, debate, collaboration, or deference.
Those environmental cues are subtle, but they matter. They shape how we show up. They tell us what kind of behavior is normal or expected here.
In remote and hybrid teams, that lobby does not exist.
There are no spatial clues. No architectural boundaries. No way to sense whether interruption is welcome or discouraged, whether decisions are centralized or shared. There is only a screen, and what we choose to put on it.
And that absence changes how culture forms.
When we only worked together physically, new employees absorbed norms almost without realizing it. They noticed how quickly people responded. They watched how conflict unfolded. They saw which metrics were celebrated and which were quietly ignored. Even something as simple as what tchotchkes (if any!) are displayed on desks speaks to the culture of an organization. The environment carried context.
Now, without that shared space, people infer. They interpret tone from Slack messages. They guess at urgency. They build their own models of how things work.
Guessing works for a while. Until it doesn’t.
In distributed product teams, misalignment rarely begins with disagreement. It begins with invisible assumptions. This is why remote leadership requires something different. Not more rules. Not more documentation. But more clarity around the invisible parts of how we operate.
One of the most important shifts I’ve noticed in virtual teams is the need to make the implicit explicit.
How quickly do we expect a response? (And is that response and answer, or just a thumbs-up-emoji to acknowledge receipt?)
What does “ready” actually mean? How do we orchestrate those hand-offs?
When is debate open, and when is a decision closed?
What tradeoffs are we comfortable making?
What does good work feel like here?
In co-located teams, many of these norms emerge through observation. In distributed teams, they need articulation. Priya Parker writes in The Art of Gathering that the more diverse a group is, the more explicit its norms must become. In homogenous spaces, people operate from similar assumptions. In diverse spaces, clarity is what can create safety.
Remote product teams are inherently diverse. Different time zones. Different communication styles. Different experiences of hierarchy and speed. Without shared agreements, even well-intentioned teams can begin pulling in slightly different directions.
This isn’t about control. It’s about reducing friction.
When expectations are invisible, cognitive load increases. Engineers try to decode urgency instead of building. Designers second-guess feedback tone. Product managers spend energy reconciling interpretations instead of facilitating decisions.
Clarity frees attention. I’ve written before that culture is not the icing on the cake. It’s how the cake is made. In virtual teams, that recipe doesn’t sit on the counter where everyone can see it. It lives in documents, in habits, in the way leaders model tradeoffs. And in the absence of physical cues, leadership presence becomes architectural.
You can often feel when a team has left too much unsaid. Meetings drift. Decisions resurface. Quality bars shift quietly. The friction isn’t dramatic. It’s ambient.
That’s usually a sign that something assumed has never been articulated.
It can be helpful to pause and imagine your remote team as a physical building. What would the lobby feel like? Quiet and focused? Energetic and conversational? Would there be signs explaining how things work, or would everything rely on institutional memory? Would a new person know where to go, or would they hover at the entrance? Would a passerby helpfully answer a question or ignore your presence? That image can surface surprising truths.
Then consider what in your current culture still lives only in people’s heads. What expectations have never been written down? What definitions of “good” differ slightly across functions? What behaviors are rewarded, even if they’re not named?
You don’t need a manifesto. You don’t need a reorg. You might simply need a shared conversation that brings those invisible agreements into view.
Remote work did not remove culture. It removed the physical architecture that once helped carry it.
In that empty lobby, teams have a choice. We can allow norms to form through assumption. Or we can design them intentionally, in language that reflects who we want to be.
The lobby may be virtual.
But it still sets the tone.