You worked on a project with several people and owned part of the work. “Participated in the project” says too little, but claiming the entire outcome as your own says too much.
Keep the team result as context, then explain your responsibility, actions, and confirmed deliverables. You do not need to calculate your percentage of the credit or prove that you could reproduce the same outcome at another company.
Separate three kinds of information
- Team context: What problem did the project address, and what stage did it reach?
- Your responsibility and actions: What did you deliver, coordinate, or decide?
- The confirmed output or change: What did you complete, and how was it used?
Team size, budget, and overall performance can explain the setting. They do not establish your individual contribution on their own. Carrying out an agreed plan can also be valuable work; it does not need to be relabeled as leadership.
Example 1: make execution specific
These three examples illustrate writing choices. They are not reported customer, project, or hiring outcomes.
Original: Participated in a store system launch to support business operations.
Suppose the team migrated 20 stores. Under the project plan, you handled account checks, staff training, and issue logging for 6 of them, and those 6 stores completed the transition.
Revised: Supported 6 stores in a team rollout covering 20 locations, handling account checks, staff training, and issue logging through their transition to the new system.
This does not claim that you designed the whole plan or delivered the entire rollout. Your scope and work are specific enough to understand.
Example 2: coordination does not need a revenue figure
Original: Coordinated engineering and support, significantly improving issue-resolution efficiency.
Suppose customer issues were scattered across chat threads. You collected the issues, reproduction steps, and resolution statuses in a shared list that both teams began using. You have no measurements of time saved.
Revised: Created a shared list of customer issues, reproduction steps, and resolution statuses for engineering and support to use in follow-up.
The shared list being used is a result. It does not need an invented efficiency percentage. See Resume Achievements Without Metrics for other forms of evidence.
Example 3: show what you managed
Original: Led the team to successfully deliver a key project.
Suppose you led a four-person team through a knowledge-base migration. You assigned work, checked progress, and organized acceptance reviews. The migration was completed, and support staff began using the new knowledge base.
Revised: Led a four-person team through a knowledge-base migration, assigning work, tracking progress, and organizing acceptance reviews; the new knowledge base is now used in daily support work.
A manager can describe the team’s delivery while making their own organizational responsibilities clear. There is no need to claim every task personally or add an unverified increase in satisfaction.
Choose “contributed,” “owned,” or “led” to match your role
A stronger-sounding verb is not always more informative. “Responsible for” followed by a clear scope can say more than an unsupported “led.”
- After “contributed to,” explain which part you worked on.
- Use “responsible for” or “owned” when you can define the responsibility you held.
- Use “led” when you actually provided the relevant direction, coordination, or decision-making, and can explain what that involved.
“Co-developed” can also describe shared work accurately. The question is whether the wording could mislead someone about your authority or contribution.
What if you cannot isolate an individual metric?
If team revenue increased but you cannot establish how much your process change contributed, do not attribute all the growth to your action. Include the team context when it helps and describe your work separately. Omit the total when it adds little to the reader’s understanding.
“I was responsible for 6 stores” is different from “I created 30% of the project’s value.” Records can establish scope; attribution needs additional evidence. Read How to Use Numbers Accurately on Your Resume for the distinction.
Ask someone outside the project to read it
Can they identify the project, your part, and the team’s shared work? If they can only tell that the project was large, add your contribution. If they think you completed everything alone, clarify the wording.
For help choosing projects and deciding where they belong, read How to Write Project Experience on Your Resume.