An archive becomes useful to future work when it keeps the reason for a decision alongside the result. Add a short note to the final file: what prompted the work, which option was set aside and what would change if the project started again?
The note can be brief. Its value is helping someone understand the circumstances of a decision months later. Details without permission to share should remain in the internal record.
What belongs in a decision record?
I think of an archive in three layers: the published result, the reason for the decision and the learning that can be reused. A final asset rarely explains all three. Connect the original brief, accepted changes and review to the same project identity.
When a folder contains several versions, identify the approved file explicitly. Dates and version numbers help, but approval should not be inferred from a file name alone. Record who reviewed which version.
A simple project card
| Field | Information |
|---|---|
| Starting point | Need, audience and conditions |
| Decision | Chosen direction and reason |
| Change | Departure from the original scope |
| Result | Final asset and published location |
| Learning | What to preserve or change next time |
Build the card through brief notes at meaningful decisions rather than reconstructing everything from memory at the end. A retrospective story can accidentally make later knowledge appear as though it was available from the beginning.
Separate the internal archive from the public portfolio
Budgets, private discussions and personal contact information should not move automatically into a public case study. Review publication permissions separately. Possessing an image does not establish permission for every possible use.
In public writing I preserve the distinction between my role, contribution and available evidence. Without measurement, I do not invent an outcome. The archive should represent work accurately, not merely make every project sound successful.
Use the archive to compare conditions
When a new brief arrives, look for similar questions rather than copy an earlier design. Which conditions remain and which have changed? That comparison turns project memory into support for a new decision instead of an excuse to repeat an old one.