Decide what the unfinished work needs to prove
A portfolio does not have to be a museum of completed assignments. A strong unfinished project might show a skill that your finished work does not yet represent, such as early concept development or visual exploration. But visitors should not have to guess why it is there. Before adding a work-in-progress piece, finish this sentence: “This project helps someone see that I can…” If the answer is vague, the piece may be better kept in a private archive for now.
Consider the kind of opportunity you want. Someone looking for a collaborator in an early exploratory phase may value a well-explained concept. Someone hiring you to deliver a finished product will also need evidence that you can bring work across the finish line. Unfinished projects can broaden the picture, but they should not crowd out examples of completed work.
Be precise about what is and is not finished
“Unfinished” can mean several things. A personal project may still be in development; a client project may have ended before launch; a concept may never have been intended for production. State which situation applies near the start of the project description. A simple label such as “self-initiated concept,” “prototype,” or “exploration in progress” gives visitors a more accurate frame than a polished image alone.
Explain the boundaries of your contribution as well. If you made interface screens but did not test or build them, say so. If a campaign proposal was not selected, present it as a proposal rather than as published work. These distinctions do not diminish your skills. They help a reader assess the work fairly and make the claims you do make more credible.
Check whether you have permission to show the material, particularly if another person or organization contributed to it. When permission or ownership is unclear, choose a different example or ask before publishing. Cropping a screenshot or removing a name does not necessarily make private material appropriate to share.
Show a useful slice, not an open-ended process
An unfinished project is easier to evaluate when you present a coherent stage of work. Choose a small set of artifacts that belong together: for example, a brief, two promising directions, and the reasoning behind the direction you would develop next. Avoid posting every sketch simply to demonstrate effort. Selection is part of the story.
Give visitors enough context to understand the problem, your constraints, and the decisions visible in the work. You can describe what you intended to explore without claiming that the idea succeeded. For instance, explain why you changed a layout after reviewing its readability, then identify what you would check next. Keep the distinction between a decision you made and an outcome you have not measured.
The presentation itself should feel deliberate even if the project is incomplete. Use legible images, consistent labels, and a clear stopping point. If the final artifact is missing, do not end with a promise that updates are coming. End with what the work currently demonstrates and, if useful, the next question you would investigate.
Give unfinished pieces the right place in your portfolio
Placement sets expectations. If most of your portfolio shows completed work, an unfinished piece can sit in a clearly named “Explorations” or “In progress” group. If it appears among your main projects, make its status apparent before a visitor opens the full page. You do not need a separate section for a single concept, but you do need a label that travels with it wherever it appears.
Review the balance of the portfolio as a whole. Ask whether a visitor could quickly find examples of finished work, understand what you personally did, and tell which pieces are speculative. If the unfinished work raises more questions than it answers, narrow the presentation or move it off the public site. A private version can still be useful when a conversation calls for that particular skill.
Finally, set a point at which you will reassess the piece. You might replace it when a stronger finished example becomes available, update it after another development stage, or remove it if it no longer reflects the work you want to do. The goal is not to apologize for unfinished work. It is to show it honestly and only when it helps someone understand your capabilities.
