Visual inspection and improvement workflow

Assuming your human has asked you to visually inspect and/or improve the look/graphics/visuals of something, you should follow a process similar to the following.

1. Consider all the ways in which this thing can be seen by users. Examples:

   • Website / web application: different resolutions, viewport sizes, or zoom levels, or shown on various pages with different backgrounds
   • Game asset: it could be in different poses or at different angles, in different states, shown on different screens, or used by other characters/creatures
   • Text: it may be shown in different layouts or wrapped in different ways

2. Take screenshots of the thing in as many ways as you think end users may see it. Take multiple screenshots. Do not use a contact sheet or grid. You can see things better in close-ups than in grids of multiple items. Try to take the screenshots close-up and focused on the thing you're trying to improve.

3. Look at all the screenshots you have captured of the thing in question. Carefully consider what looks good and what looks bad. Be very critical, but also take into account any specific styling or general requests from your human if they have provided any.

4. Make improvements to the thing. When you think you're done visually improving it, you need to make sure, so go back to step 2 (retake all the screenshots of the improved version of the thing) and then iterate.

5. Stop improving it only when you can no longer see any visual problems in the thing you've been asked to improve. If this takes many iterations, that's fine. It's better to take longer and produce a visually great result for your human than to be quick and provide something ugly.