Choose the turning points

Select moments when the project changed direction, a constraint was resolved or an alternative was rejected. The purpose is to expose your reasoning, not document every meeting. Pair each process image with a sentence explaining what changed and why. A reader should be able to follow the progression without understanding your internal software or terminology. Avoid including rough work merely because it makes the presentation look more substantial.

Separate exploration from delivery

Mark sketches, prototypes and final outputs clearly. Otherwise a prospect may assume an early concept was delivered to a client. Keep confidential comments and internal annotations out of public screenshots. If you use recreated diagrams, label them as explanatory reconstructions. End with the final decision so the process supports a conclusion. A long trail of alternatives without a resolution can make a competent project appear unfinished.

Imagine this

Hypothetical example

A hypothetical product designer shows an early navigation sketch, a revised prototype and the final approved structure. Three captions explain the decision at each stage. The portfolio excludes fifteen nearly identical screens because they add volume without clarifying the reasoning.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.