Insights
Production scaled. Deciding did not.
A single shoot used to produce a handful of finished images. It now produces a master and twenty outputs: aspect ratios per channel, localized cuts, versions sized for placements that did not exist last year. Production scaled. The number of decisions a team can actually make did not, and the gap between the two is where the risk now sits.
Mathias Buschor
Co-Founder at moodcase
•
2
min read

Variants are parallel forms of one master, all current at once: a ratio per channel, a localized cut, a size for a new placement. Versions are sequential, and one of them is current. A library built five years ago assumed a finished image was a thing you kept. Today it is a source. Nothing broke, so the shift goes unnoticed, and what changed is the ratio between what gets made and what gets looked at.
Variants are parallel, and all of them are current
Channels multiplied, localization became an image job, and the tools that produce variants removed production as the constraint. A campaign of six images now means six images and ninety derivatives, each legitimate and each correct. Handling built around files assumes versions, where only one is current.
A decision does not scale the way output does
Approval covers what a person looked at. When ninety derivatives come from six approved masters, the approval covers the masters. Generating more answers a question nobody was stuck on: the bottleneck was knowing whether the fifteenth crop should exist, and whether anyone looked at it before it ran. Usually that is fine. Then a face is cut at the edge of a square, or a rights window covered the master and not the placement.
The failure is that nothing recorded a decision, and absence of a decision looks identical to a decision that went unrecorded. Generation and judgment scale differently. What handling can do is keep the decision attached to the thing it was about, so the boundary between what was decided and what was derived stays visible.

What moodcase does with this
moodcase Visual Asset Management does not generate derivatives. It keeps the decision with the asset. Workflow Statuses record each asset's state on the asset, and Activity & Audit Logs record who changed it. A derivative brought into the library carries its own status, and one still at No Status says plainly that nobody has moved it. Collections hold a master and its channel cuts side by side without copying a file.
Where this fits
The moment is a question about last quarter: how many of the things that went out were looked at first. In moodcase each one in the library carries its status, so the decided and the merely produced can be told apart.
Visual assets need more than a folder. See how moodcase handles the full workflow.
Try all features for 7 days. No credit card required.
Delivery
Approval
Marketing Teams
Brands
RELATED


