Remote Work Culture: What 8 Years of Running a Distributed Team Taught Me

Ask ten companies how they build remote work culture and you’ll hear the same playbook: virtual happy hours, online trivia, a Slack channel full of GIFs, a bot that pairs people up for coffee chats on Friday afternoons.

I’ve run a fully distributed company since 2018. Full Scale has more than 350 people, split between my office in Kansas City and our team in the Philippines, and almost everyone works remotely. So I’ve had eight years to watch what actually holds a remote culture together, and it is none of that. Distance tests more than culture. Keeping a distributed team secure runs on the same trust.

Here is the number that tells the real story. Our developer retention runs about 93 percent, in a country where the business process outsourcing (BPO) industry loses somewhere between 30 and 45 percent of its people every year. That gap is also why Full Scale is Great Place to Work Certified in the Philippines.

The distance between those two numbers is the culture. It shows up as one thing: whether people choose to stay.

I know plenty of companies have given up on this and started dragging everyone back to the office. I think that’s a mistake, and I’m about as biased toward remote as a person can be, so take it for what it’s worth. But most of the culture problems people blame on remote work are really management problems wearing a remote costume. Calling people back to a building doesn’t fix a culture you were never actually running, it just hides the symptom behind a commute.

This post is about the culture itself. If you want the operational playbook for running local and offshore developers as one group, I wrote that separately in managing distributed teams. And if your problem is really about messages getting lost across time zones, remote team communication is its own thing. What I want to talk about here is why people on a remote team feel like they belong, why they stay, and why most of the advice you’re getting about it misses.

Most remote work culture advice is theater

The happy-hour playbook is comforting because it’s easy. You can schedule a virtual game night on a Thursday and check a box that says you worked on culture. The problem is that none of it touches the thing that’s actually broken.

Look at the engagement numbers. Gallup found that global employee engagement fell to 20 percent in 2025, the lowest it’s been since 2020, and that low engagement costs the world economy around $10 trillion a year in lost productivity. A trivia bot does not move that number. People are checked out for reasons that have nothing to do with whether the company throws a good virtual party.

On a remote team, the real culture problem is that the people you can’t see slowly become invisible, and that costs them. An analysis by Live Data Technologies, reported by Bloomberg, found that fully remote workers were promoted 31 percent less often than their in-office and hybrid peers. SHRM surveyed supervisors and found that 67 percent considered remote workers more easily replaceable, and 42 percent admitted they sometimes forget remote workers when handing out assignments.

Read those two findings together. Remote people get passed over for promotions, and the managers above them quietly think of them as expendable. You cannot happy-hour your way out of treating people like they’re disposable.

I’m not saying the game night is worthless. A bit of social time can genuinely help a lonely junior developer feel less alone, and that counts for something. The trouble is that it’s a rounding error next to whether that same person gets promoted, gets heard in a meeting, and gets treated like they matter. The danger is when the trivia bot becomes the thing you do instead of the hard work, a way to feel like you addressed culture without touching any of it.

Culture is how you treat the people you can’t see

Here’s a definition I trust more than any poster on a wall. Your culture is how people get treated when no one is forcing anyone to be nice.

That matters more on a remote team than anywhere else, because so much of the bad treatment isn’t a decision. It’s neglect. When half your team is in the building and half is on a screen, the people in the building get all the hallway conversations, the quick desk-side questions, the context that never makes it into a document. The remote half gets left out, and nobody meant to leave them out. They just weren’t in the room where it happened.

When McKinsey studied why people were quitting, the top reasons weren’t pay. They were not feeling valued by the organization (54 percent), not feeling valued by their manager (52 percent), and not feeling a sense of belonging at work (51 percent). Those are relationship problems, and relationships are exactly what go quiet when you forget about the person on the other end of the screen.

The flip side is just as real. BetterUp’s research found that employees with a strong sense of belonging had a 50 percent lower turnover risk and performed 56 percent better. Belonging does real work for you. It’s what separates a team that ships from a team that’s always rebuilding itself because good people keep leaving.

So the first real culture work is unglamorous. You go out of your way to spend more time with the people you can’t see than feels strictly necessary, because the building isn’t doing it for you. You make sure the remote half hears about the decision, gets the credit, gets the promotion when they earned it. None of that shows up on a calendar invite called “culture.”

Treat the remote half exactly like the local half

The single biggest thing you can do for a distributed culture is refuse to run two teams. A developer in Cebu and a developer in Kansas City should have the same first day, the same code review bar, the same shot at the interesting work, and the same direct line to leadership.

Worth being honest about the obvious objection here. The Cebu developer and the Kansas City developer are not paid the same dollar figure, so how can they be treated the same? The gap comes down to cost of living. A senior salary in the Philippines stretches a lot further there than the same number would in Kansas City, so what looks like a discount is really just two different local markets. Everything else has to be identical: the standards you hold them to, the ownership you hand them, the respect they get in a meeting, and the path in front of them. People can live with earning a market wage for where they live. What kills a culture is being treated like the cheaper, lesser half of the team.

Derrick Leggett, the CIO at AMC Theatres, runs a global engineering org with people in the US, South America, India, and the Philippines, and he describes it in a way I’ve never improved on: “It’s a fully integrated team. It’s just some of the people happen to be living in the Philippines.” That’s the whole mindset in one sentence. There’s no offshore team and onshore team. There’s one team, and they live in different places.

The opposite of that is treating remote developers as cheap, interchangeable bodies you rent by the hour. I call that cheapshoring, and it’s the fastest way to build a culture nobody wants to be part of. If your whole reason for hiring someone is that they were the cheapest option, they can feel it, and they’ll leave the moment something better comes along. People know when they’re being treated like a line item. I cover the practical mechanics of folding the two halves into one group, the shared standups, the single source of truth, the in-house technical leadership, in the guide on running local and offshore developers as one team. The culture point is simpler: developers are not headcount, and the second you treat them like they are, your retention tells on you.

Build culture through real work, not forced fun

If virtual happy hours don’t build culture, what does? Shared work that people are proud of.

One story I tell in my book Product Driven is about Basys, a payments company a few miles from me here in Kansas City. Their technology and product leader, Chris Borchers, changed the whole company’s culture with something that sounds almost boring: weekly live demos where engineers show what they actually built, in front of the whole company. The CEO called it “the best meeting I’ve ever been in.” One time a junior engineer demoed a redesigned claims screen and a support manager blurted out that it was going to cut their support calls in half. That’s culture. Nobody scheduled fun; people just got to see their work land, in front of the people it landed on.

That only works if people feel safe enough to show rough work and to speak up when something’s wrong. I think the three skills that decide whether a software team succeeds are communication, curiosity, and courage, and courage is the one most leaders underrate. Courage is the engineer who says “I don’t understand this ticket” instead of quietly building the wrong thing for two weeks. This matters more as AI takes over the actual typing, because once the mechanical part of the job is automated, what’s left is human judgment, and judgment runs on people feeling safe enough to question things. On a remote team, where it’s easy to go heads-down and hide, you have to build that safety on purpose. A team member who stays silent because they didn’t want to look dumb will cost you far more than the awkwardness of the question ever would.

Protect your people from the always-on trap

Remote work was supposed to give people their time back. For a lot of teams it did the opposite, because the office used to end and the laptop never does.

Microsoft’s 2025 Work Trend Index found that knowledge workers get interrupted by a meeting, email, or message roughly every two minutes, and that 40 percent of people check email before 6 a.m. Buffer’s 2023 State of Remote Work found that loneliness was a top struggle for 23 percent of remote workers, and that 71 percent said setting boundaries was very important to them. The thing that makes remote work feel free is the same thing that quietly eats your evenings, and the difference between the two is whether the company protects the line.

A real remote culture protects people from that, and it has to come from the top, because people copy what their leaders actually do, whatever those leaders say about unplugging. If you fire off messages at 11 p.m. and answer email on vacation, your team learns that’s the expectation, no matter how many times you tell them to unplug. This gets harder across time zones, where it’s tempting to expect the Philippines team to always be available during your hours. The fix is to design the overlap on purpose and protect the rest, which I get into in the piece on time zone differences on a remote team. Watch for the early signs of developer burnout on the people you can’t physically see, because you won’t catch it by walking past their desk.

Measure your culture with the one number that doesn’t lie

You can survey people about culture and they’ll tell you what they think you want to hear. There’s one number they can’t fake, and it’s whether they stay.

That’s why I keep coming back to retention. Full Scale’s developer retention is about 93 percent. We’re Great Place to Work Certified in the Philippines two years running, with 95 percent of our people saying it’s a great place to work, against 65 percent at a typical company there. The fair comparison is US tech, where turnover runs 13 to 15 percent a year, and keeping 93 percent is a different league than that. The Philippine outsourcing industry we sit inside loses 30 to 45 percent of its people a year, which makes the gap look even starker, though call-center churn isn’t a clean comparison to salaried engineers. Either way, the culture is the reason our number looks the way it does.

If your team is small, you can’t run this math, because one person leaving a team of six isn’t a trend, it’s a coin flip. So watch the softer version of the same signal: whether your best people re-up year after year, whether they refer their friends when you’re hiring, and whether they act like owners instead of renters. Those tell you whether the culture is real long before a retention percentage would.

And it pays for itself. Gallup estimates that replacing an employee costs between one-half and two times their annual salary, and that voluntary turnover costs US businesses around $1 trillion a year. Keeping good people is cheaper than constantly finding and training new ones. That math is the entire reason we built our model around retention instead of churn. We put a customer success manager on every account whose job is partly to keep developers engaged and growing, and we invest in training and mentoring, because that’s what makes someone want to stay. If you want the longer version, I’ve written up the specific developer retention strategies that actually hold people. Mentoring is a skill in its own right, and I wrote about what it takes to be a good software engineer mentor on a team you rarely see in person.

The whole thing comes down to one belief I run the company on. Take care of your employees and they take care of your clients. Without employees, you have nothing. That’s true in an office, and it’s truer when your people are scattered across the world and the only thing keeping them is whether the culture is real.