Someone drops a task on you in the last two minutes of a meeting, says your name, and waits. You can feel the right answer forming, something like a clean no with a reason attached. What comes out of your mouth is “yeah, I can probably make that work.” The meeting ends, the task is yours, and you spend the walk back to your desk replaying the sentence you meant to say.
That gap, between the words you rehearsed in your head and the ones you actually produced under a little social pressure, is where most communication advice quietly gives up. Psychologists describe assertiveness as an adaptive style of communication where you express your needs directly while still respecting the other person, which sounds easy until a real person is looking at you and the clock is running. The real problem is that the moment arrives faster than your script does.
So this post skips the theory and hands you the words. Fifteen hard moments that push people into going passive or aggressive, each with the exact line to say. There is a well-known four-step conflict tool called the DESC script, taught in hospitals for its clean opener, and it’s genuinely good at getting you started. It just stops at the part where the other person pushes back, which is the part that actually decides how these go. So that’s where we’ll start.
Why assertive scripts fail: you cave on the second sentence
Most people can deliver the first line. You practiced it, you said it, it landed. Then the other person pushes back, “come on, it’s just this once” or “I really need this today,” and the wheels come off. You hear yourself start negotiating against your own position: “well, I guess if it’s urgent.” The opener was never the hard part. The reply after the pushback is.
Here’s the mechanic that holds. When they push, you do three things and only three: acknowledge that you heard them, repeat your ask in the exact same words, and offer the next step. You do not add a new reason. Every fresh justification you volunteer is a new thing for them to argue with, and it signals that your no is a door rather than a wall.
The shape is always the same. “I hear that this is urgent. I still can’t take it on today. What I can do is send you the two people who can.” Notice what’s missing: no apology stacked three deep, no invented excuse, no “but if you really need me to.” You’re not louder than your opener. You’re just unmoved by it.
That is the whole game. People who read as assertive are rarely the ones with the best opening line. They’re the ones who can say the same reasonable thing twice without their voice climbing half an octave. Every one of the fifteen scripts below comes with its own pushback line for exactly this reason, because the second sentence is where the moment is won or lost.
The same words land differently on a peer, your manager, and a skip-level
One adjustment changes whether any of these scripts actually work. Assertiveness is not a fixed volume you set once. The same sentence reads as confident to one person and reckless to another, depending on who holds the power in the room.
With a peer, lead with plain directness. Wrapping a simple no in four layers of apology reads as an opening bid, and a peer will negotiate it. Say the ask flat and stop talking.
With your manager, attach the ask to a trade-off they care about. Managers are holding a stack of priorities you can’t fully see, so a bare no can read as you opting out of the stack. Give them the decision instead: “If I pick up the audit, the launch doc slips to Monday. Which do you want first?” You’ve been direct, and you’ve handed them the lever.
With a skip-level or a leader two rungs up, keep it short and don’t route around your own manager. Length reads as nerves at that altitude. Make your point in a couple of sentences, and loop your manager in rather than surprising them later.
This is why “just use I-statements” falls apart. The words are the easy part. Aiming them is the skill. If you’re not sure whether you default to passive or aggressive when the pressure lands, a short oral communication assessment will show you where you tend to start from.
Protecting your time: 4 scripts for when work lands on your plate
The fastest way to end up buried is to be the person who never makes the cost of yes visible. These four moments share a tell: staying quiet reads as agreement, so silence is the passive choice you didn’t know you were making.
1. A task gets handed to you in a meeting and the room goes quiet
You freeze because the silence has a clock on it. Every second you don’t answer, the group reads as a yes, and speaking up now feels like making a scene in front of eight people.
Passive: “Sure, I can probably fit that in.”
Aggressive: “Why is this landing on me? I’m already buried.”
Assertive: “I can own that. To do it well, I’d need to move the Henderson deck to next week. Does that trade work, or should this go to someone with more room?”
If they push back: “I hear it’s a priority. That’s exactly why I don’t want to half-do it between other things. Which one should slip?“
2. A colleague asks for a “quick favor” that will eat your afternoon
The word “quick” is doing quiet work here. It frames a real request as a small one, so declining feels like you’re being difficult about something trivial, even though your gut already clocked it as a lost afternoon.
Passive: “Yeah, no problem, send it over.”
Aggressive: “That’s not a quick favor, that’s basically your whole job.”
Assertive: “Happy to help, though that’s more like a two-hour job than a quick one. I can get to it Thursday, or I can point you to the template that does most of it right now.”
If they push back: “I get that it’s time-sensitive. Thursday is the honest answer for doing it properly. The template is the faster route today.”
3. New scope lands on you in a public Slack or Teams channel
This one has an audience. Someone types “can you also take the billing integration? @you” into a channel with twenty people, and the public setting makes a private worry feel impossible to raise. The pull to just react with a thumbs-up and move on is enormous.
Passive: a thumbs-up react, and now it’s yours.
Aggressive: “This keeps happening. Stop volunteering me for things.”
Assertive: “Happy to take the billing integration. Flagging that it lands on top of the reporting work due Friday, so one of them moves. @Sam, which do you want first?”
If they push back: “Totally can. I just don’t want to quietly drop the Friday deliverable to do it. Your call on the order.”
A channel is not the place for a long defense. Keep the written version short, name the trade-off, and put the decision back on the person who owns priorities. For the wider skill of writing so a message settles a thing instead of starting a forty-reply thread, our guide to async communication that doesn’t spark a meeting walks through the templates.
4. You’re stuck in a standing meeting that stopped being yours
You keep attending because leaving feels like a statement, and you’re not sure you’re allowed to make it. So you sit through ninety minutes a week that no longer touches your work, and you resent it in silence.
Passive: attend anyway, camera off, half-listening.
Aggressive: “This meeting is a waste of my time.”
Assertive: “I don’t think I’m adding much here anymore now that the project moved off my plate. I’d like to drop the standing invite and catch up async instead. Grab me for a specific topic if you need me back.”
If they push back: “Fair, I can stay on for the parts that touch my work. Can we make my attendance by-agenda rather than default?”
Defending your work and credit: 4 scripts for when someone takes what’s yours
Nothing turns a steady person aggressive faster than watching their work get claimed by someone else. The trick is to correct the record without sounding like you’re keeping score, because the second you sound bitter, the room stops hearing the facts and starts watching the friction.
5. Someone repeats your idea as their own and the room nods
Calling it out feels petty, and pettiness is the exact accusation you’re afraid of. So you sit on it, and by tomorrow it’s quietly become true that it was their idea.
Passive: say nothing, replay it on the drive home.
Aggressive: “That’s literally what I said ten minutes ago.”
Assertive: “Glad this is landing, it’s the direction I floated earlier. Building on it, the open question is how we staff it.”
If they push back: “We’re on the same page then. I just want to keep track of where it started so the follow-up lands with the right people.”
6. Your manager credits your win to the team, or the wrong person
This one stings because you can’t argue with “great team effort” without looking small, and correcting your own boss in the moment feels like a career risk. So the specific thing you did dissolves into a group blur.
Passive: smile, let it go, hope they noticed privately.
Aggressive: “Actually, that was me, not the team.”
Assertive (later, one-on-one): “Quick thing from the review. I’m glad the migration got a shout-out. I led that one end to end, and I’d love for that to be visible for promotion conversations. Can we make sure it’s logged as mine?”
If they push back: “I’m not trying to take it from the team. I just want the record to reflect what I actually owned, because that’s what these reviews decide.”
7. A teammate takes credit in a thread while others watch
The written version is trickier than the in-person one, because everything you type is permanent and forwardable. Fire off something sharp and you’re the difficult one on record. Say nothing and the thread becomes the history everyone refers back to.
Passive: let the thread stand, correct it in your head.
Aggressive: “Weird, since I’m the one who actually built this.”
Assertive: “Nice to see this launch. For anyone picking it up later, Dan and I split it, and I built the forecast model and the rollout plan. Happy to walk through that half.”
If they push back: “Not a big deal, just tagging the ownership so the right person gets pinged for the forecast questions.”
The move in writing is to claim your part by being useful, not wounded. You’re the person who knows the forecast half, so make that the reason your name belongs on it.
8. You’re being blamed for a miss that wasn’t yours
The instinct is to defend yourself fast and hard, which is exactly what makes you look guilty. You freeze between that hot defense and the passive urge to just absorb the blame so the discomfort stops.
Passive: “Sorry, I’ll fix it,” for something you didn’t break.
Aggressive: “That’s not my fault, go talk to Dev.”
Assertive: “Let me untangle what happened. The spec changed on the 12th, after my part shipped, so the gap came in downstream. I’m happy to help fix it, and I want us clear on where it actually started so we don’t wire it the same way twice.”
If they push back: “I’m not dodging it. I’m pointing at the step that broke so the fix actually holds. Let’s look at the timeline together.”
Disagreeing up the chain: 4 scripts for pushing back on someone senior
Disagreeing with someone who has power over your next review is where assertiveness gets genuinely hard, and where most people either go silent or overcorrect into sounding insubordinate. The aim is to be the person who raises the risk early, not the one who says “told you so” later. If you want to see how you handle friction with authority in general, that’s the habit a conflict resolution assessment is built to surface.
9. Your manager makes a call you think is wrong and asks “sound good?”
The question is a trapdoor. “Sound good?” invites a yes, and disagreeing now means slowing down a decision your boss clearly wants to close. So you nod, and you own a plan you don’t believe in.
Passive: “Yeah, sounds good.”
Aggressive: “I don’t think that’s going to work at all.”
Assertive: “Mostly, with one flag. If we ship without the fallback, my worry is we’re one outage away from a bad week. Can I take ten minutes to show you the risk before we lock it?”
If they push back: “You might be right that the odds are low. I’d just rather you make that call seeing the downside than not. Then I’m fully on board either way.”
10. A senior leader’s plan has a flaw and the room stays silent
Everyone can see it and nobody wants to be the one, because pointing at the gap in a VP’s plan feels like volunteering to be wrong in public. The silence turns into its own pressure to keep quiet.
Passive: nod along, mention your doubt to a peer afterward.
Aggressive: “This plan doesn’t account for the vendor timeline at all.”
Assertive: “This looks strong. One thing I want to pressure-test: the timeline assumes vendor sign-off by week two, and last time that took six. If that repeats, what’s our move?”
If they push back: “Happy to be wrong on the timing. I’m raising it now because it’s cheap to plan for and expensive to discover in week three.”
11. You’re handed a deadline you already know is impossible
Saying it can’t be done sounds like admitting you’re not good enough to do it. So you take the date, privately knowing you’ll miss it, and trade a hard conversation now for a worse one later.
Passive: “I’ll try to make it work.”
Aggressive: “That’s not happening, nobody could do that by Friday.”
Assertive: “Friday isn’t real for the full scope, and I’d rather tell you that now than on Thursday night. I can get you the core flow by Friday and the edge cases by Tuesday, or the whole thing done right by Wednesday. Which version do you want?”
If they push back: “I hear the pressure is real. That’s why I’m giving you the honest date instead of a hopeful one. Pick the trade and I’ll hit it.”
12. The decision’s already made and you still disagree
This is the one people handle worst, because the meeting is over and reopening it makes you the person who can’t let go. So you either sulk through the execution or snipe about it in side channels, both of which cost you more than the disagreement ever would.
Passive: go quiet, drag your feet on the rollout.
Aggressive: “For the record, I still think this is a mistake.”
Assertive: “I pushed for the other option and I lost that one fairly, so I’m in. One ask: can we set a checkpoint in three weeks to see whether the risk I flagged is showing up? If it isn’t, great, I’ll happily be wrong.”
If they push back: “I’m committed either way, that’s not the question. I just want a date where we look at the numbers instead of arguing from opinion.”
Holding boundaries with people who don’t take the hint: 3 scripts
Some people adjust the moment you give them a soft signal, and this section isn’t about them. It’s about the ones who treat every polite no as an opening offer, where the skill shifts from being clear once to being clear repeatedly without tipping into a fight. That last part matters, because the person who keeps pushing is often hoping you’ll lose your temper so the story becomes about your reaction instead of their behavior. Our guide to de-escalation techniques at work goes deep on staying steady when someone is trying to pull you off balance.
13. A colleague keeps talking over you in meetings
By the second interruption you’ve done the math: fighting for the floor looks worse than losing it. So you lose it, again, and over months the pattern hardens into “that’s just how meetings go.” The cost is that your ideas keep arriving in someone else’s mouth.
Passive: stop talking, let them have it, raise it never.
Aggressive: “Can you let me finish for once?”
Assertive (in the moment): “Hold that thought, I’m going to finish my point first.” Then finish it, same tone, no rush.
If they push back or keep going: “I let you make your full point. I’d like the same thirty seconds.” Said evenly, it lands as a norm, not a complaint.
Holding the floor calmly is downstream of actually hearing people, which is why the steadiest interrupter-handlers tend to be strong listeners too. For a read on that half of it, an active listening assessment is a fast gut-check.
14. Someone DMs you after hours and expects a reply
The blue dot says you’re online, and the message just sits there, implying that a good teammate would answer. Reply once and you’ve taught them the boundary doesn’t exist. Ignore it and it feels passive-aggressive. So you answer at 9 PM and quietly resent it.
Passive: answer right away, every time, and train them to expect it.
Aggressive: “It’s 9 PM. This can wait.”
Assertive (next morning, not that night): “Saw this came in last night. I’m generally offline after six, so I’ll always catch these first thing. If something’s truly on fire, call me and I’ll know it’s real.”
If they push back: “Totally fine to send them whenever works for you. I’ll just answer during hours unless it’s an actual emergency, which is what the call is for.”
The boundary is set by when you reply, not by what you say about replying. Answer the next morning even once and that does more than any speech about work-life balance.
15. The person who “forgets” every boundary you’ve set
By the third time, you know it isn’t forgetfulness, and that’s what makes this one hard. Naming a pattern feels like a bigger accusation than flagging a single slip, so you keep treating each violation as the first one, and they keep counting on exactly that.
Passive: restate the same gentle no, again, hoping it sticks this time.
Aggressive: “How many times do I have to tell you?”
Assertive: “This is the third time the design’s gone out without my sign-off. I want to name it as a pattern, not a one-off. Going forward, I need to see it before it ships. Can we agree on that as the rule?”
If they push back: “I’m not looking to relitigate the past ones. I’m asking for one specific change from here: my eyes on it before it goes out. Are we agreed?”
Naming the pattern is the whole move. A single no is easy to wave off as a misunderstanding. “This is the third time” makes the pattern the subject, and patterns are much harder to shrug off than moments.
Rehearse the exact moment before you’re in it
Reading a script and saying it out loud to a person who’s frowning at you are two different skills, and the space between them is where the good line dies in your throat. The fix is reps.
Merlin is an AI coach that lives inside Slack and Microsoft Teams, and one of the most useful things you can do with it is run a hard conversation before the real one. Tell it the situation, tell it who you’re talking to and how that person usually reacts, and have it play the other side, pushback included. You get to blow the first attempt in a room where nobody’s watching, adjust, and walk into the actual moment having already heard yourself say the words once. Practicing the pushback is the part that sticks, because that second sentence, the one you were always going to fumble, is now one you’ve already run.