CREATIVE WORKSHOP / CRAFT
Keep versions.
Keep learning.
Saving a draft is not indecision. It lets you compare what changed with what actually improved.
THE MAIN IDEA
Make revisions testable rather than circular.
A version is a checkpoint in the development of an idea. Saving one before a substantial revision makes it possible to compare choices, restore material you later miss, and discuss changes concretely. Use names that describe what changed rather than labels that imply a draft is worthless: “navigation-test-02” tells you more than “final-FINAL-new.” A written note can explain the decision: larger headline for mobile clarity, shorter introduction to get readers to the map, or less saturation to improve text contrast. One meaningful change per version makes cause and effect easier to notice. In a digital project, version-control software can show text and code differences; a duplicate file or a photographed sketch may be enough for a paper project. Protect private client or personal information when backups are created, shared, or stored in a cloud service. Some revisions are experiments that will be rejected, and that is still learning if you record the result. A side-by-side comparison can expose trade-offs that memory smooths over. One version may read faster while another feels more distinctive; the brief and audience determine which trade-off is acceptable. Establish a finish line so the process does not become an endless attempt to remove every trace of uncertainty. A workable test might be that a reader can locate a contact link, that the printed fold is correct, or that a recording is understandable at a reasonable level. Ask for feedback on the specific change and compare observations from appropriate participants. Do not treat a vote as an objective measure of quality if the people giving feedback do not match the project's audience. Review variations at the actual output size and on the devices or materials that matter. A tiny-screen design may look different when enlarged, and a color that is vivid on one monitor may print muddy. Keep original assets and licenses alongside versions so provenance is not lost when layers are flattened. Revision also has an emotional dimension: deleting a draft can feel like losing effort, even when you have learned from it. A saved copy allows you to move forward without pretending previous work never mattered. Maintaining iterations is a craft habit, not a demand for industrial process. Small checkpoints are enough to protect experimentation and make it easier to commit to a clear final choice. Finish the project, retain the source files appropriately, and make the next project easier because you now know why certain decisions worked.
TRY THIS
Save an A/B pair before editing.
Duplicate a small project and change exactly one decision in the copy. Name each version for the change, compare them side by side at real output size, and ask a reader one specific question. Record why you choose one or keep both for different uses.