How to give feedback remotely: Slack, async, or video

The feedback you'd give in thirty seconds walking out of a meeting together becomes, when your team is distributed, one of two failures. Either it never gets sent — because opening a channel specifically to raise something feels heavier than mentioning it in passing ever did — or it gets sent as a carefully composed four-paragraph Slack message that lands like a formal reprimand for something you considered minor. Remote work doesn't change what good feedback is. What it removes is everything that used to make feedback survivable without you noticing: your tone of voice, your face, the ability to see the flicker of reaction and immediately soften, and the shared understanding that you were both just in the same room. Take those away and the same words hit completely differently.

What distance actually takes away

Being specific about the losses makes the fixes obvious.

• Tone and paralanguage. In person, warmth is carried by voice and face, and it does most of the work of making a critical observation feel like help. Written text has none of it — so the receiver supplies a tone themselves, and under any uncertainty they'll supply a harsher one than you intended.
• Real-time reading of the reaction. In a room you see the wince and can course-correct mid-sentence: "—and honestly this is minor, I'm just flagging it." Async, you send and go dark, and the person sits with whatever they made of it, alone, with no correction available.
• Immediate repair. Face to face, misunderstandings get resolved in seconds. In writing, a misread waits — sometimes overnight, sometimes over a weekend — and hardens while it waits.
• Shared context. "That thing in the meeting" needs no explanation when you both just left it. Remotely, especially async across time zones, you often have to reconstruct the situation before you can even give the feedback — which makes short, casual, in-the-moment feedback disproportionately harder to deliver at all.

What distance genuinely gives you

It's not all loss, and pretending otherwise leads to bad advice. Written feedback lets you compose — you can be precise, avoid the vague summary that time pressure produces in person, and reread before sending. It creates a record the person can return to when they're ready to act, rather than half-remembering it. And it lets them process privately, without having to perform an appropriate reaction in front of their manager, which for some people is a substantial relief — the defensive reflex is much easier to ride out alone than across a desk. Nicholas Bloom's research on remote and hybrid work has consistently found that distributed teams do fine on execution and struggle on the relational and developmental parts — which is exactly where feedback sits, and exactly why it needs deliberate handling rather than good intentions.

Choosing the channel is the main decision

Most remote feedback goes wrong at channel choice, before a single word is written. A rough rubric that holds up well:

• Positive and specific → async text is ideal, sometimes better than in person. It's a keepable record, it costs the receiver no performance, and in a shared channel it scales. Do this often; it's also what keeps corrective feedback from being the only time you ever message someone directly.
• Corrective, small, purely factual → async text is fine. "The staging link in the doc points at the old build" needs no meeting. Keep it short, neutral, and about the artifact.
• Corrective and behavioral → video call, nearly always. Anything about how someone works, communicates, or comes across involves tone, nuance, and their reaction. Text is the wrong instrument, and a call that takes eight minutes prevents a misunderstanding that takes days.
• Anything you're tempted to write at length → that length is your signal. If the draft is getting long, you're compensating in writing for something that needs a conversation. Stop writing and schedule fifteen minutes.

That last one is the most useful rule in this article. Length reads as severity. A four-hundred-word message about a minor thing tells the receiver, structurally, that this is a serious matter regardless of how kindly it's phrased — because nobody writes four hundred words about something small.

The wall of text vs the right-sized message

Rules for feedback in writing

1. 1

   Say the scale out loud

   Because they can't read your face, tell them explicitly how big this is: "this is a small thing" or "this one matters, so let's talk." Absent that signal, people almost always assume it's bigger than you meant.
2. 2

   Keep it short and specific

   One observation, one concrete moment, one forward-looking ask. Resist adding evidence, caveats, or softening layers — each one lengthens the message and raises the perceived severity.
3. 3

   Drop irony, humor, and hedging

   All three flatten or invert in text. A joke meant to lighten a criticism frequently reads as contempt, and heavy hedging reads as bad news being cushioned. Plain and warm survives the medium; clever doesn't.
4. 4

   Never corrective in a public channel

   Positive feedback in public is a gift; corrective feedback in public is a punishment you didn't intend to administer. Direct message, or a call.
5. 5

   Mind the clock

   Don't send it end-of-day Friday or right before their holiday. They can't respond, can't ask, and can't resolve it — so they just carry it. If you're about to send at a dead time, save the draft.
6. 6

   Explicitly invite a response

   Close with a real opening — "tell me if I've read that wrong" or "happy to jump on a call." It restores some of the repair mechanism that distance removed, and it signals you're describing a situation rather than issuing a ruling.

Async makes the regular rhythm more important, not less

The deeper problem with remote feedback is frequency, not phrasing. In an office, small feedback happens constantly as a byproduct of proximity — you mention the thing while walking to the kitchen, and neither of you registers it as A Feedback Event. Remotely, that entire layer disappears, so feedback only occurs when someone deliberately decides to create an occasion for it. And people mostly decide that when something's wrong, which means remote feedback drifts toward being rare and negative — the exact combination that makes every instance feel like a verdict.

The counterweight is structure: protected space in your 1:1s so feedback isn't waiting on an occasion, and enough small positive feedback that a direct message from you isn't inherently ominous. MIT Sloan Management Review's work on distributed teams and candor keeps making the same point: what proximity used to supply for free, distance requires you to design. Without that design, the feedback drifts vague or stops entirely.

Where Mirorly fits

Now the direction that matters more for you: distance degrades the feedback you receive far more than the feedback you give. You see less of how you land — no hallway signals, no read of the room, no overheard reaction — and your team, already reluctant to critique their manager, now has to open a channel and compose something deliberate to do it. In practice that means almost nobody does. Mirorly is built for exactly this shape of problem, because it's async by nature: your team answers specific behavioral questions about how you actually work, on their own time, aggregated with an anonymity threshold so candour is safe, and repeated each quarter so patterns surface rather than one-off remarks. The core leadership behaviours template gives distributed teams a structured way to tell you what proximity would have shown you for free.

Common questions

The one-line summary

Remote feedback fails at channel choice and message size, not at wording: distance strips out tone, live reaction, and instant repair, so keep positive and small factual notes async, move anything behavioral to a call, state explicitly how big the thing is, keep it short (length reads as severity), never correct in public, and design a regular rhythm — because the casual layer that proximity supplied for free simply doesn't exist anymore.