Thrive working remotely
This curriculum takes you from remote-work newcomer to high-performing distributed professional in four tightly sequenced stages. It begins by building the mindset and vocabulary of async, location-independent work, then layers in deep-work habits, communication craft, and finally the advanced skills of visibility, leadership, and career growth on a distributed team.
Foundations: The Remote Mindset
New to itUnderstand what makes remote work fundamentally different, bust common myths, and adopt the core principles that high-performing remote workers live by.
▸ Study plan for this stage
Pace: 4–5 weeks total (~20–25 pages/day): spend the first 2 weeks on "Remote: Office Not Required" (roughly 240 pages, ~17–20 pages/day at a relaxed pace), then 2–3 weeks on "The Year Without Pants" (~270 pages, ~18–22 pages/day), leaving a few buffer days at the end for review and reflection exercises.
- The 'office as default' myth — Fried & Hansson's central argument that the physical office is a habit, not a necessity, and that most objections to remote work are rooted in managerial fear rather than evidence
- Asynchronous-first communication — the shift from real-time interruption culture to deliberate, written, time-shifted collaboration as the backbone of remote productivity
- Trust over surveillance — why measuring output and results replaces measuring presence and hours, and how this reframes the manager–employee relationship entirely
- Remote work as a talent and lifestyle advantage — Fried's case that remote unlocks a global talent pool and gives workers autonomy that drives retention and performance
- Culture is behavior, not a building — Berkun's on-the-ground account of how Automattic deliberately encoded values (transparency, writing, autonomy) into daily rituals rather than office perks
- Writing as a first-class skill — Berkun's observation that at Automattic, the ability to communicate clearly in text was the single most important professional competency, replacing verbal charisma
- Distributed teams still need human connection — Berkun's nuanced counterpoint that remote does not mean isolated; intentional meetups, chat culture, and 1-on-1s are engineered substitutes for hallway serendipity
- The remote mindset shift — moving from 'I need permission to work remotely' to 'I need to design my own environment, schedule, and communication habits to perform at my best'
- According to Fried and Hansson, what are the three most common employer objections to remote work, and what evidence do they offer to refute each one?
- How does Automattic's culture, as described by Berkun, demonstrate that company values can be maintained — or even strengthened — without a shared physical office?
- What specific communication practices did Berkun observe at Automattic that replaced the spontaneous information-sharing of an open-plan office, and which of those practices could you adopt today?
- Both books argue that remote work demands a higher standard of written communication. What concrete habits or norms do the authors suggest to meet that standard?
- Fried argues that 'the office is an interruption factory.' How does this critique connect to the asynchronous-first principles Berkun witnessed at Automattic?
- After reading both books, how would you define the 'remote mindset' in your own words — and what is one belief or habit you currently hold that contradicts it?
- **Myth-busting journal:** After finishing 'Remote,' list every objection to remote work you have heard (or believed). For each one, write a one-paragraph rebuttal grounded specifically in Fried & Hansson's arguments and data points.
- **Personal async audit:** For one full workday, log every communication you send or receive. Categorize each as synchronous (meeting, phone, instant ping) or asynchronous (email, doc comment, recorded video). Calculate your ratio, then write a plan to shift at least 30% of sync interactions to async, using principles from both books.
- **Write like Automattic:** Pick one topic you would normally explain verbally to a colleague (a project update, a decision, a how-to). Write it up as a P2-style internal blog post — clear, self-contained, and readable by someone in a different time zone who wasn't in any prior conversation about it.
- **Remote environment design sprint:** Inspired by Berkun's descriptions of Automattic employees owning their own workspaces, sketch and then physically rearrange or upgrade your own remote workspace. Document what you changed and why, linking each change to a principle from the books.
- **'Office Not Required' debate prep:** Write a two-page position paper arguing the opposite of your natural instinct — if you're pro-remote, steelman the office; if you're skeptical of remote, steelman full distribution. Use specific passages from both books as evidence for the side you're arguing against your gut.
- **Reflection letter:** Write a one-page letter to yourself dated one year from now, describing the specific remote work habits and mindset shifts you intend to have made. Reference at least three concrete ideas — one from Fried, one from Berkun, and one synthesis of both.
Next up: By internalizing the 'why' and 'what' of remote work through Fried's manifesto and Berkun's field report, the reader has the conceptual foundation needed to move into the next stage, which tackles the 'how' — the practical tools, workflows, and team rituals that turn remote principles into daily, repeatable systems.
The canonical starting point — it dismantles objections to remote work and frames the philosophy clearly, giving you the vocabulary and conviction to commit to the lifestyle before diving into tactics.
A journalist's inside account of working at Automattic, one of the world's most successful fully-remote companies; it makes the abstract principles of Remote concrete through vivid real-world storytelling.
Deep Work & Personal Productivity
New to itBuild a personal system for focused, high-output work from any location — protecting attention, structuring your day, and designing a home office that enables flow.
▸ Study plan for this stage
Pace: 6–8 weeks total: Weeks 1–4 for "Deep Work" (~25–30 pages/day, ~5 days/week), Weeks 5–8 for "Getting Things Done" (~20–25 pages/day, ~5 days/week). Allow 1–2 buffer days per week for reflection and exercise completion.
- Deep Work vs. Shallow Work (Newport): The distinction between cognitively demanding, distraction-free work and low-value, logistical tasks — and why remote workers must actively protect the former.
- The Four Deep Work Philosophies (Newport): Monastic, Bimodal, Rhythmic, and Journalistic scheduling modes, and how to choose the right one for your remote lifestyle.
- Attention Residue & the Cost of Task-Switching (Newport): Why jumping between tasks — especially common in remote work chat culture — destroys cognitive output, and how to batch and isolate focus sessions.
- Productive Meditation & Deliberate Practice (Newport): Using idle physical time (walks, commutes) to advance complex thinking, and structuring practice to push cognitive limits.
- The GTD Capture-Clarify-Organize-Reflect-Engage Workflow (Allen): A five-step system for externalizing every commitment out of your head and into a trusted system, eliminating mental overhead.
- The Two-Minute Rule & Next Actions (Allen): If a task takes less than two minutes, do it immediately; otherwise, define the very next physical action to keep projects moving without mental drag.
- The Weekly Review (Allen): A non-negotiable ritual to process inboxes, update project lists, and re-calibrate priorities — especially critical when working remotely without manager check-ins.
- Designing a Distraction-Resistant Environment (Newport + Allen): Combining Newport's 'grand gesture' and workspace rituals with Allen's physical/digital inbox design to create a home office that signals and sustains deep focus.
- After reading Deep Work, can you articulate the difference between deep and shallow work and give three concrete examples of each from your own remote job?
- Which of Newport's four scheduling philosophies fits your current remote work arrangement, and what would a realistic weekly deep work block schedule look like for you?
- How does attention residue explain the hidden productivity cost of Slack/email notifications, and what specific boundaries would you set to reduce it?
- Can you walk through all five steps of Allen's GTD workflow and explain what happens to a new task — say, an email requesting a project update — at each stage?
- What is a 'next action' in GTD terms, and why is defining it the critical moment that prevents projects from stalling?
- How would you design your home office (physical layout, digital tools, and daily rituals) by combining Newport's environmental cues for flow with Allen's inbox-zero capture system?
- **Deep Work Audit (Week 1):** Track every work activity for five days in 30-minute blocks. Label each block 'Deep' or 'Shallow.' Calculate your weekly deep work hours as a baseline, then set a target to increase it by 20% by the end of the stage.
- **Philosophy Experiment (Weeks 2–3):** Pick one of Newport's four scheduling philosophies and run it as a two-week experiment. Block deep work sessions in your calendar, treat them as unmovable meetings, and log your output quality and volume each day.
- **Shutdown Ritual Design (Week 3):** Following Newport's 'shutdown complete' concept, write out a personal end-of-day shutdown checklist (review tasks, clear inboxes, set tomorrow's top priority). Practice it every workday for two weeks and note its effect on evening mental rest.
- **Full GTD Capture Dump (Week 5):** Do a complete mind-sweep as Allen prescribes — write down every open loop, project, commitment, and nagging thought across work and personal life. Process each item through Clarify and Organize into a tool of your choice (Notion, Todoist, paper folders, etc.).
- **Weekly Review Implementation (Weeks 6–8):** Schedule a 60-minute Weekly Review every Friday. Use Allen's checklist: process all inboxes, review all project lists, update next actions, and do a calendar look-ahead. Journal two sentences after each review: what felt clear, what still felt murky.
- **Home Office Deep Work Design Sprint (End of Stage):** Redesign your physical or digital workspace using both authors' principles: create a single capture inbox (Allen), remove your phone from your desk, add a visible timer for focus sessions, and write a personal 'rules of engagement' document (Newport) — a one-page manifesto of when you are and aren't reachable during deep work hours.
Next up: By establishing a personal deep work schedule and a trusted GTD capture system, the reader has the focused time and mental clarity needed to tackle the next stage's challenges — whether that involves remote collaboration, async communication, or managing distributed teams — without those external demands collapsing their hard-won productivity structure.
Establishes the intellectual case for distraction-free concentration and provides concrete protocols for scheduling deep work — essential before you can thrive without an office environment to impose structure.
The gold-standard trusted system for capturing, clarifying, and executing tasks; remote workers must self-manage ruthlessly, and GTD gives you the infrastructure to do that reliably.
Async Communication & Distributed Collaboration
Some backgroundMaster written async communication, run effective remote meetings, and collaborate seamlessly across time zones without defaulting to constant interruption.
▸ Study plan for this stage
Pace: 6–8 weeks total: Weeks 1–4 cover "It Doesn't Have to Be Crazy at Work" (~20–25 pages/day, including reflection pauses after each section); Weeks 5–8 cover "Collaborating with the Enemy" (~15–20 pages/day, slower pace to wrestle with the more conceptual "stretch collaboration" framework). Reserve the
- Calm company philosophy: protecting time, attention, and energy as finite resources in a remote/distributed context
- Asynchronous-first culture: the discipline of defaulting to written, time-shifted communication rather than real-time interruption
- Long, uninterrupted work blocks ('library rules'): designing your workday so deep work is the norm, not the exception
- Meetings as a last resort: Fried's criteria for when a meeting is truly necessary and how to run it with minimal cost
- Written communication as a craft: clarity, completeness, and context in async messages so recipients can act without follow-up pings
- Stretch collaboration (Kahane): working effectively with people you disagree with, don't fully trust, or cannot control — essential for cross-functional and cross-timezone teams
- The three dimensions of complexity (Kahane): dynamic, generative, and social complexity, and how each shows up in distributed team problems
- Toggling between 'downloading' and 'presencing': Kahane's spectrum of listening and co-creating, applied to async threads and remote workshops
- According to Fried, what specific organizational habits make work 'crazy,' and which of those habits are amplified in a remote setting?
- How does Fried distinguish between a 'real' meeting and a reflexive one, and what concrete alternatives does he propose for distributed teams?
- What does Kahane mean by 'collaborating with the enemy,' and how does his concept of stretch collaboration differ from conventional consensus-building?
- How can Kahane's three types of complexity (dynamic, generative, social) be used to diagnose why a particular distributed team is struggling?
- How do the philosophies of Fried and Kahane complement each other — where does Fried's 'calm' culture need Kahane's 'stretch' mindset to handle genuine conflict or ambiguity?
- What practical protocols can you design, drawing on both books, to run a remote decision-making process that is async-first yet still surfaces real disagreement?
- Async communication audit: For one full work week, log every message or meeting you send/attend. Classify each as truly async-capable or genuinely synchronous. At the end of the week, rewrite three 'sync' interactions as async alternatives (a structured Loom video, a decision doc, or a detailed Basecamp-style message) using Fried's principles of clarity and completeness.
- Meeting diet challenge: Apply Fried's 'last resort' test to your next five scheduled meetings. Cancel or convert at least two into written updates or recorded walkthroughs. Document the time saved and any information lost — reflect on the trade-offs honestly.
- Stakeholder complexity map (Kahane): Pick a current cross-team or cross-timezone project. Map all stakeholders using Kahane's three complexity dimensions — who introduces dynamic complexity (things keep changing), generative complexity (the goal itself is unclear), and social complexity (people disagree on values or power). Write a one-page diagnosis and propose one process change for each dimensi
- Stretch collaboration role-play: Identify a real or hypothetical distributed team conflict (e.g., two time zones disagreeing on a release schedule). Draft a facilitation plan using Kahane's 'stretch' moves — explicitly include moments for both advocacy and inquiry, and design at least one async step (e.g., a shared written reflection before a live call).
- Personal async communication style guide: Write a 1–2 page personal guide for your own async communication — covering message structure, expected response times, how you signal urgency, and how you handle disagreement in writing. Ground each rule in a specific insight from Fried or Kahane.
- Cross-timezone collaboration protocol: Design a lightweight team agreement (a 'working together' doc) for a hypothetical 3-timezone team. Include: core overlap hours, async-first norms, a decision-making ladder (what's async vs. sync), and a conflict escalation path informed by Kahane's stretch collaboration steps.
Next up: Mastering async communication and stretch collaboration builds the written clarity and interpersonal trust needed to tackle the next stage's focus on remote leadership and building high-performing distributed teams — where the stakes of miscommunication and misalignment are organizational, not just individual.
Bridges personal productivity into team culture — it teaches calm, intentional communication norms that reduce meeting overload and make async-first collaboration the default.
Teaches how to work productively with people you don't share a physical space — or even full alignment — with, building the collaborative resilience needed on diverse, distributed teams.
Visibility, Leadership & Long-Term Career Growth
Going deepStay visible and promotable on a distributed team, lead remote projects with influence rather than authority, and build a sustainable, thriving remote career for the long haul.
▸ Study plan for this stage
Pace: 10–12 weeks total (~20–25 pages/day, 5 days/week): Weeks 1–4 for "The Long-Distance Leader" (~30 pages/day, 4 days/week), Weeks 5–8 for "Digital Body Language" (~25 pages/day, 4 days/week), Weeks 9–12 for "A World Without Email" (~25 pages/day, 4 days/week); reserve one day per week for reflection,
- The 'Rules of Engagement' for remote leadership — Eikenberry's model of leading with outcomes, trust, and intentional communication rather than physical proximity or micromanagement
- The Remote Leadership Model: separating leadership tasks (coaching, goal-setting, accountability) from the tools used to accomplish them in a distributed context
- Digital Body Language as a new literacy — Dhawan's argument that tone, timing, formatting, and responsiveness in written digital communication carry the same weight as physical cues in face-to-face settings
- The four laws of Digital Body Language: Value Visibly, Communicate Carefully, Collaborate Confidently, and Trust Totally — and how each law applies to career visibility on a remote team
- The Hyperactive Hive Mind — Newport's diagnosis of how always-on, unstructured email and chat culture fragments attention, signals busyness over output, and systematically disadvantages deep workers
- The Attention Capital Principle — Newport's framework for redesigning workflows around human cognitive capacity rather than reactive communication tools, enabling sustainable high performance
- Influence without authority: how remote leaders build credibility, psychological safety, and followership through consistency, clarity, and visible contribution rather than positional power
- Sustainable remote career design: integrating deliberate visibility strategies, communication discipline, and deep-work protocols into a long-term professional identity
- According to Eikenberry, what are the most common mistakes remote leaders make when trying to maintain team cohesion, and what specific practices does he recommend to lead with outcomes rather than oversight?
- How does Dhawan define 'digital body language,' and can you give three concrete examples of how a misread digital cue (e.g., a short reply, a delayed response, or overuse of exclamation points) can damage trust or career reputation on a remote team?
- What are Dhawan's four laws of Digital Body Language, and how would you apply each one to a real scenario — such as a promotion conversation, a project kickoff email, or a cross-functional Slack thread?
- Newport argues that the 'Hyperactive Hive Mind' workflow is economically entrenched despite being cognitively destructive — what forces keep it in place, and what does he propose as a structural alternative at the individual and organizational level?
- How do the frameworks from all three books intersect? Specifically, how does Eikenberry's remote leadership model depend on the communication precision Dhawan advocates and the workflow redesign Newport prescribes?
- What does a 'promotable remote professional' look like according to the combined lessons of this stage — how do they stay visible, lead with influence, and protect their capacity for high-value work simultaneously?
- **Leadership Audit (Eikenberry):** List every recurring interaction you have with your team or manager in a week. Classify each as 'outcome-focused' or 'activity-focused.' Redesign at least two activity-focused touchpoints into outcome-focused ones using Eikenberry's framework, and run the new format for two weeks.
- **Digital Body Language Rewrite (Dhawan):** Pull five real emails or Slack messages you sent in the past month. Score each against Dhawan's four laws. Rewrite any that fall short — paying attention to tone, length, formatting, and response timing — then compare the before/after versions with a trusted colleague.
- **Visibility Mapping Exercise (Dhawan + Eikenberry):** Draw a stakeholder map of everyone who influences your career (manager, skip-level, cross-functional partners, senior leaders). For each person, note how often they see your work and how clearly they understand your contributions. Create a 30-day plan to close the biggest visibility gaps using intentional digital communication.
- **Workflow Redesign Sprint (Newport):** Identify your top three sources of reactive, unstructured communication (e.g., always-on Slack, reply-all email threads). For each, design a 'process-centric' alternative — a defined protocol, office-hours slot, or async update system — and pilot it for three weeks, tracking your deep-work hours before and after.
- **Influence-Without-Authority Project (Eikenberry + Newport):** Take a current or upcoming cross-functional initiative where you have no direct authority. Write a one-page 'influence plan' that specifies: how you will communicate progress visibly, how you will protect the team's attention from hive-mind overhead, and how you will build trust through consistency and clarity over the project's durat
- **Long-Term Career Narrative (all three books):** Write a 500-word 'remote professional statement' that articulates your leadership philosophy, your communication standards, and your workflow principles — drawing explicitly on concepts from all three books. Share it with a mentor or peer and refine it based on feedback; revisit it quarterly.
Next up: By mastering visible leadership, disciplined digital communication, and attention-protective workflows, the reader has built the personal infrastructure of a high-performing remote professional — laying the foundation for any next stage focused on scaling those skills to organizational change, team culture design, or entrepreneurial remote ventures.
Shifts the lens from individual contributor to team leader — it provides a model for leading with trust and outcomes rather than oversight, critical as you grow in seniority on a remote team.
Teaches you to project presence, credibility, and warmth through digital channels — the advanced communication layer that determines who gets noticed, trusted, and promoted in a remote organization.
The capstone read: Newport's systems-level critique of hyperactive hive-mind work and his blueprint for redesigning team workflows around deep collaboration — ideal for those ready to change not just their own habits but their team's culture.