Task ≠ Contribution ≠ Impact
How to separate task, contribution, and impact so your work is presented at the right level and with the right attribution.
Why these three are often confused
Profiles often list “user research,” “designed a flow,” or “managed a campaign” as if those activities were impact.
They are activities, not yet value.
Task: what was assigned or performed
Task answers: What did you do?
Examples include interviewing users, designing checkout, writing a proposal, or coordinating a sprint.
Contribution: the value you directly created
Contribution answers: What value did you personally create inside that work?
It may be an insight, decision, structure, resolved conflict, or new clarity.
Impact: what changed afterward
Impact answers: What changed because that contribution existed?
It may be higher conversion, lower cycle time, better decisions, fewer errors, or improved customer experience.
Framework: Task → Contribution → Impact
Task — activity.
Contribution — value creation.
Impact — consequence.
Example: Product Designer
Task: redesigned onboarding.
Contribution: identified three friction points and restructured the sequence to reduce cognitive load.
Impact: activation increased 14% over six weeks.
Contribution matters especially in teamwork
Team outcomes are usually collective.
Do not claim the whole impact as yours, but do not hide behind a task list either. Separate team outcome from your contribution .
Impact is not always a metric
Impact may be reduced ambiguity, stronger trust, alignment, avoiding a bad decision, or creating a reusable system.
Applying this on Forwork
Each Project can make the logic explicit: What I did, What I contributed, What changed.
Profile can surface contribution; Proposal can reuse impact as credibility.
Conclusion
Do not let a task list replace the story of value.
Ask: What did I do? What value did I create? What changed because of it?
Task → Contribution → Impact.