Wrivio
Get Wrivio
5 min readBy Wrivio Team

How to Ask a Teammate to Slow Down Without Friction

A teammate is moving fast: shipping quickly, skipping steps, making calls without looping people in. You need them to slow down, and you know that saying so badly will land as “you are being reckless,” which turns a process concern into a personal one. This is one of the harder messages to write, because the content is a criticism of how someone works and the goal is to keep them on your side. The trick is to frame it around the shared risk rather than their behaviour, and to be specific about the one thing you want, not the general vibe.

Frame It As Shared Risk, Not Personal Fault

The difference between a message that lands and one that starts a fight is whether it is about them or about the work. “You are rushing and it is causing problems” is about them, and they will defend themselves. “I am worried we will miss something on this one if we move at this pace” is about the shared outcome, and it invites them to problem-solve with you.

Before:

You are moving way too fast and cutting corners, and honestly it is creating a lot of risk for the rest of us who have to clean it up.

After:

This one feels higher-stakes than usual, and I would feel better if we built in a review step before it ships. Could we add a quick check on Thursday before it goes out?

The second names a shared concern and proposes a concrete fix. The first assigns blame and invites a defence. Writing to avoid a fight is the whole point of how to write in a group chat without starting a fight.

Be Specific About What You Want

“Slow down” is vague, and vague feedback is both easy to dismiss and easy to take personally, because the person fills the gap with the worst interpretation. Name the specific thing: a review step, a heads-up before a decision, a day to test. A concrete, small request is easier to agree to and harder to read as a general indictment of how they work.

Acknowledge The Upside Of Their Pace

The person is moving fast for a reason, often a good one: momentum, a deadline, a bias for action you actually value. Acknowledging that is not flattery; it is accuracy, and it stops the message from reading as if you want to slow everything down. “I know we are trying to hit the launch, and I am not trying to stall it” tells them you share the goal and are only worried about one risk. The related skill of giving feedback on someone’s work is in how to give feedback on a colleague’s draft.

Pick The Private Channel

A “slow down” message in a public channel reads as a public correction, which almost guarantees a defensive response. This is a direct-message or a quick-call conversation. Raising a concern about someone’s work in front of an audience changes what it is, regardless of how gently you word it. Private and specific beats public and vague every time, and plain phrasing throughout keeps it from sounding like an accusation, which the plain language guidelines favour.

A Wrivio Context for this message could say:

Rewrite this to ask a teammate to add a check or slow down on one thing, framed as a shared concern about the work rather than a criticism of them. Acknowledge the value of their pace, name one specific request, and keep it warm. Keep every name and date exactly as written, and do not add complaints I did not make.

Press Ctrl+Shift+Space, paste your draft, and check that it reads as a concern you share, not a charge you are laying.

Common Questions

How do I tell a teammate to slow down without offending them?

Frame it as a shared risk to the work rather than a fault in them, acknowledge the value of their pace, and name one specific request like adding a review step, so it lands as a concern you share rather than a personal criticism.

Why does “slow down” land badly?

Because it is vague and sounds like a judgment of how they work, so the person fills the gap with the worst interpretation and defends themselves; a specific, small request about one step is easier to accept.

Should I raise it publicly or privately?

Privately, in a direct message or quick call, because raising a concern about someone’s work in front of an audience reads as a public correction and almost guarantees a defensive response however gently you word it.

Should I acknowledge why they are moving fast?

Yes, naming the good reason for their pace, like hitting a deadline, is accurate rather than flattering and shows you share the goal, which stops the message from reading as if you want to stall everything.

Download Wrivio for Windows to reframe a touchy “slow down” note as a concern your teammate will actually hear.