Reclaim Credit for Your Idea from a Coworker

This template is for the moment when a coworker presents your idea as their own in front of others, usually during a meeting or update. The learner practices correcting the record while the conversation is still happening. It is not a generic conflict template; the scenario is specifically about reclaiming credit without turning the meeting into an argument.

It is a good fit for individual contributors, project leads, and new managers who need to speak up when their work is misattributed. It also works for anyone who tends to stay quiet in the moment and then feels frustrated afterward. The persona is a peer, so the practice stays grounded in a realistic workplace power dynamic.

Use it whenever you want to build a steadier opening line and a calmer tone for real meetings. A few short attempts are usually enough to test different ways of naming the idea, the prior conversation, and the correction you want. Revisit it after a real incident or before a meeting where your work may be discussed.

Read the situation, start the conversation, and speak to Dana as if the meeting is happening now. Focus on naming the specific idea, referencing your earlier contribution, and asking for a simple correction to the record. Then review the rubric and retry with a cleaner, more concise version if needed.

It can support those conversations indirectly by helping you practice clear self-advocacy, but it is not a performance review or promotion negotiation template. The core use case is a live correction when credit is misassigned. If you need to discuss broader recognition patterns, that would be a different scenario.

Ad-hoc practice often drifts into vague conflict talk, which makes it harder to build a repeatable response. This template gives you a concrete situation, a specific learner objective, a reactive persona, and behavioral rubric criteria. That structure makes each attempt more useful because you can compare what changed from one run to the next.

Yes. You can swap in the actual meeting context, the exact idea, and the kind of rollout being discussed so the wording feels natural to your workplace. The same structure works in product, operations, client services, or internal process teams as long as the core issue is credit for an idea.

Avoid accusing language that turns the correction into a personal attack, such as saying the coworker stole your idea. Also avoid overexplaining or apologizing for speaking up, because that weakens the correction. The goal is to be specific, calm, and brief enough that the manager can update the record in the moment.

Yes. It pairs well with feedback, boundary-setting, and difficult-conversation practice because the same skills show up across those scenarios. If the issue becomes a broader pattern of credit-taking or team conflict, you can move from this template into a more general workplace communication or leadership scenario.