You Don’t Declare a Culture — You Engineer One

A high-performing culture is the output of three things you build: the people on the team, the processes they run, and the systems underneath them. Get those right and the culture follows. Get them wrong and no amount of values-on-the-wall will save you.

The case against remote-first is familiar: culture is fragile, collaboration is dying, innovation needs proximity. They’re not wrong about the symptoms. Teams are disconnected. Early-career engineers are stalling. Decisions are slow. But the diagnosis is wrong. The problem isn’t that people are working from home. It’s that nobody designed the conditions for them to do good work when they got there.

Those conditions don’t require a shared zip code. Talent, focus, leverage. You can build all of it without an office. Often better. Three things make the difference, and you have to get all of them.

1. People. Remote-first raises both the ceiling and the floor of who you hire. But hiring is just the first move. You’ll screen harder for remote-fit, invest more in early-career engineers, and design team identity that an office gives away for free.
2. Process. Focus doesn’t happen by accident. The highest-leverage hours an engineering team has are the concentrated, conceptual ones, and your cadences, rituals, and meeting culture either protect those hours or shred them. The office shreds them by default. Remote-first lets you build the defense in.
3. Systems. Make the right thing the easy thing. Co-located teams can survive on tribal knowledge and hallway conversations for a while. Remote teams can’t. Your paved roads, your scoreboards, your cultural amplifiers carry the weight that proximity used to.

Miss any of these and the whole thing falls apart. Get all three right and you’ve built the intentional engineering culture that scales as you grow.

---

People — Talent Lives Everywhere

Talent is equally distributed. Opportunity is not. — Leila Janah

Your best hire isn’t in the zip code you’re searching. I’ve tried to staff engineering teams in saturated markets like the Bay Area, and the math gets brutal fast. Every strong engineer is already employed, comp is punishing, and the same fifteen candidates are interviewing at the same fifteen companies. Meanwhile, one of the best engineers I ever hired lived in rural Missouri. They would never have shown up in a geographically locked search, and I never would have known what I was missing. Remote-first lets you fish the global pond instead of the thirty-mile one, and the candidate pool grows by roughly an order of magnitude. The practical limit isn’t geography anymore, it’s timezone overlap: flexible hours are a perk, core hours are a requirement. Screening gets harder since you’re now competing globally for the top of every market.

Remote-first isn’t for everyone. Screen for it. At home, every reinforcing alternative to the work is an arm’s length away: phone, family, fridge, the dog. The office creates friction against drifting through social pressure and physical separation; at home there’s none. Some people do their best work in a room with other humans, with the ambient pressure and the hallway conversations. That’s a real preference, not a flaw. Name remote-fit in the job post, ask about it directly in the interview, describe what an average Wednesday actually looks like alone in a home office, and let candidates self-select. Self-selection is the cheapest filter you have, and most companies don’t use it.

Supporting early-career engineers is genuinely harder remote, and it changes how you build the team. In an office, early-career engineers learn by osmosis: overhearing a debate, watching an experienced engineer debug, leaning over to ask the person next to them. Remote kills that channel. Mentorship has to be deliberately scheduled, and each early-career hire costs more experienced-engineer hours than it would in person. In my own experience, supporting one early-career engineer in-office required roughly five experienced engineers around them. Remote, that number doubled to closer to ten. The mechanism is old: Brooks called this out in The Mythical Man-Month (1975). Mentorship is a tax on the people doing it, and remote makes the tax heavier.

Who you ship with matters more than who you sit with. In an office, identity emerges broadly and organically. You belong to your immediate team, but you also bump into other functions, drift into coffee chats with people across the company, and form connections that nobody planned. Remote strips all of that out. You start 100% isolated, and every connection has to be deliberately created. You can’t rebuild everything the office gave you for free, so you have to focus your design energy on what matters most. In our engagement surveys, the context and health of the local team was the single largest driver of employee satisfaction. The team is the atomic unit of organizational performance. Getting it right is the highest-leverage move you have for each team member’s experience.

Process — Focus Doesn’t Happen by Accident

Focus is one of the most endangered mental factors in the modern world. There’s nothing more fatal to an organization’s ability to get things done than a team that can’t focus on its goal. — Flow Engineering: From Value Stream Mapping to Effective Action

The office is the worst place to do deep work. Focus is the asset everything else converts into output, and modern offices are structurally hostile to it. Open floor plans actually reduce face-to-face interaction (Bernstein & Turban, 2018). Claustrophobic phone booths are a draining and demoralizing employee experience. Endless “got a sec?” interruptions destroy concentration. Remote-first flips all of those issues on their heads. You can protect uninterrupted blocks of focus in ways offices structurally can’t. Performance directly increases as a consequence: workers in Bloom’s Ctrip study posted a ~13% performance gain.

Intentional in-person investments pay off. Some work is high-bandwidth by nature, and remote tools don’t replicate it well. Quarterly planning brings the team into alignment on strategy. Team off-sites are concentrated time for design sprints, product discovery, and the kind of work that benefits from a shared whiteboard. Fast, in-the-room ideation is structurally harder over a wire. That’s exactly why you schedule the off-site, not why you mandate the office.

Docs over decks. A written narrative is a concrete artifact: anyone can read it, push back on it, or reference it, regardless of whether they were in the room when it was discussed. Reading is roughly twice as fast as listening anyway. Writing also forces clearer thinking. Bezos’s anti-PowerPoint memo at Amazon argued that “the narrative structure of a good memo forces better thought.” Steve Jobs ran Apple the same way: “I hate the way people use slide presentations instead of thinking.”

Systems — Make the Right Thing the Easy Thing

You do not rise to the level of your goals. You fall to the level of your systems. — James Clear, Atomic Habits

Remote skips the duct-tape phase. Co-located teams can run on tribal knowledge, post-it notes on the wall, and hallway conversations for years before they need to invest in mature systems. Remote teams can’t. Every team that survives to scale-up ends up with the same infrastructure. Remote-first just pays the cost on day one.

Paved roads pay dividends. When the right path is the cheapest path, teams take it without thinking. Thaler and Sunstein call this choice architecture (Nudge). Investments in self-service tooling remove friction and yield ~5% productivity gains at both individual and team levels (DORA 2024). The same study flagged a “platform paradox” where individual gains can mask system-level slowdowns.

Teams play to the score. Team health and platform health both need instruments to set a baseline and track progress. Psychological safety, Developer eXperience, and SPACE or DORA frameworks measure team performance. Scorecards across security, maintainability, and observability measure platform quality. Project Aristotle put psychological safety at the top of team performance factors. What gets measured gets managed (Drucker).

Create cultural amplifiers. Culture eats strategy for breakfast. Name the behaviors you want and celebrate them publicly when they happen. From Amazon’s Leadership Principles to a Slack shoutout channel, the consistency matters more than the format. Peers see more behavior than managers ever could, which makes them the most effective and most underused source of reinforcement (Daniels), a gap that remote only widens. Give them the surfaces, and culture replicates from there.

It Was Never About Location

If employees are not engaged, it is a leadership problem. Nothing more, nothing less. — Aubrey Daniels

All three buckets (people, process, systems) are leadership problems, not location problems. Transformational leadership and stable priorities drive performance (DORA 2024). Rigid location mandates dampen productivity (Great Place to Work, 4-year study). Engagement reflects management’s behaviors, decisions, and policies.

The office treats collaboration as the default unit of work; remote-first treats focused deep work as the default. The default is what you optimize for. RTO mandates aren’t choosing collaboration over isolation; they’re choosing distraction over focus. The 2026 RTO mandate wave (TikTok 5d, Meta 5d, NBCU 4d) is treating the symptom: leadership avoiding the harder work of building the three disciplines.

The strongest counter-argument deserves a fair hearing. Learning, innovation, and peak performance can accelerate in-person. Remote teams were consistently less likely to make breakthrough discoveries across 20M papers and 4M patents over 50 years, drifting toward execution over conceptual work (Lin, Frey & Wu, 2023). But proximity alone doesn’t produce collaboration; it can suppress it (Bernstein & Turban, 2018). Collaboration is a design problem, not a real estate one. How a team interacts matters far more than where they sit (Google Project Aristotle).

Built Intentionally

The team you’ve built: globally-sourced talent doing their best work in flow, scaffolded by paved roads and scoreboards, reinforced by cultural amplifiers, with leadership that owns the conditions. Location stops being the variable.

Remote-first, intentional.