Give the work a little distance
Once an illustration is delivered or set aside, the urge to judge it can be strong. Small imperfections may be especially visible after hours of looking at the same image. A post-project review works better when it is treated as a record of decisions, not a final verdict on whether the work is good. Its purpose is to make the next project a little easier to plan.
If possible, wait until the immediate rush of finishing has passed. Then set aside ten or fifteen minutes and open the final image alongside any brief, sketches, or notes you kept. You do not need a polished journal entry. A few honest sentences are more useful than a long review you will never want to repeat. Keep the scope to this project rather than trying to assess your entire development as an illustrator.
Start with the job the image needed to do
Before listing strengths and weaknesses, write down the illustration’s purpose. Was it meant to explain an idea, establish a mood, introduce a character, or guide a reader through a sequence? Note the intended audience and any constraints that shaped the work, such as format, limited colors, or a short turnaround. An image can succeed at its task without containing your most ambitious drawing, and an attractive detail can be less important than a clear focal point.
Now look at the finished piece at the size and in the setting where it is likely to be seen. Ask what a viewer notices first and whether that supports the purpose you recorded. If there was feedback, separate it from your own observations: write what someone actually said rather than guessing what they thought. When there is no feedback, describe what you can see instead of inventing a viewer’s response.
Trace the process, not just the result
The final image cannot show every decision that made it possible. Look back through your roughs or layers and identify one choice that helped: perhaps a quick value study clarified the composition, or a reference sheet kept a character consistent. Then identify one point where progress slowed. Was the problem unclear direction, an unfamiliar tool, too many competing ideas, or too little time reserved for revisions?
Be specific enough that the observation could change a future workflow. “I am bad at backgrounds” offers little guidance; “I began the background after the character was fully rendered, so I had limited room to adjust the lighting” names a sequence you can test next time. It is also worth recording what did not need improvement. If a simple thumbnail settled the composition quickly, you may not need to add more planning steps.
Choose one experiment for the next piece
A review becomes useful when it leads to a manageable action. Choose one change that fits a likely future project: make three small composition options before refining, check the image in grayscale halfway through, or schedule a pause before the final pass. Frame it as an experiment rather than a permanent rule. Different briefs call for different methods, and a technique that helps one illustration may be unnecessary for another.
Keep the experiment narrow enough to notice its effect. Trying to change your sketching method, color palette, file organization, and working hours at once makes it difficult to tell what helped. You can keep a separate list of ideas to revisit later. For now, record the next action in a sentence that begins, “On a similar project, I will…”
Keep a short record you can actually reuse
A repeatable review can fit in a single note with four prompts: What was the image meant to do? What worked? Where did the process become difficult? What will I test next time? Add a small copy of the final image or a file name so the notes remain connected to the work. If you used references or received a brief, keep those materials organized according to any sharing or storage limits that apply to the project.
Over time, look for recurring patterns rather than judging individual pieces in isolation. You may find that rough layouts reliably help, or that revisions become harder when you skip an early clarity check. Some projects will offer little to learn beyond the fact that a method worked well enough. That is still worth recording. The goal is not to make every illustration a lesson in failure; it is to build a practical memory of how you work.
