You mention an idea in a team conversation.
You share a rough proposal with a colleague.
A week later, they present a working version to management. The room responds enthusiastically. They explain how they “came up with” the approach.
Your name never comes up.
For a moment, you barely hear the discussion. You are deciding whether to interrupt, wondering how it would look, and watching a story about your work take shape without you.
There are two things to deal with: the record of what happened, and what the experience brings up in you. Giving yourself space to understand the second can help you address the first.
Understand what you want restored
Before deciding what to say, finish this sentence:
“What hurts most is…”
Perhaps someone you trusted used your contribution without acknowledging it. Perhaps management now associates your idea with someone else. Perhaps you wanted the opportunity to lead the work.
Or perhaps another feeling sits alongside the unfairness: they moved faster than you did.
These experiences can overlap, but they point toward different requests:
- Missing recognition calls for accurate attribution.
- Lost involvement calls for a conversation about your role.
- Broken trust calls for clearer collaboration boundaries.
- Frustration about execution calls for examining what prevented your own next step.
You can learn from someone’s speed while still challenging how they claimed credit. Delivering quickly does not justify erasing another person’s contribution.
Be precise about what was yours
A useful starting point is to distinguish the original suggestion, the developed proposal, and the implementation.
“I once suggested improving onboarding” is a different contribution from “I designed the workflow, identified the bottleneck, and shared the prototype they presented.”
Likewise, a colleague who turns your proposal into a working system may have added substantial value.
A fair account can include both:
“I developed the initial approach and workflow. Alex built the implementation and prepared the demonstration.”
Review the relevant proposal, message thread, document history, or meeting notes. Establish what you contributed, when you shared it, and what was subsequently presented.
Also distinguish omission from an explicit false claim. “They did not mention me” and “They said they originated the proposal” may require different conversations.
Neither requires you to pretend the impact was insignificant. Precision gives you a stronger basis for asking for a correction.
Correct the record where it matters
If the meeting is still happening and you have clear evidence, a brief factual contribution may be enough:
“It’s good to see the workflow I proposed last Tuesday implemented so quickly. Alex has done valuable work building it. I can add some context on the original problem and design choices.”
Use language that matches your actual contribution. Avoid claiming the whole project if you contributed only one part.
If someone explicitly claims sole authorship, you can be more direct:
“I’d like to clarify the contributions. I developed and shared the proposal last Tuesday, and Alex implemented this version afterward. Both contributions should be reflected in the update.”
You do not need to settle the entire disagreement in front of stakeholders. A short correction can establish the relevant fact; the fuller conversation can follow.
If you froze or decided the setting was unsuitable, you can still address it afterward. Missing the moment does not mean accepting the account.
Ask for a concrete repair
For a private conversation, the Center for Creative Leadership’s Situation–Behavior–Impact framework offers a useful structure: identify the occasion, describe observable behavior, and explain its effect. Its extension adds a question about intent rather than assuming you already know it. Read CCL’s explanation.
Applied to this situation:
“In yesterday’s leadership update, you presented the workflow from the proposal I shared with you, but my contribution wasn’t mentioned. I’m concerned the stakeholders now have an incomplete understanding of my work. How did you understand our respective contributions?”
Listen to the answer. They may have assumed the background was known, misunderstood your role, or deliberately taken advantage. You do not have to decide their motive before requesting accurate attribution.
Then make the repair specific:
“Please clarify in the follow-up to that group that I developed the initial proposal and you led implementation. I’d also like us to agree on how we describe our contributions in future presentations.”
A private apology may matter personally. If the inaccurate impression reached management, ask for a correction that reaches the same audience.
Involve your manager when the issue persists
A direct conversation is an option, not an obligation in every circumstance. If the colleague has substantial power over you, has retaliated before, or repeatedly dismisses your contribution, consider seeking support from a trusted manager or an appropriate internal channel first.
When escalating, bring a short factual account and a clear request:
“I shared this proposal on 8 October. It was presented to the steering group on 15 October without attribution. I raised it afterward, but the record hasn’t been corrected. I’d like your help ensuring the project summary reflects our respective contributions and clarifying ownership of the next phase.”
Keep the focus on the work, the evidence, and the remedy. You do not need to prove that someone is a fundamentally dishonest person to establish that a specific account needs correcting.
Notice how the organization responds. Repeated misattribution that leadership tolerates may require changes to how you collaborate, who sponsors your work, or which opportunities you pursue.
Make future contributions easier to see
After this happens, withdrawing your ideas can feel protective. A more useful first step may be to make collaboration explicit.
When sharing a substantial proposal, document the problem, your proposed approach, and a next step. Agree on who will develop it, who will present it, and how contributions will be acknowledged.
For example:
“I’ll develop the concept and success criteria. You’ll lead the prototype. Let’s present the results together.”
You can also share concise progress updates with relevant stakeholders as the work develops.
These habits help make contributions traceable. Responsibility for deliberate misattribution still belongs to the person doing it; better documentation is a protective practice, not a condition for deserving credit.
And examine the speed question separately. Did competing priorities, missing authority, perfectionism, or unclear resources prevent you from moving? The answer may reveal something useful to change without excusing what happened.
Choose the next conversation deliberately
You may not obtain the acknowledgment you deserve. You can still identify your contribution accurately, request a proportionate correction, and decide what boundaries you need.
Before responding, write down:
What happened? What am I assuming? What feels threatened? What would a fair repair look like?
Then choose one action that serves that repair.
Before your next conversation, take a moment to reflect: What did I contribute? What recognition or responsibility matters to me? What specific correction will I ask for?
Explore these questions in a DeepMirror check-in, then use your answers to prepare a clear, factual request.
Sources and further reading
- Center for Creative Leadership. Use Situation–Behavior–Impact to Understand Intent. LinkedIn.
The workplace scenarios and suggested wording are illustrative examples. The hero image is AI-generated.