# A coworker keeps taking credit for my work. Is it petty to say something? - URL: https://www.agentskillpacks.com/guides/coworker-taking-credit-for-my-work - Updated: 2026-10-21 - Book: The Manipulator's Phrasebook by Iris Athens (https://www.agentskillpacks.com/books/the-manipulators-phrasebook) ## Short answer It is not petty to keep your name on your own work. You don't need to accuse anyone. The calm move is to claim your part warmly and add the next step, so it is plain whose idea it was. In a meeting, say that was what you were getting at earlier and share what comes next. After praise lands on someone else, offer to walk through the part that was yours. The habit that protects you most is boring: post short progress updates under your own name as you go. Work with a visible history is hard to walk off with. ## Monday stand-up, 9:15, eight little boxes Your manager asks about the new client dashboard. A coworker unmutes first. He got that across the finish line Friday night, he says. Took some wrangling, but it's live. You built that dashboard. You spent most of last week on it. He fixed one filter on Friday. Your manager says, "Great job." The meeting moves on. You think about speaking up. But it would sound petty. It's a stand-up. Nobody wants a fight over a dashboard at 9:15 in the morning. So you stay muted. After the call, he messages you. He mentioned the dashboard so they'd know the team shipped it. Hope that's cool. Exclamation point. You make a good team. ## Why staying quiet and being nice keeps backfiring The usual advice is to let your work speak for itself. Rise above it. The problem is that work doesn't speak. People speak about it. In most offices, credit gets handed out after the work is done, when someone reports on it. Whoever stands in that spot gets the credit, and the book says that is the shape of most coworker manipulation. It's rarely loud. He didn't lie, exactly. He did touch the dashboard. A coworker has no official power over you. He can't fire you or set your pay. So the pressure moves through other channels. The currency is credit. The market is being seen by the people who decide. And the main tool is a third person, usually the boss, who is always being quoted and never in the room. That is why "be nice" doesn't fix it. Being nice is fine. Being invisible is the problem. ## Claim it warmly, then make it visible The book's replies don't accuse anyone. They put your name back on the work and move on. That is the whole trick. When someone repeats your point ten minutes later, louder and smoother, as if he had said it first, the reply is: > "Yep, that's what I was getting at earlier. Glad it's landing. Here's the next step I had in mind." Having the next step ready makes it obvious whose idea it was. Afterward, a short note in writing helps: you are following up on the idea you raised in today's meeting. When praise lands on someone who says they "just pulled together what everyone sent," the reply is: > "Happy to walk through the analysis section, since that part was mine. There are a couple of details worth flagging." Offering to present your part is not bragging. It's a normal thing colleagues do. When a peer offers to "just send it over" for you because you're swamped: > "Thanks, that helps. Can you take the formatting? I'll send the final version myself." Accept the help. Keep the delivery. And the habit under all of it: post short progress updates in the team channel, under your own name, as you go. It's hard to walk off with work that has a visible history. It helps to stay calm in the moment, and that is harder than it sounds when your face is hot on a video call. A [2014 study by Ethan Kross and colleagues](https://doi.org/10.1037/a0035173) found that talking to yourself by name, or as "you," gave people more distance under stress. Try it silently before you unmute. ## Don't decide who he is, count what he does People really do forget where ideas came from. Meetings move fast. So the book asks you to watch for a pattern, not one slip. One sentence is data. Three are a pattern. The pattern looks like this: it's your ideas, specifically, that keep getting repeated by the same person, and his version is always the one in the notes. The visible parts of your work keep ending up in his outbox. Names only come up when something went wrong. We also don't ask you to label anyone. Research on darker traits, going back to [Paulhus and Williams in 2002](https://doi.org/10.1016/S0092-6566%2802%2900505-6), treats them as a scale that everyone sits somewhere on. A label stops you looking. A short log with dates and exact words keeps you looking. If the pattern turns into harassment or discrimination, keep records and talk to HR, or an employment lawyer if it is serious. ## Should you talk to him in private first? Many guides say yes, and it is a fair step once you see a pattern. [SHRM's Ask HR column](https://www.shrm.org/topics-tools/news/organizational-employee-development/ask-hr-colleagues-take-credit-for-your-ideas) (April 2025) suggests a short private talk in a curious tone. Ask, don't accuse. Its example line: > "Did you get a chance to mention it was something I'd floated?" Keep it that small. You are not asking him to admit anything. You are letting him know you noticed, and giving him an easy way to fix it. The same column puts your manager last. Go to her only if the problem keeps going after you have talked to him directly. When you do, stick to facts, like dates, what you built and what was said. Ask how to get your work seen, not for a verdict on him. Your short log makes this easy. ## When it happens in an email or the team chat Written credit-taking is easier to fix, because you can reply in writing too. The book's tool for tense work threads is BIFF, a method from Bill Eddy at the High Conflict Institute: Brief, Informative, Friendly, Firm. Answer with the facts and the next step. Leave out the feelings and the hints. A reply-all can be as simple as: > "Glad the dashboard is helping. I built the data model last week, so I'm happy to answer questions on it. Next step is the export view by Thursday." Before you send, read it as if your boss were reading it aloud. If a sentence sounds like a jab, cut it. A calm reply next to a vague claim makes the record clear without a fight. ## The chapter written for this This is the problem [The Manipulator's Phrasebook](/books/the-manipulators-phrasebook) was written for. **Coworkers** has 17 office lines in four groups: credit and visibility, triangles and secrets, the paper trail, and belonging and tone. Each one has a payload, an honest version, a reply and a pattern check. **The Calm Toolkit** gives you the sunlight move, which brings private side deals back into the shared space, and witnesses, which keeps important talks where others can see. **The Wrapper and the Payload** explains why "just trying to help" is such easy cover, and gives you a private log to start this week. If the person taking credit is your manager, our page on whether [your boss is manipulating you](/guides/is-my-boss-manipulating-me) covers that version. ## Where this is in the book - Coworkers - The Calm Toolkit - The Wrapper and the Payload Kindle: https://www.amazon.com/dp/B0HLGZ6XHL Paperback: https://www.amazon.com/dp/B0HM25N9BF Links go to Amazon. ToolGenX publishes this book under a pen name and earns from every sale. If you are afraid of someone, call the National Domestic Violence Hotline at 800-799-7233 or text START to 88788. ## Is the book for you? - Yes, if Someone keeps presenting your work as theirs in meetings - Yes, if You stay quiet because speaking up would sound small - Yes, if A peer keeps offering to carry your work to the boss - Skip it if You want a way to get back at the coworker - Skip it if You are facing harassment or discrimination and need HR or a lawyer ## FAQ ### How do you handle a coworker who takes credit for your work? Claim your part calmly in the moment, then follow up in writing. In a meeting, say it was what you were getting at earlier and give the next step. Afterward, send a short recap that names the idea you raised. Over time, post progress updates under your own name. ### Is it petty to correct a coworker who took credit? No. Putting your name back on your work is normal, as long as you do it warmly and without accusing. You are not attacking them. You are making the record match what happened. Being specific and calm keeps it from feeling like a fight. ### What do I say when a coworker repeats my idea in a meeting? Say something warm, like yes, that is what you were getting at earlier, glad it is landing, and here is the next step you had in mind. Having the next step ready makes it plain whose idea it was, and nobody has to be called out. ### What if a coworker always offers to send my work to the boss? Accept the help and keep the delivery. Thank them, ask them to take a smaller task like formatting, and send the final version to the boss yourself. If they push to give the boss the quick version, agree it should be short and send a two-line summary yourself. ### How do I protect my work from being stolen at work? Make it visible as you go. Post short updates in the team channel under your own name. Put your name and the date on documents before they travel. Send short recaps after meetings. Work with a visible history is very hard to reassign. ### When should I go to my manager about a coworker taking credit? Usually after the calm steps have not worked. SHRM's advice treats the manager as a last resort, for when the problem keeps going or gets worse after you have talked to the person. Bring facts, not complaints: dates, what you did and what was said. Ask for advice on getting your work seen, rather than asking for a ruling on your coworker.