Every CEO who's managing a remote team has heard some version of this: "But how do you maintain culture without being in person?" It's usually framed as a concern, sometimes as a gotcha, occasionally as a genuine question from someone figuring out whether to go remote.
The honest answer is: you don't maintain culture. You build it. Culture is not a thing that exists and needs to be preserved — it's a thing that's created by how people behave and what gets rewarded and what kind of stories get told. An office doesn't create culture. It's just one environment where culture happens. Remote teams can have culture. They just have to build it on purpose.
What the office was actually doing
Before going remote, most companies weren't building culture intentionally. Culture was happening as a side effect of proximity. People ate lunch together, bumped into each other in hallways, overheard conversations, absorbed norms by watching how things worked. It felt effortless because it was ambient — culture-building was happening without anyone having to do anything special.
Remote work removes the ambient channel. Now if you want those things to happen, you have to design them in deliberately. That sounds like more work. In some ways it is. But it also means you can be intentional about what kind of culture you're building instead of just inheriting whatever happens when you put a bunch of people in a room together.
Shared context is the foundation
Culture is largely about shared context: shared understanding of what the company is trying to do, shared norms about how people treat each other, shared stories about what's happened and what it means. In an office, that context builds up over time through a thousand small interactions. In a remote team, you have to create explicit containers for it.
One thing we've seen work: a running team "context doc" that's updated when something important happens. A big deal closes, someone adds a paragraph about what went into it. A product bet doesn't pay off, someone writes honestly about what was learned. A new person joins who's changing the shape of the team, someone writes about why that matters. This isn't a company wiki — it's more like a team journal. The kind of thing you'd tell someone who was catching up on what they missed.
Teams that do this consistently say it makes onboarding dramatically better. New people can read two years of context in an afternoon instead of absorbing it by osmosis over six months.
Deliberate social time: the good kind
Every remote team eventually discovers that they need to create social time intentionally, but a lot of teams implement it badly. The weekly "virtual happy hour" that feels mandatory and awkward. The icebreaker questions at the start of every meeting that everyone dreads. The team retreat where you fly twelve people to Denver and fill every hour with planned activities.
What actually works is lower-stakes, more frequent, and genuinely optional. A short async video channel where people share what they're reading or listening to or working on outside of work. A monthly call that has no agenda and is genuinely optional. An annual in-person gathering that has a lot of unstructured time because the structured time is less valuable.
Optional matters. Culture doesn't come from forcing social interaction. It comes from creating conditions where it happens naturally, then staying out of the way.
How values become real in a remote team
Most companies have values written on a website or a slide deck. They're usually aspirational to the point of uselessness: "Be bold." "Embrace learning." "Treat people well." In an office, values get operationalized through visible behavior — you watch how a senior person handles a difficult situation and you absorb the actual value system, not the words on the wall.
In a remote team, that transmission has to be more explicit. When a manager makes a decision that reflects a company value, they should say so. "We're taking the longer path on this one because we said we'd prioritize quality over speed, and I want to be consistent about that." When a decision goes against a stated value, acknowledge it: "We said X but we did Y, and here's why, and here's whether that's a one-time exception or a signal that our values need to change."
This kind of transparency feels uncomfortable for leaders who are used to authority being quiet and implicit. In a remote team, it's how norms spread.
Conflict and culture
Culture is also tested by conflict, and remote teams handle conflict differently than in-person teams. In an office, tension between two people can be resolved through a hallway conversation, a shared lunch, a tone of voice that doesn't come through in text. In a remote team, unresolved conflict tends to fester in the passive register of slow responses and avoided threads.
The teams with the healthiest remote cultures tend to have one thing in common: a norm around named conflict. When something's wrong, someone says it directly, by name, to the right person, with a request for resolution. The company's values explicitly support this. Leaders model it. It's the opposite of the remote team default, which is to let things drift and hope they resolve themselves.
It doesn't happen by accident
The teams that say remote work killed their culture usually had a culture that was held together by an office building. Remove the building and there was nothing structural underneath. The teams that thrive remotely had to decide what they actually believed and build systems to make those beliefs visible and consistent.
That's harder than having a ping-pong table. It's also more durable.