The hardest thing about managing a remote team is not productivity tracking or time zones. It is knowing when someone is struggling before they tell you.
In an office, you catch it in seconds. Someone is quieter than usual in the standup. They stop eating lunch with the team. Their camera is off when it normally is on. Your body registers it before your brain explains it, and you pull them aside.
Remotely, all of that disappears. By the time a remote team member says “I am not okay,” the damage is usually three to four weeks deep. That is the real remote management problem, and almost every other challenge on the usual lists is a symptom of it.
I work with managers every week through Risely’s coaching data, and the same patterns show up across industries. The common remote-work advice (set KPIs, use Slack well, do virtual happy hours) stays at the surface. Below I have ranked the six challenges that actually break remote teams, in order of how often they show up in coaching conversations, with specific fixes for each.
1. You cannot see early warning signs
This is the root problem. Disengagement, burnout, confusion, conflict, personal difficulty: all of these announce themselves visually before they announce themselves verbally. Remote work strips the visual channel.
The consequence is that managers become reactive instead of proactive. You find out about the problem when it hits the work, not when it starts inside the person. A team member who would have been course-corrected in week one now gets a performance conversation in week six, and at that point they are already halfway out the door.
What to do
Replace visual cues with structured check-in questions. Not “how is everything going” (which gets “fine”) but specific ones that invite a real answer:
- “What is one thing slowing you down this week that I could help clear?”
- “On a scale of 1 to 10, how is your energy this week? What made it that number?”
- “Is there anything I am missing about how the team is feeling right now?”
Ask these every week in your one-on-one. The first few times you will get generic answers. By week four, you will start getting real ones, because the team member learns that the question is not performative. If you want a tighter structure, our one-on-one assessment scores the quality of your check-ins and shows where they are going shallow.
2. Expectations quietly drift
The second most common pattern I see is expectation drift. In an office, expectations get re-calibrated through a hundred tiny exchanges. Someone overhears a priority shift. You swing by a desk and say “actually, do this first.” A whiteboard updates.
Remotely, none of that happens by accident. If you do not explicitly re-align expectations, the team member is working off the expectations from your last formal meeting, which may be two weeks old. They are doing the right work for a world that no longer exists.
This is where “my team is underperforming” often lives. The team is not underperforming. The team is performing against stale instructions.
What to do
End every one-on-one with a 90-second re-alignment. Three questions, written down in a shared doc:
- What are your top two priorities for this week?
- What is lower priority than last week?
- What would make you stop and ask me before proceeding?
That last one is the most important. It prevents the “I thought you wanted X” conversation three weeks later. If writing these rhythms feels heavy, that is a signal that your management muscle needs reps, not that the rhythm is wrong. The art of delegation guide goes deep on how to hand off work cleanly without losing visibility.
3. Unaddressed conflict gets expensive
Remote conflict is different from in-office conflict. In a room, two people who disagree can escalate quickly, but they also de-escalate quickly because the non-verbal feedback loop is fast. Remotely, both the escalation and the de-escalation slow down. A terse Slack message can sit in someone’s head for 48 hours before they respond, and by then they have built an entire narrative around it.
The cost of slow conflict on a remote team is very high. You lose collaboration quality first, then trust, then retention. Managers usually notice at stage three, which is too late.
What to do
- When you see any tension sign in a written channel (a short reply, a passive-aggressive reaction emoji, a CC that feels pointed), move it to voice within 24 hours. Not Slack, not email. A call.
- In the call, name the tension out loud. “I noticed the thread this morning felt sharper than usual. What is going on?” Do not pretend it is not there.
- Do not mediate over text. Text makes people feel cornered. Get people on video, get the disagreement in the open, name what you heard, and ask both parties what resolution looks like.
For a full playbook on this, conflict resolution at work walks through the escalation ladder and the specific scripts I use.
4. Learning and mentorship collapse for junior team members
Senior team members usually do fine remotely. They already know the work, they have networks, and their learning is mostly self-directed. Junior team members fall off a cliff.
In an office, a new hire learns by osmosis. They hear the way people talk to clients. They see how someone handles a tricky Slack thread by looking over a shoulder. They learn judgment by absorbing a thousand small decisions. Remotely, all of that is invisible, and what replaces it is nothing, unless the manager builds a replacement.
This is the challenge most managers miss because it shows up slowly. A remote junior hire looks fine at 90 days. At 180 days, their growth has quietly flatlined and they do not know why.
What to do
- Assign a peer buddy, not just a manager mentor. Someone one level above them who they can ask questions without worrying about optics.
- Narrate your decisions. When you decide something in front of a junior team member, say the reasoning out loud. “I am saying yes to this because X, even though Y is a real concern.” That is the learning they are not getting by osmosis.
- Do shadow sessions. Let them sit silently in your calls for 30 minutes a week. They learn more from watching you handle a tough client than from any course.
- Review their writing. Not their work output, their writing. How they phrase a Slack message, how they write a client email, how they frame a project update. Remote work is writing-heavy, and written judgment is the skill most junior hires lack. Top skills for a new manager has more on this if you are newer to people management yourself.
5. Always-on culture replaces “presence” culture
In an office, presence is proxy for commitment. When a team moves remote, that proxy disappears, and most teams accidentally replace it with a worse one: response time. If you reply to Slack within two minutes at 9pm, you are committed. If you reply tomorrow morning, you are slacking.
This is how remote teams quietly burn out. Nobody calls it overwork because no one is pulling 12-hour days in a single block. They are just online all the time, in three-minute increments, for 14 hours. That is worse.
The manager is almost always the one who sets this pattern. If you reply at 10pm, your team will too.
What to do
- Write down your working hours and stick to them. Publicly. Put them in your Slack status and your email signature.
- If you have to work outside hours, use scheduled send. Nobody needs to see your 11pm Slack message at 11pm.
- Audit your own “red dot” behavior. If you cannot ignore a Slack notification for 90 minutes during focused work, your team will not believe they can either.
- Make “I am offline tomorrow” a normal sentence. Say it yourself. Model it.
6. Collaboration goes shallow
This one is last because it is the most visible and the most overblown. Yes, remote collaboration is harder. But the real failure mode is not lack of tools (everyone has Zoom and Slack and Notion). The failure mode is that remote collaboration defaults to shallow parallel work instead of deep interlocking work.
Two people on a remote team will each do 80% of a project alone and then stitch them together at the end. In an office, those two people would have bumped into each other ten times during the week and the work would be deeply interleaved. The stitched-together version is almost always worse, but the team does not know that because they have no in-office version to compare it to.
What to do
- Schedule working sessions, not just meetings. A “working session” is a 60-minute video call where you both have the doc open and actually write together. It feels wasteful. It is not.
- Use async-first for updates, sync for thinking. The inverse of what most teams do. Most teams use sync for updates (standups) and async for thinking (solo work then review). Flip it.
- Build in “weird time.” 20 minutes at the start of a team meeting for anything, including non-work. The office created weird time by accident. Remote teams have to create it on purpose.
In-office vs remote: what actually changes
The table below shows what stays the same and what has to change in your day-to-day. Most remote management mistakes come from assuming the habit transfers.
| Behavior | In-office manager | Remote manager |
|---|---|---|
| Reading the team’s mood | Absorb it passively by walking around | Ask specific questions in structured check-ins |
| One-on-one cadence | Biweekly often works | Weekly, 30 minutes, non-negotiable |
| Setting priorities | Re-align in hallway exchanges | Write down top two priorities every week |
| Catching a struggling team member | Notice body language change | Notice reply time, tone, and engagement drop |
| Onboarding a new hire | Osmosis handles 40% of learning | Narrate decisions, pair with a buddy, shadow calls |
| Resolving conflict | Move to a room, talk it out | Move from text to video within 24 hours |
| Working hours | Defined by office entry and exit | Defined explicitly in writing, modeled by manager |
| Building trust | Accumulates through presence | Built through predictability and follow-through |
| Collaborating on work | Happens by accident at desks | Scheduled as working sessions |
| Recognising good work | Quick hallway “nice job” | Written, specific, in public channels |
| Handling bad news | Same room, same time | Video call, same day, never text |
Notice what is not on the list: “tracking productivity.” That is not in the top six on purpose. In five years of coaching managers through remote transitions, productivity tracking has almost never been the real problem. Managers who obsess over it are usually compensating for one of the six above, and once those get solved, the productivity concern disappears on its own.
What most managers get wrong about the fix
The usual advice is “use better tools.” Pick Notion. Pick Slack. Pick Asana. Buy a time-tracker.
Tools do not fix any of the six problems above. What fixes them is a specific kind of manager behavior: being explicit about things that used to be implicit. In an office, a huge amount of management happened through osmosis, proximity, and body language. Remote work removes all of those channels. The manager has to replace them with writing, structure, and deliberate rhythm.
That is a real skill, and it is learnable. It is also the skill most managers do not get trained on, because the training industry still assumes everyone works in a shared space.
The 30-day reset
If you are taking over a remote team, or your remote team feels off, here is the reset I give managers in coaching:
Week 1: Run a one-on-one with each person. Ask one question: “What is working, what is not, and what do you wish I knew?” Do not defend anything. Just listen.
Week 2: Write down the top two priorities for each person, in a shared doc. Ask them to edit it. Re-align until the doc reflects reality.
Week 3: Set weekly one-on-ones at a fixed time. Announce working hours publicly. Audit your own Slack behavior against what you just announced.
Week 4: Start the structured check-in question rhythm from section 1. Pick one working session per team pair. Review the team energy level against where it was in week 1.
Four weeks is enough to see the shape of the team shift. Six weeks is enough for the team to trust that the shift is real.
Where to go from here
If you want to pressure-test where your remote management is breaking, our leadership assessment for managers includes a section on remote-specific behaviors and flags the two or three areas you are likely weakest in. It takes about 15 minutes and the report is sharper than most 360 reviews.
For ongoing support, Merlin is Risely’s AI coach. It handles the specific scenarios in this article (how to have the silence-on-Slack conversation, how to write a priority re-alignment doc, how to move conflict from text to video) in real time. Most of my coaching clients use it between our sessions when something comes up on a Tuesday afternoon and they need to think through the right move in 15 minutes.
If you want a deeper read on the management fundamentals that remote work exposes, start with the complete guide to effectively managing your team and the one-on-one meetings playbook. Remote work does not create new management problems. It amplifies the ones that were already there. The managers who handle it best are the ones who rebuild their habits from first principles, rather than trying to transplant office behavior onto a laptop screen.
You cannot manage a remote team the way you managed an in-office one. But you can manage a remote team well, if you are willing to replace what you used to get for free with structure you build on purpose.