Difficult Conversations at Work: Scripts for Credit-Stealing, Scope Creep, and No
Word-for-word language for the three conversations that tax women's careers most — reclaiming credit without sounding petty, repricing scope creep instead of absorbing it, and a no that closes the topic. Plus the escalation ladder for when scripts aren't enough.
Educational, not advice. Capital Diva publishes information about careers and earning — not financial, investment, legal, tax, or individualized career advice. Figures cite their source and year; laws change. Read the full disclaimer.
Every workplace has a hidden tax system. Credit quietly reassigned, scope quietly added, requests quietly assumed to be yes — none of it dramatic enough to name, all of it compounding against your pay and your promotion case. And it compounds against some people more than others: with women’s median weekly earnings at 82 cents on the men’s dollar in mid-2026 per BLS data, the price of absorbing these taxes quietly is not evenly distributed.
The counter-tool is not courage, exactly. It’s preparation — specific words, chosen calmly in advance, for moments engineered to catch you off-balance. What follows are the scripts I actually use for the three most common taxes, with the design notes on why each line is built the way it is, because you’ll need to adapt them to your own voice for them to survive contact with real life.
Tax #1: Credit-stealing
The scenario: your analysis, your idea, your late nights — presented in the meeting, by someone else, in first person singular. The wrong responses are the two extremes: silence (the org chart quietly records the wrong author) and visible fury (the room remembers your reaction, not your authorship).
In the room, within minutes — the reclaim-and-build:
I'm glad this is landing — when I built the model, the piece I found most surprising was the retention effect, so let me add some context on how that works…
The engine here is casual authorship plus new detail. “When I built the model” re-attributes without accusing anyone of anything, and immediately demonstrating deeper knowledge makes the authorship self-evident. No one can gracefully object to you adding context to “their” idea — and if they know more than you about your own work, it was never stealing.
Afterward, if it’s a pattern — the private naming: “I’ve noticed the last two times my work went up the chain, my name didn’t go with it — the pipeline model last month, the pricing memo Tuesday. I want to assume that wasn’t deliberate, so I’m flagging it: I need my work attributed. How do we make sure that happens going forward?” Specific instances, an off-ramp for their dignity, a direct need, a question that hands them the fixing. And from that day, run the paper trail: work shared by email with your name in the file, summaries sent after meetings — the same receipts habit that feeds your promotion case makes credit theft structurally harder. Prevention beats reclamation: I now send a two-line “here’s the deck, happy to walk anyone through my methodology” note before big meetings, which quietly timestamps authorship to the whole room.
Tax #2: Scope creep
Somewhere between “can you just” and month four, you’re doing a second job for free. The count matters more than the feelings, so before any conversation, spend twenty minutes listing what you actually own now versus your role as written. Then — and this is the reframe most advice misses — treat the conversation as a repricing, not a complaint:
I want to look at my scope with you, because it's grown in a way I think is worth making official. Since March I've taken on vendor management, the intern program, and the weekly exec report — I've been glad to step up, and I think it's gone well. I'd like us to either formalize this scope in my role — title and compensation reflecting it — or decide together what comes off my plate so the core role stays excellent. Which direction makes more sense from where you sit?
Notice what this refuses to do: it never says “overwhelmed,” which converts a pricing problem into a capacity problem and invites “let's work on your time management.” The two-door close is the load-bearing wall — pay for it or reassign it — and either door is a win: formalized scope is a raise case, and reassignment is your evenings back. The failure mode to expect: “let's revisit in a quarter.” Accept once, with a date in the calendar and the scope list in a follow-up email. A second deferral means the answer is no, and no is information — take it to your review-season case or your resume, but stop paying the tax silently.
One honest caveat: repricing works when the scope is genuinely valuable. If what crept onto your plate is undifferentiated glue work — notes, ordering lunch, the office-mom portfolio — formalizing it prices you into a role you don’t want. For that flavor, use door two only: “I can keep doing the meeting notes, or the analysis due the same hour — which would you rather have from me?” Make the trade-off theirs to hold.
Tax #3: The missing no
Every yes is a no to something invisible — usually your own priorities, your first-90-days momentum, or your evening. The no that works has three properties: it’s fast (a slow no burns goodwill twice), it’s clean (over-explained refusals invite negotiation of your reasons), and where possible it prices instead of refuses:
- The priority no: “I can’t take that on and protect the Q4 launch. If this is more important than the launch, let’s decide that together with [manager] — otherwise I have to pass.”
- The clean no (for the recurring favor that became an expectation): “I can’t keep owning this — I need to hand it back after this week. Happy to write up how I’ve been doing it.”
- The priced yes: “Yes, if we move the deadline on X” / “Yes, as the formal lead on it, not a helper.” A yes with a price is a no that pays you.
The delivery mechanics that make scripts work
A script is sheet music; delivery is the performance, and three mechanics decide whether the same words land as calm authority or as nerves:
Rehearse out loud, twice, before the real thing. Not in your head — your head lies about how sentences sound. Say the credit-reclaim or the repricing to a mirror, a friend, or your parked car. The first pass always exposes a phrase your mouth won’t say naturally; swap it for your own words. The second pass is for pace: nervous scripts accelerate, and speed reads as apology. If you have a trusted person, have them play the difficult counterpart uncharitably once — hearing “let’s revisit in a quarter” in rehearsal means it can’t wrongfoot you live.
Let silence do its half of the work. Every script above ends with either a question or a clean stop. What follows is the counterpart’s turn — and the strongest delivery error is filling their silence with softening: “…I mean, it’s not a big deal, I just thought—” That postscript un-says the script. Deliver the last line, close your mouth, and count the wallpaper if you have to. Five seconds of quiet after “which direction makes more sense from where you sit?” is not awkwardness; it’s the question working.
Pick the venue like it matters, because it does. Rung-one scripts belong in the moment, in the room. Rung-two conversations belong in a private 1:1 you schedule — never ambush someone at their desk with an audience, which converts your reasonable ask into their public loss of face, and their face becomes the topic instead of your issue. And afterward, for anything on rung two or above, send the two-line summary email the same day: “Thanks for making time — capturing what we agreed: attribution on shared work going forward, and we’ll check in on it at month-end.” Polite, factual, and quietly the beginning of your documentation trail — the ladder’s next rung, pre-built while everything is still friendly.
When scripts aren’t enough: the ladder and your rights
A script assumes a counterpart who responds to social pressure. Some situations — a manager who retaliates, harassment, systematic discrimination — are not script problems, and pretending otherwise wastes months. Two things worth knowing cold: first, documentation started early (dates, instances, witnesses, kept off employer systems) is what separates “concerns” from “a record” if you ever need rung four. Second, some of these conversations carry legal protection — notably, discussing pay with coworkers is protected concerted activity for most private-sector employees under federal labor law, per the National Labor Relations Board, and a policy telling you otherwise is itself the problem. Comparing notes is often how every one of these taxes gets discovered.
A last honest note: I’ve had these scripts fail. The repricing script, delivered well, once got me a warm smile and eight more months of unpaid scope — because the real answer was that the company priced me exactly as low as I’d let it. The scripts’ deepest value isn’t that they always win the moment; it’s that they generate clear data fast. A workplace that responds to calm, specific, reasonable words with nothing is telling you the tax rate is permanent. The same preparation that powers a negotiation script powers these — and the same rule applies: the words open the door, and the willingness to act on the answer is what makes them heavy.