Managers resist WFH and remote work for four distinct reasons — each requires a different response. Knowing which objection applies lets you craft a proposal that actually addresses the problem. ## The Four Objections **1. Working independently**: If the manager isn't confident you can work without supervision, they won't let you out of sight. And they'd be right — if you can't work independently yet, don't ask. First build the skills (Ch 2–3), then have the conversation. **2. Business knowledge**: Complex domains require in-person onboarding. One VP told the author it would take six months to become fully productive — remote workers would have a harder time. A timing issue, not a permanent objection. **3. Communication bandwidth**: Complex ideas are easier to convey in person than on a call, let alone text chat. If the team is in a complex problem-solving phase, this is a real concern. **4. Control bias**: Managers who can't measure productivity default to measuring hours-at-desk. Working from home removes their ability to count visible hours — it's about their mental model of oversight, not your output. ## How to Diagnose and Respond Don't ask "can I work from home?" — ask open-ended questions to uncover the real objection: - "How would you feel about me working from home occasionally?" - If negative: "What specifically would I need to do to prove I can work from home?" - Propose logistical fixes targeting that objection (e.g., WFH after sprint planning day, when you're working independently anyway) Always frame WFH as company value: better focus, less commute fatigue, more output. ## Related Concepts - [[Working Independently as the First Goal]] — Prerequisite before even raising WFH - [[Trust Hurdle for Remote Work]] — Remote requires going further than WFH --- *Source: [[The Programmer's Guide to a Sane Workweek]] (Itamar Turner-Trauring, v1.3.0) — Ch 9 §9.1–9.2*