Handle a colleague who takes credit
Plans a response when a colleague takes credit for someone's work, from preventive visibility habits to a direct conversation and when to involve a manager, with exact phrasing.
Credit-taking ranges from careless ("I" when it should have been "we") to deliberate and repeated. The response should match: most cases are solved by making your contribution visible as it happens and by a calm, factual private conversation, not by a public challenge. Escalating to a manager makes sense when it repeats after a direct conversation, when it affects reviews, pay or promotion, or when the colleague is senior enough that a direct conversation is risky; even then, the framing that works is "I want my manager to see my contribution accurately", not "they are a thief". Public accusations, reply-all emails and retaliation usually cost the person who was wronged more than the one who took credit.
Help me handle a colleague who took credit for my work.
Only if [EVIDENCE] is given:
- Read the situation fairly: how clear the credit-taking is (careless wording, ambiguous shared work, or clear misattribution), whether it is a pattern, who was affected (my manager, leadership, a client), and what is at stake for me. If the work was genuinely shared or the evidence is thin, say so and lean towards prevention and a light clarifying conversation rather than confrontation.
- Prevent: four or five visibility habits that suit my situation, such as short written updates to my manager, sharing work in team channels with my name on it, agreeing roles and presenters before a joint piece of work, and presenting my own work where possible.
- In the moment: three calm lines I can use when it happens again in a meeting or email, which add my contribution without accusing anyone ("Glad that landed. I can take questions on the model, since I built it.").
- The direct conversation: unless the relationship makes it unsafe for my career, script a private conversation: a neutral opener, the specific instance described factually, the impact, the request for the future (for example naming contributors in updates, agreeing who presents), and replies to likely pushback ("it was a team effort", "I didn't mean anything by it", "you're being petty").
- Adapt to the relationship:
- peer: a direct conversation first;
- senior: lead with visibility to my own manager and a lighter, curious conversation; avoid confrontation;
- junior: treat it as coaching about attribution, while still making my contribution visible.
- Involving my manager: when it is justified, and a script focused on accurate visibility of my work and the facts, bringing evidence, not on the colleague's character. Mention HR only if the credit-taking is part of discrimination, harassment or retaliation.
- Don't: what to avoid and why.
- Phrasing must be calm, specific and factual. No sarcasm, no public call-outs, no accusations about motive.
- Use only the facts I gave; mark anything I should check with
[check: …]. - Keep scripts short enough to say naturally.
- Do not promise outcomes; workplace politics vary.
Read of the situation
Three or four lines, including how clear-cut it is and the recommended level of response.
Prevent
Four or five bullets.
In the moment
Three lines in quote blocks.
The direct conversation
Opener, the facts, the impact, the request, and pushback replies, as short quoted lines.
Involving your manager
When, and a short script.
Don't
Three or four bullets.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Interpersonal communication
- level
- Beginner
- made for
- Anyone, personal use, Software engineer, Product / UX / UI designer, People manager
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install handle-credit-taking-colleague --target claude-codeThis entry is in the full catalog, not the curated set the skills installer and plugins carry, so install it with the Hodios CLI.
pairs well with
All of Interpersonal communicationGive feedback with SBI
Turns a reaction into specific, kind feedback using situation, behaviour and impact, adds a clear request and an invitation to respond, and strips out judgements and assumed motives.
give-feedback-sbiGive feedback to your manager
Prepares feedback to a manager or senior colleague with what to say, framing around shared goals, when and where to raise it, and how to respond if they get defensive.
give-upward-feedbackPrepare for a difficult conversation
Prepares a difficult conversation with realistic goals, an opening line, the other person's likely view, phrases to use and responses to pushback, and points to help instead when safety is at risk.
prepare-difficult-conversationWrite a weekly update to your manager
Turns a messy week of notes into a short update for one's manager, covering outcomes against priorities, blockers with specific asks, risks and next week's focus, as an email, chat message or bullets.
write-weekly-update-to-managerCommunication coach
Communication coach who helps people say hard things clearly and kindly, rehearses real conversations with them, and teaches listening as much as speaking, at work and at home.
communication-coachApologise effectively
Writes a sincere apology that names the specific impact, owns it without excuses or conditional wording, offers repair and says what will change, fitted to the relationship and channel.
apologize-effectively