diff --git a/src/content/posts/2026-08-01-anti-patterns-in-remote-leadership.md b/src/content/posts/2026-08-01-anti-patterns-in-remote-leadership.md new file mode 100644 index 000000000..d26c35283 --- /dev/null +++ b/src/content/posts/2026-08-01-anti-patterns-in-remote-leadership.md @@ -0,0 +1,144 @@ +--- +title: "Remote Leadership Anti-Patterns That Don’t Scale" +description: "Most remote leadership fails for a simple reason: managers keep using co-located habits on distributed teams. Here’s the rewrite." +published: false +--- + + +I’ve personally tracked [NUMBER: e.g., "40+"] leadership mishaps on remote teams over the past [TIME PERIOD: e.g., "few years"]. About 90% of them boil down to three avoidable anti-patterns. + +The named pain sounds like this: *My manager tries to run a distributed team like it’s co-located.* + +That’s the whole problem. + +Most remote leadership doesn’t fail because people are lazy, disengaged, or bad at Zoom. It fails because managers keep reaching for synchronous habits that only worked when everyone sat within shoulder-tapping distance. They digitize the old workflow instead of redesigning it for a distributed team. Same behavior, new tools, worse results. + +And yes, it gets expensive fast. + +You get meetings to “stay aligned.” Slack pings that expect immediate answers. Decisions made in side channels, then awkwardly announced after the fact. A manager who thinks responsiveness is the same thing as leadership. Before long, your team is drowning in interruptions, starving for context, and quietly accruing [communications debt](https://ben.balter.com/2022/02/16/leaders-show-their-work/). + +Remote leadership has to be async by default or it’s not really remote leadership. It’s just office management with worse lighting. + +## The half-remote trap + +The most common failure mode I see isn’t fully in-office thinking or fully distributed thinking. It’s the mushy middle. + +A team goes remote, but the manager still treats meetings as the source of truth. Chat becomes a proxy for presence. People who answer quickly get seen as engaged. People who think before they speak get mistaken for being behind. Work happens online, but decision-making still happens in the moment, around whoever was available. + +That’s not remote-first. That’s co-located management with shipping delays. + +And the cost isn’t just annoyance. These habits create structural problems. They privilege time zones, extroversion, and proximity to the manager. They punish deep work. They make onboarding harder because the real context lives in calendars and private threads. They turn basic coordination into an O(n²) game of “did anyone tell you?” + +If you’re leading a distributed team, your job is not to recreate the office on the internet. Your job is to build a system where people can make progress without waiting for you to be online. + +## The three anti-patterns that keep showing up + +I keep seeing the same three mistakes because they feel efficient in the moment. That’s what makes them dangerous. Like most shortcuts, they borrow a little time from now and send the bill to your future team. + +### 1. Presence-based leadership + +This one shows up as constant check-ins, fast-response expectations, and an obsession with visible activity. + +You know the moves: “Can everyone stay active in Slack?” “Let’s do a quick standup on Zoom every morning.” “Why didn’t you reply for two hours?” Managers don’t always say the quiet part out loud, but the message lands anyway: I trust what I can see happening in real time. + +That logic breaks the minute your team spans time zones, caregiving schedules, or simply different work styles. Knowledge work is not a call center queue. A two-hour block of uninterrupted focus is usually worth more than [NUMBER: e.g., "20"] reactive chat messages. + +The rewrite is simple: measure momentum, not motion. + +Ask for visible work, visible priorities, and visible blockers in durable channels. Have people [show their work](https://ben.balter.com/2022/02/16/leaders-show-their-work/) through issues, pull requests, docs, project boards, or weekly written updates. Judge people by the quality, clarity, and consistency of their contributions—not whether they green-dot on command. + +If you need to know what someone is working on, that information should exist without you having to interrupt them. + +### 2. Meeting-as-default management + +A surprising number of remote managers respond to uncertainty by scheduling more meetings. It feels responsible. It’s usually the opposite. + +Meetings are expensive serialization points. They force everyone to process the same information at the same time, at the speed of the loudest person in the room. On a distributed team, that’s not alignment. It’s a bottleneck with calendar invites. + +Worse, meetings often become where decisions are made, which means anyone who couldn’t attend gets a second-class version of reality. You can publish notes later, but notes about a decision are not the same thing as seeing the trade-offs, alternatives, and reasoning that produced it. + +The rewrite: write first, meet second. + +Use a document, issue, or pull request to frame the problem, options, recommendation, and open questions before you get people in a room. Let others comment async. Use the meeting only for what actually benefits from high-bandwidth conversation—brainstorming, sensitive feedback, conflict resolution, or true deadlock-breaking. Then capture the outcome in the same durable place. + +This is the difference between a team that occasionally meets and a team that depends on meetings to function. + +One scales. One doesn’t. + +### 3. Private-context decision making + +This is the sneakiest anti-pattern because it often looks efficient, even considerate. + +A manager grabs a few people in a DM, hashes out the decision in private, then posts the conclusion publicly once it’s “ready.” The intent is usually good: save time, avoid noise, spare everyone the churn. The result is predictable. The team sees the what, but not the how or why. People feel decisions are happening *to* them, not around them. Then the follow-up questions start. Then the re-explaining. Then the rumor mill. + +That’s communications debt in its purest form. + +The rewrite is to work in the open by default. Not performatively. Not because every thought needs a stage. Because teams make better decisions when the relevant context is visible to the people affected. + +Open the issue early. Share the draft before it’s polished. Invite input while the decision can still change, not after. If you need a small working group to make progress, fine. Just leave a trail. Show the alternatives considered. Capture the rationale. Link the artifacts. + +A URL is necessary, but not sufficient. The record has to explain the decision, not just announce it. + +## The copy-pasteable playbook + +If you manage a distributed team, here’s the rewrite in plain English: + +- **Anti-pattern:** Treat responsiveness as engagement + **Rewrite:** Treat clear, durable progress as engagement + +- **Anti-pattern:** Use meetings to create alignment + **Rewrite:** Use writing to create alignment, and meetings to resolve what writing can’t + +- **Anti-pattern:** Make decisions in DMs, then broadcast the result + **Rewrite:** Make decisions in visible channels, and capture the why along with the what + +- **Anti-pattern:** Ask people for status updates one by one + **Rewrite:** Create shared systems where status updates are ambient and self-serve + +- **Anti-pattern:** Reward the fastest responder + **Rewrite:** Reward the clearest thinker and the best teammate + +- **Anti-pattern:** Assume everyone heard the same thing + **Rewrite:** Put the source of truth in writing, and link to it often + +- **Anti-pattern:** Use chat as your management system + **Rewrite:** Use chat for coordination, not institutional memory + +- **Anti-pattern:** Wait until a decision is final to socialize it + **Rewrite:** Share work while it’s still shapeable + +Print that out. Paste it into your manager README. Better yet, audit your calendar and your team norms against it. + +## A fair objection + +Some work does need synchronous communication. + +Of course it does. + +You can’t brainstorm every messy idea in a pull request. Sensitive feedback deserves a human conversation. A team in crisis should not wait politely for threaded comments to roll in across three time zones. Remote leadership is not the dogmatic rejection of meetings, chat, or real-time discussion. It’s the refusal to make them your default operating system. + +That distinction matters. Async by default doesn’t mean async only. It means synchronous communication is the exception you choose deliberately, not the habit you fall back on automatically. That’s a big theme in [Why async](https://ben.balter.com/2022/03/17/why-async/), and it’s also where a lot of teams get stuck: half-measures. They adopt remote tools without adopting remote norms. + +That’s why so many distributed teams feel oddly exhausting. They didn’t remove the old coordination costs. They added new ones on top. + +## What to do this week + +If this post feels uncomfortably familiar, don’t start with a grand transformation. Start by removing one source of drag. + +Cancel one recurring status meeting and replace it with a written update. Move one decision out of DMs and into a visible issue. When someone asks you for context, don’t answer only in chat—write it down somewhere durable and send the link. If you find yourself asking, “Why didn’t I know this?” the answer is probably not “my team failed to tell me.” It’s “our system failed to surface it.” + +That shift sounds small. It’s not. + +Remote leadership is systems design. Your team will follow the incentives, defaults, and channels you create. If your workflow rewards interruption, private context, and real-time availability, you’ll get more of all three. If your workflow rewards clarity, traceability, and autonomy, people will rise to that too. + +I have a pretty strong opinion here: if you’re leading a distributed team, you owe people a way of working that doesn’t require them to be constantly online, constantly reactive, or constantly guessing. Anything less is just making them pay for management habits you didn’t bother to update. + +And your team can tell. + +Usually long before you do.