Key Takeaways
Design culture deliberately; an office is only one possible setting
Culture is a working system. Razzetti defines culture as the interplay of what people do, feel, and assume, not the perks or slogans on display. It shapes how work gets done, so it cannot be repaired with a fresh values poster. The book cites research linking strong cultures to stronger results, including a Glassdoor analysis in which companies with strong cultures delivered nearly twice the gains of the S&P 500 comparison.
Rebuild what no longer fits. GoTo chose to refresh its office-centered culture rather than simply return to it, then declared itself remote-first. Apple’s proposed three-day office schedule, by contrast, drew employee protest. The lesson is not that offices are useless, but that old practices need to be reconsidered with employees, not copied into a new arrangement.
What's striking is the shift from treating culture as atmosphere to treating it as an operating system. In organizational design, routines, information flows, and decision rights often shape behavior more reliably than stated intentions. Remote work makes those hidden mechanisms easier to notice because informal office cues no longer fill every gap. Deliberate design, however, should not become leaders scripting every interaction. The strongest approach pairs clear structures with employee participation, leaving room for local teams to adapt practices to the work they actually do.
Measure contribution by impact, not by how busy someone looks
Visibility is not value. Office cultures often reward signals of effort, such as long hours, packed calendars, or rapid email replies. Those signals are easy to observe, but they do not establish that useful work was done. Razzetti recommends evaluating people against clear outcomes instead. Google’s use of objectives and key results helps teams define what they intend to achieve and clarify individual contributions without tracking every move.
Include learning, too. Microsoft also asks employees to consider how they helped others succeed and what they learned. The point is not to replace one rigid scorecard with another. It is to make expectations explicit, then judge work by its contribution rather than by presence, activity, or access to the office.
This principle challenges a familiar measurement error: mistaking what is easy to count for what matters. In economics, Goodhart's law describes how a measure can stop being useful once people are pressured to optimize it. Counting meetings or online minutes can reward performance theater. Outcome measures are better, but they also need care: individual targets can obscure teamwork, quality, or invisible support work. A sound system pairs clear results with judgment about how those results were achieved and who helped make them possible.
Give each team a purpose tied to people beyond itself
Purpose explains the why. The book distinguishes purpose from a mission, which describes what an organization does, and a vision, which describes what it hopes to become. Purpose names the positive impact it aims to create for others. For a team, Razzetti suggests asking what it delivers, whom it serves, and what difference its work should make.
Make the claim costly. CVS said it existed to help people improve their health, then stopped selling tobacco, risking about $2 billion in annual sales. The book reports that CVS customers became 38% more likely to stop buying cigarettes. A Mars Wrigley packaging team also changed its focus after discussion revealed that consumers, not only internal departments, were the people its work ultimately served.
Purpose is most useful when it helps people resolve competing demands, not when it merely supplies emotional decoration. This connects to the idea of a shared mental model: teams coordinate more easily when members understand who benefits from their work and why. A purpose statement can also expose disagreements about who counts as the customer or beneficiary, as the packaging team discovered. The test is behavioral consistency. If a purpose never changes priorities, resource allocation, or difficult decisions, it is probably descriptive branding rather than an operating guide.
Judge values by what leaders reward, tolerate, and punish
Behavior outranks the poster. US Bank employee Emily James used her lunch break and personal money to help a stranded customer. The bank fired her and her manager for violating a rule, despite its stated commitment to doing the right thing. The episode shows how employees learn the real culture from consequences, not declarations. Even unpunished behavior sends a signal about what leaders accept.
Translate ideals into actions. Calling a company transparent means little if employees fear speaking up; calling it collaborative rings hollow if selfish conduct earns promotion. Leaders need to name observable behaviors that express their values, and make those behaviors visible in recognition, promotion, and accountability. The book also warns that aspirational values can mislead when organizations claim qualities they have not yet made real.
The example illustrates a form of organizational learning: people watch what happens to someone who acts, then update their own sense of what is safe. That lesson can spread faster than a formal policy. It also explains why inconsistent value statements can damage trust more than having no slogan at all. Still, consequences require context. A single rule violation may involve genuine safety or legal risks, so leaders should investigate before rewarding or punishing. The important question is whether the rule serves the stated value or protects the organization from reconsidering it.
State your tradeoffs before competing priorities make them for you
Priorities mean choosing. A company that says yes to every worthwhile initiative can lose sight of what matters most. Razzetti describes “even over statements” as a way to make tradeoffs explicit: one important consideration takes priority over another when both cannot be satisfied. For example, a team might choose outcomes over visible effort, or long-term direction over a quick win.
Focus can restore capacity. When Steve Jobs returned to Apple in 1997, he cut the number of products by about 70 percent and concentrated on four. The company moved from a $1.04 billion loss in his first fiscal year to a $309 million profit the next. For hybrid teams, stating priorities in advance can make choices about flexibility, well-being, speed, and performance less arbitrary.
Explicit tradeoffs make decision-making more predictable because they turn vague values into guidance for real conflicts. They can also reduce the need to escalate every choice to a manager. The danger is treating a priority statement as a universal rule. Speed over perfection may suit a reversible experiment and be reckless for a safety-critical decision. A useful priority is therefore a default, not a substitute for context. Teams should name the tradeoff, identify when it applies, and revisit it when the work or its risks change.
Offer real flexibility, then prevent proximity from becoming privilege
Hybrid has several shapes. The book describes arrangements ranging from office-centered schedules to flexible hybrid work and remote-first systems. GoTo interviewed employees and identified different work situations, including people working alone, with children, or while caring for adults. Those differences helped the company design a remote-first approach around actual needs rather than a single imagined employee.
Equal opportunity is not identical treatment. Office presence can quietly grant some employees more access to executives, important conversations, and advancement. Razzetti calls this proximity bias. Teams can reduce it by making meetings accessible to remote participants, using clear participation rules, and judging results rather than visibility. Flexibility also means accepting that work and personal life overlap, while setting boundaries that prevent flexibility from becoming permanent availability.
Flexibility is not simply a location benefit. It redistributes control over time, attention, and care responsibilities, which can make work more accessible to people whose lives do not match a standard office schedule. Yet discretion without safeguards can create a hidden hierarchy between people who are physically present and those who are not. This is a procedural fairness problem: workers need comparable access to opportunity, even when their arrangements differ. Some roles also require physical presence, so fairness depends on explaining constraints and addressing them, not pretending every job can be remote.
Build safety until people can challenge the boss and the plan
Safety enables risk. Amy Edmondson’s term psychological safety means a shared belief that a team is safe for interpersonal risk-taking. People can ask for help, raise concerns, disagree, and admit mistakes without fearing retaliation. Razzetti presents a three-stage ladder: feeling welcomed, taking part in difficult conversations, and feeling safe enough to experiment and challenge existing practice.
Comfort is only the start. A team that is friendly but cannot question a plan has not reached the most useful form of safety. Practices such as letting quieter participants speak first, pausing after questions, or beginning idea work alone can widen participation. The book points to Apple’s early iPhone development as an example of employees continuing to argue for an idea that its founder initially rejected.
Psychological safety is often misunderstood as avoiding discomfort. In fact, its organizational value appears when people can surface information that is inconvenient, uncertain, or unpopular. That makes safety closely tied to error detection and collective learning. The distinction between welcome and challenge is especially useful: a team can feel pleasant while dissent remains costly. There is also a limit to what a workshop can accomplish. If leaders punish bad news in everyday decisions, an exercise designed to invite candor will not make the environment safe.
Make feedback a shared tool for learning, not a verdict
Feedback should open inquiry. Many employees dread formal reviews; the book cites a study in which 89% of people said they did not look forward to them. Razzetti argues that criticism can provoke defensiveness, while feedback works better as a perspective offered for learning rather than as an objective diagnosis of someone’s flaws. Managers can model this by requesting feedback themselves and by asking peers to contribute.
Turn toward the next attempt. Spotify’s development conversations devote most of their attention to the future, less to the present, and only a small portion to the past. Teams can also discuss a failure without hunting for a culprit: establish what happened, identify causes, and decide what to change. Sensitive personal issues may still call for a private conversation, even in a culture of open feedback.
This approach treats feedback as information to interpret, not a command to obey. That is a meaningful correction to systems where one manager's judgment can define an employee's reputation. Peer input and self-reflection can broaden the evidence, while future-oriented questions make feedback more actionable. But openness does not automatically make feedback accurate or kind. Power differences, bias, and vague criticism remain possible. Good practice separates observation from inference, asks what support would help, and gives the recipient room to decide how to use the perspective.
Make belonging repeatable, not dependent on chance encounters
Rituals carry meaning through repetition. Razzetti distinguishes a ritual from a routine: a ritual is a repeated act with shared symbolic meaning that helps shape identity and behavior. A weekly team walk or a new-hire welcome can make connection part of the work system rather than something left to office proximity.
Design for the feeling you want. The All Blacks rugby team clean their own locker room after matches, reinforcing humility and shared responsibility. During the pandemic, Zappos sent employees herb garden kits so they could continue sharing gardening and food in a distributed setting. A useful team ritual can happen live or asynchronously, but it needs a purpose, a regular cue, and a reason participants find it meaningful.
Rituals are a form of social infrastructure: they create repeated opportunities for people to recognize one another and reinforce a group's identity. That makes them particularly valuable when casual contact is less predictable. The strongest example is not necessarily the most elaborate one. A ritual can become hollow if attendance is forced or if its symbolism contradicts daily behavior. Teams should ask whose traditions it reflects, who feels welcome to participate, and whether the practice still serves its purpose. Meaning comes from shared interpretation, not the calendar invitation.
Default to asynchronous work; reserve live time for what needs it
Not every task needs a meeting. Asynchronous work lets people contribute at different times, often through written documents or shared digital tools. It gives people room to think, supports different schedules and time zones, and creates a record others can consult. Synchronous communication is still valuable for urgent coordination, sensitive conversations, and work that benefits from rapid exchange.
Match the method to the task. Razzetti distinguishes focused individual work, intensive joint problem-solving, routine coordination, learning, informal connection, and time away from work. A UC Berkeley finding cited in the book reports that people felt 43% more productive when they had a daily block of uninterrupted time. Documentation and clear response expectations help prevent asynchronous work from becoming a slow, confusing message backlog.
The important distinction is not remote versus in-person, but interruption versus intentional attention. Written communication can make discussion more inclusive because people have time to formulate a view, and it can preserve reasoning for colleagues who were not present. Yet asynchronous systems reward clarity and can disadvantage people who lack access to context or confidence in writing. Live discussion is sometimes the fairer and faster method, especially in emotionally complex situations. Teams need explicit criteria for choosing a channel, not an ideological ban on meetings.
Give reversible decisions to the people closest to the problem
Match authority to risk. Many routine decisions can be changed if they do not work, so they need not wait for senior approval. Amazon calls these low-stakes, reversible choices Type 2 decisions. More consequential or difficult-to-reverse decisions deserve slower consideration and broader input. Razzetti recommends checking the cost of waiting, not only the risk of acting.
Make the process visible. A decision page can record the context, available information, input, and rationale for important choices. The Advice Process asks a decision-maker to consult people substantially affected by the decision and those with relevant expertise, without requiring unanimous agreement. Teams can also test a safe-to-try option, learn from its effects, and adjust rather than waiting for certainty.
Distributing authority can improve both speed and information quality because people closest to a problem often know details that executives cannot see. Recording the rationale also makes a decision easier to challenge when its assumptions change. The essential distinction is between consultation and consensus: involving affected people does not mean every person holds a veto. Still, reversibility can be deceptive. A small operational choice may have unequal effects across groups, so decision-makers should consider who bears the downside, how quickly harm can be detected, and who has the power to stop the experiment.
Lead by shaping conditions, not by monitoring everyone's presence
Remote leadership is facilitation. Razzetti argues that leaders need not be the heroes who solve every problem. Their job is to build a culture where people can do good work: clarify expectations, listen, remove obstacles, and create fair ways to participate. The book’s “trust battery” is a metaphor for how trust rises or falls through repeated interactions; leaders are urged to extend trust rather than making every new employee prove themselves under surveillance.
Model the rules. If leaders say focused time matters but send constant messages, the real norm is still instant availability. Leaders can demonstrate the intended culture by respecting calendars, communicating clearly, inviting input, and acknowledging uncertainty. They also need to experience the practical difficulties of remote work rather than designing policies only from the office.
This view shifts leadership from direct supervision toward system stewardship. It aligns with research on autonomy-supportive management, where clear goals coexist with meaningful discretion. Such leadership does not mean withdrawing: employees still need resources, feedback, and help resolving conflicts. Trust also cannot substitute for accountability. The useful balance is to make outcomes and decision boundaries clear while avoiding surveillance as a proxy for performance. The strongest test of a leader's credibility is whether the same norms apply to senior people, not only to everyone below them.
Analysis
Remote, Not Distant is a practical argument against treating office attendance as a proxy for culture. Its core contribution is to recast culture as a set of connected choices: what outcomes matter, who has voice, how work moves, and which behaviors receive consequences. The book’s five-part journey moves from resetting assumptions to purpose, belonging, collaboration, and agility. Its examples make abstract concepts tangible, from US Bank firing an employee who helped a customer to GoTo deliberately adopting remote-first work.
The strongest insight is that distance does not automatically weaken culture. It exposes whether a team already depended on informal access, visibility, or unspoken rules. Documentation, explicit decision rights, inclusive facilitation, and recurring rituals can replace some of those mechanisms, while preserving the human connection they were meant to provide. The approach also correctly refuses a single universal remote policy: teams differ in their work, caregiving needs, time zones, and access to suitable spaces.
The book is most persuasive as a design toolkit, not as proof that every organization should maximize remote work. Much of its evidence comes from surveys, company examples, and practitioner interviews. These offer practical insight but cannot establish that a particular policy caused a company’s performance or culture. The argument also travels unevenly across occupations. Work that requires equipment, physical care, or secure facilities cannot be made location-flexible by better meeting norms. Even within knowledge work, flexibility without fair access to advancement can reproduce hierarchy in a new form.
The lasting value is therefore not a formula for remote work. It is a way to ask better questions: What problem does this rule solve? Who can participate? What behavior does this reward? Can the team change course if the evidence changes? Those questions help organizations design work around purpose and contribution rather than habit, while keeping flexibility accountable to both people and results.
Review Summary
Remote, Not Distant offers practical insights for creating a thriving remote work culture. Readers appreciate its actionable advice, real-world examples, and focus on intentional culture design. The book emphasizes flexibility, asynchronous collaboration, and employee empowerment. While some find it repetitive or lacking groundbreaking ideas, many praise its relevance to post-pandemic workplace challenges. Critics note that hybrid implementation seems secondary, and the book could benefit from more hard data. Overall, it's considered a valuable resource for leaders and employees navigating the evolving landscape of remote and hybrid work.
Glossary
Anywhere/Anytime Culture
Location-flexible shared cultureRazzetti's term for a workplace culture designed to connect people and support effective work regardless of where or when they work. It does not mean that every task can happen anywhere or at any hour. It requires intentional norms for communication, collaboration, inclusion, and decision-making across different schedules and locations.
Culture Design Canvas
Map of culture componentsA visual framework Razzetti developed to help teams examine and shape culture as an interconnected system. It groups the work into three areas: the Core, including purpose, values, priorities, and rewarded behavior; Emotional Culture, including belonging, safety, feedback, and rituals; and Functional Culture, including decisions, meetings, norms, and rules.
Psychological Safety Ladder
Stages of team safetyRazzetti's framework for thinking about psychological safety as a progression. Teams first help members feel welcomed, then make it possible to have courageous conversations, and finally support challenge, experimentation, and innovation. The ladder emphasizes that friendliness alone is not enough, and that harmful behavior can undermine safety that a team has built.
trust battery
Metaphor for changing trustA metaphor popularized by Shopify CEO Tobi Lütke for the level of trust between colleagues. The battery begins partly charged, rises through positive interactions, and falls through negative ones. Razzetti uses the idea to argue that leaders in distributed workplaces should demonstrate trust early rather than relying on constant observation while employees slowly prove themselves.
even over statements
Explicit priority tradeoffsA technique for stating which of two worthwhile priorities takes precedence when both cannot be fully satisfied. A team might choose outcomes over visible effort, for example. The statement is not a claim that the lower-ranked priority has no value. It provides a default for decisions and helps employees act without seeking managerial approval for every conflict.
Advice Process
Consult before decidingA decision practice in which the person making a decision seeks input from people who will be significantly affected and from people with relevant expertise. The decision-maker remains responsible for the final choice. The process aims to improve decisions and account for affected interests without requiring consensus or giving every participant a veto.
async-first
Default to time-shifted workAn approach that favors communication and collaboration people can complete at different times, such as written proposals, shared documents, or recorded updates. It protects focus, supports varied schedules, and creates a record of decisions. It does not eliminate live meetings, which remain useful for urgent, sensitive, or highly interactive work.
Blameless Postmortem
Learn from failures without scapegoatingA structured review of a mistake or failure that focuses on what happened, which conditions contributed, and how the system can improve. It assumes people generally acted on the information available at the time and seeks causes rather than culprits. Blameless does not mean consequence-free; it aims to build accountability through learning and prevention.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.