Role & Contribution
How to present your role and personal contribution in collaborative work so viewers can see what you owned, what decisions you influenced, and what value you created.
A title is not enough
Product Designer, Project Lead, Developer, or Consultant are categories. People with the same title can create very different value.
Role: define responsibility
Role answers: What were you expected to own? Discovery, UX direction, architecture, stakeholder alignment, delivery, measurement, or coordination.
Contribution: define the value you created
Contribution asks: What would not have happened in the same way without your involvement? It may be an insight, decision, structure, system, artifact, or alignment.
Framework: Scope → Ownership → Decision → Contribution → Evidence
Scope — how broad was the project?
Ownership — what was yours?
Decision — what decisions did you directly make or shape?
Contribution — what value was created?
Evidence — what proves it?
Ownership should be specific
“Responsible for design” is vague. Explain where responsibility began, where it ended, and who you collaborated with.
Decisions make seniority visible
Senior contribution is often visible less through task volume and more through judgment: what problem you prioritized, what option you rejected, and what trade-off you made.
Team outcome is not a personal claim
Keep the team result and your contribution visible together, but do not merge them.
Contribution is not always an artifact
Alignment, reducing ambiguity, resolving conflict, creating operating rhythm, or preventing a bad decision can all be meaningful contribution.
Applying this on Forwork
Each Project can include Scope, Ownership, Key Decisions, Contributions, and Evidence so both people and AI can distinguish participation from real value creation.
Conclusion
Do not stop at “I was X on this project.” Ask: What did I own? What did I decide? What value did I create? Where is the evidence?