Ask a creative team what goes wrong and they will tell you things get lost. Push on it and the picture changes: the messages are all there, searchable, in the thread where they were written. What is gone is everything around them.
A note without its subject is noise
“Can we warm this up a bit?” is a perfectly clear instruction attached to an image and a version. Detached from both, it is a riddle. Three weeks later nobody can say which frame it referred to, whether it was applied, or whether the warmth someone added later was this note or a different one.
This is why chat feels productive and reviews feel slow. Chat is excellent at moving sentences between people and structurally incapable of remembering what they were about.
The cost shows up as re-litigation
You can measure lost context by how often a settled decision comes back.
A team that loses context does not notice it as loss. They notice it as meetings. The same discussion returns because nobody can produce the reasoning that closed it last time, and re-deciding is easier than reconstructing.
Anchoring beats archiving
The instinct is to archive harder — better folders, longer documents, a wiki nobody reads. That treats the symptom. The fix is to anchor: every note lands on the version it is about, and travels with it.
Once feedback is anchored, the archive mostly writes itself. The history of a shot is the history of its notes, in order, against the versions they changed.
