When discussing a team achievement in an interview or development conversation, it is easy to swing between taking too much credit and making your own role disappear. A precise contribution sits between those extremes.
Start with the shared outcome, then describe the part you owned. Name an action and a decision you made, using information you are authorised to share. Do not reveal confidential figures simply because a more detailed story sounds impressive.
For an invented example, “We launched a new reporting process” can become: “The team introduced a monthly report. I compared the old definitions, resolved two inconsistencies with the data owners and wrote the handover note.” The second version explains useful work without claiming responsibility for every part of the launch.
Include the boundary of your role
Mention whose approval or expertise the work depended on. This can show that you understand collaboration rather than diminishing your contribution. Distinguish suggesting a change from approving it and carrying it out.
If you discuss a result, explain how it was observed. “People used the handover note during the next cycle” is different from an unsupported claim that productivity improved by a particular percentage.
Practise a short version aloud and ask whether the listener can identify what you actually did. Remove jargon that hides the action.
You do not need to present yourself as the sole cause of success. A credible account of one consequential contribution gives a future colleague more to understand and ask about than a sweeping statement of ownership.
Editorial illustration from the site library.