Summary
Remote was published in 2013, years before the pandemic forced the question on most organizations. Jason Fried and David Heinemeier Hansson — the founders of Basecamp — had been running a distributed company for a decade and wrote the book to make the case that remote work isn't a compromise but a competitive advantage. Their argument is that the traditional office is itself a productivity problem: open plans, endless meetings, and the expectation of constant availability destroy the kind of focused work that actually produces results.
The book is structured around objections. Each chapter takes a common argument against remote — "how do you know they're working?", "collaboration requires being in the same room", "company culture dies without a physical office" — and dismantles it. Fried and DHH are direct and often blunt. They don't try to address every edge case; they argue from Basecamp's experience and challenge readers to test the assumptions behind their current working arrangements.
The practical advice covers hiring for remote work, managing by output rather than presence, building asynchronous communication habits, and avoiding the trap of replicating office culture online. They emphasize writing over meetings, trust over surveillance, and results over face time. The book also tackles the risks of remote work honestly: isolation, difficulty separating work from home, and the challenge of building relationships without shared physical space.
Remote is a short book and reads quickly. By 2013 standards it was ahead of its time; by 2026 standards much of it reads as established practice in tech. For organizations still wrestling with hybrid policies and the politics of returning to office, the book's central question — what problem does the office actually solve? — remains sharper than most of the commentary around it. The authors don't pretend remote works for every role or every person, but they push the burden of proof back onto the assumption that physical presence is necessary.
Talk to Remote: Office Not Required like its author wrote you back.
Get the ideas that fit your life — not generic summaries.
- Chat with the book
- Audiobook-style main ideas
- Adapts to your life and goals
- Helps you take action
Key takeaways
- 1.
The traditional office is not neutral ground — open plans, constant interruptions, and mandatory presence actively undermine focused work for many people.
- 2.
Managing remote workers requires shifting from presence-based oversight to output-based evaluation: what gets done, not who was online when.
- 3.
Asynchronous communication — email, documents, recorded video — is often more effective than synchronous meetings, which interrupt deep work and require everyone to be available at the same time.
- 4.
Hiring for remote work requires different filters: self-discipline, clear written communication, and comfort with autonomy matter more than office-floor charisma.
- 5.
Remote work doesn't eliminate culture; it requires building culture deliberately through writing, shared tools, and occasional in-person gatherings rather than daily proximity.
- 6.
Surveillance tools and keystroke loggers signal distrust and demoralize employees; high-performing remote teams are built on trust, not monitoring.
- 7.
The biggest risk of remote work is isolation. Companies need to be intentional about creating connection, from online social spaces to periodic all-hands gatherings.
- 8.
Remote work expands the hiring pool globally, which means companies can hire the best person for a role rather than the best person willing to relocate to their city.
Discussion questions
Use these on your own, with a book club, or as chat starters in Superbook.
- 1.
Fried and DHH argue that offices are full of productivity-destroying interruptions. Does your experience in offices match that diagnosis?
- 2.
What assumptions does your current organization make about physical presence that have never been explicitly tested?
- 3.
Remote shifts performance evaluation from presence to output. For your role, what would measuring by output actually look like in practice?
- 4.
The book argues for asynchronous communication as a default. What decisions in your work genuinely require real-time discussion, and which ones only feel like they do?
- 5.
What do you lose in a remote environment that you can't easily replace? Is it structural to remote work or a symptom of doing it badly?
- 6.
The authors push back on surveillance tools for remote workers. How much does trust factor into how your organization manages distributed or hybrid teams?
- 7.
They argue that culture can be built remotely but requires deliberate effort. What have you seen organizations do well — or badly — when trying to maintain culture without physical proximity?
- 8.
Remote work expands access to talent globally but also creates challenges around time zones, pay equity, and legal complexity. How should organizations navigate those tradeoffs?
- 9.
Fried and DHH wrote this in 2013. Has the mass remote work experiment of 2020–2022 confirmed or complicated their arguments in your view?
- 10.
Is there a difference between remote-first and remote-tolerated organizations? Which model does your organization actually operate under?
- 11.
What would you personally need — tools, habits, boundaries — to do your best work fully remotely? What would you need to make a physical office worth the commute?
Themes
Frequently asked questions
-
Is Remote still worth reading in 2026?
Yes, though with lower surprise value than in 2013. The arguments have largely been validated by events. The book is most useful for managers and executives still debating hybrid policy, and for anyone wanting a compact, direct case against reflexive return-to-office mandates.
-
What is Remote by Jason Fried about?
It makes the case that remote work is not a compromise but a competitive advantage — for hiring, for focus, and for output quality. It addresses common objections to remote work and gives practical advice on managing distributed teams by results rather than presence.
-
How long does it take to read Remote?
About three to four hours. It's a short book, organized in bite-sized chapters. You can read it in a weekend afternoon or spread across several commutes.
-
Who should read Remote?
Managers, founders, and HR leaders making decisions about workplace policy. Also useful for employees trying to build the case for remote work with their own organizations, since the book gives them concrete counterarguments to the standard objections.
-
How does Remote compare to Rework by the same authors?
Rework is a broader manifesto about how to run a simpler, calmer business. Remote is narrower: it focuses specifically on distributed work. Rework is the more foundational text; Remote is better if remote work is the specific question you're wrestling with.
