The idea
Evaluating the work itself and understanding its consequences provide different information. Learning requires enough visibility into downstream use, difficulties, and outcomes to investigate how the contribution mattered.
Situation
You can assess the technical quality of your work but cannot tell whether it helped, or what you should improve.
Useful when
Reviewing applied researchMentoring someone through a projectEvaluating a technical investmentUnderstanding why a feature did not helpPlanning feedback after a launch
Watch for
Outcomes alone do not establish the quality of a decision or an individual's contribution. Other people, external conditions, chance, and delayed effects can influence what happens.
Where this came from
Research, Product work, Startups, Mentoring
Example
A well-built feature sees little use. Before judging the work, investigate whether people could find it, whether it addressed their need, and whether something made it difficult to use.