MarkedUp career guides
How to Explain Your Role in a Team Design Project
A case study should make your contribution visible while giving credit to the people and constraints that shaped the work. Clear attribution is more credible than presenting a team outcome as an individual achievement.
Describe the team and your remit
Name the disciplines involved, your role, the project stage when you joined, and the decisions you were responsible for. If the project changed hands or your role shifted, give the relevant timeline. You do not need to list everyone; include enough context to explain who made which decisions.
Distinguish ownership, collaboration, and influence
- Owned: you were responsible for a defined deliverable or decision.
- Collaborated: you worked with others and can name the shared work.
- Influenced: your research, critique, or proposal informed a direction chosen by the team.
- Observed: you were involved, but did not make or deliver the work being described.
Use first person precisely
“I” can clarify your actions; “we” can preserve shared credit. Explain which applies to each important step. Illustrative wording for a fictional team: “I mapped the interview notes into themes with the researcher; the product team selected the onboarding direction after reviewing the evidence.” This shows your role and the decision boundary; replace it with what actually happened on your project.
Check whether the wording assigns credit fairly
Compare each “I” sentence with the project record or a collaborator’s recollection. If you created the prototype but another person ran the study, say so. If a team decision used your recommendation, describe the recommendation and the team’s decision separately. This distinction makes the case study more precise and gives an interviewer a natural path to ask about your actual work.
Protect confidential and sensitive work
Check what you are permitted to share before naming a client, showing a screen, or describing internal metrics. You can explain the nature of the problem and your process at a high level when details are confidential, but do not expose user data or claim permission you do not have.
Review the story with a collaborator
Ask a teammate to check whether the roles, sequence, and decisions are represented fairly. Their review is not a substitute for employer or client approval, but it can catch accidental credit inflation and missing context before you publish the case study.