Describe a team result with clear attribution: establish the shared context, identify your own action and label the outcome as collective. Keep responsibility for decisions, delivery and approval distinct. If the team result is difficult to verify or share, focus the CV bullet on your specific contribution and its supported output.
Separate three kinds of ownership
Team work often involves ownership of a task, influence over a decision and accountability for a result. These can belong to different people. Before drafting, list who did the work, who chose the approach and who approved the outcome. You do not need to name colleagues in a CV, but the distinction prevents verbs such as led or delivered from quietly overstating your role.
Create two short notes: what the team accomplished and what changed because of your particular action. The first provides context; the second supplies your career evidence. You may have tested one workflow, organized review comments or maintained a migration checklist. Those contributions can be substantial without implying that you directed the entire project or controlled the business result.
Choose a sentence structure that keeps attribution visible
One approach begins with your action and places the wider outcome afterwards: “Prepared the support handover checklist for a cross-team service launch.” Another begins with the shared result and qualifies your role: “Contributed to the service launch by preparing the support handover checklist.” Choose the structure that makes the relevant skill easiest to understand, while keeping the collective nature of the work explicit.
Be cautious with a large metric immediately following a small contribution. A reader may infer that your work caused the entire result even when the sentence contains the word supported. If a shared metric is essential, state that it belongs to the team and explain your bounded contribution alongside it. When space makes that distinction impossible, leave the metric for a longer case study or interview discussion.
Prepare to explain the handoffs
An interviewer may ask what happened before your work began, what another contributor did and how you handled disagreement. Prepare an account with those handoffs intact. Recognizing another person’s expertise does not weaken your own example; it helps demonstrate that you understand how the project operated. Keep the story centered on your decisions rather than speculating about the motives or competence of colleagues.
A useful rehearsal question is what would have been missing if your task had not been completed. Answer with the actual dependency, such as an untested handover, rather than claiming the whole project would have failed. This helps explain value without assigning yourself sole responsibility for success.
Check whether project names, internal results or collaborators may be disclosed. You can describe a generic service or department when identification is unnecessary. Do not publish a colleague’s work sample as your own evidence, even if you were part of the same team. A portfolio may show your portion, an approved composite or a clearly labeled reconstruction, with the limits explained where the reader encounters it.
Fictional example: a shared service launch
A fictional service team introduced a new appointment process. An operations assistant gathered front-desk questions, drafted a handover checklist and ran a rehearsal with two colleagues. A service manager chose the launch date, a developer changed the booking tool and trainers delivered staff sessions. The assistant’s first draft says “Led the new appointment-system launch,” which blurs those different responsibilities and is difficult to defend.
The revised entry says: “Drafted and rehearsed the front-desk handover checklist for a cross-team appointment-process launch, incorporating questions from service colleagues.” A longer portfolio note lists the team context and explains which materials the assistant authored. It does not claim ownership of the booking software or training program. The candidate can now discuss their judgment in organizing handover information while giving an accurate account of the wider work.
A checklist for your next step
- List your actions separately from collective outcomes.
- Check who made and approved key decisions.
- Use contribution verbs that match your authority.
- Attribute any shared result explicitly.
- Prepare a clear account of project handoffs.
Common questions
Can I say I led a task within a larger project?
Yes, if you actually coordinated that defined task. Name its boundary, such as leading a document review, so the reader does not infer responsibility for the whole initiative.
Should every team member appear in my CV?
Usually no. Describe the team context and relevant responsibility boundaries. A fuller case study may include approved credits, but personal names are unnecessary when roles explain the collaboration.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveCV.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.