How to Check Who Actually Did the Work
How to separate the overall project result from the contributor’s actual role and scope.
In a portfolio, ask not only who made the work, but what they owned and how far their responsibility went.
A project may include planners, designers, developers, photographers, and external partners. A company name or a polished image does not explain the individual role.
Separate the result from the responsibility
Write down the overall project result and the part the person directly handled. A full website may represent only a specific screen or system owned by that person.
Five useful checks
Who defined the problem?
Which decisions did the person own?
What deliverables did they produce directly?
How did their work connect to other contributors?
What role could they take on in a similar project?
Ask for one concrete example
Instead of relying on “I did everything,” ask about one difficult decision, one changed condition, one delivered file, and how completion was checked.
A partial role is not a weakness
Accurately describing a limited role makes collaboration easier to predict. The useful distinction is between the overall result and the work actually owned.
Conclusion
A portfolio starts a conversation; it does not settle every question. Separating the result, role, collaboration, and likely future scope leads to a clearer assessment.
Related updates
A Portfolio That Fits Without Looking Flashy
How to find portfolio work that fits your problem and conditions, even when it is not the most eye-catching.
Read moreBlogHow to Read a Portfolio for Practical Fit
A practical way to compare portfolios by problem, constraints, audience, and operating conditions rather than appearance.
Read moreBlogWhy a Portfolio Should Show the Process
The process explains the decisions behind a result and makes future collaboration easier to assess.
Read more