Asset management when shared drives stop working
Every growing agency reaches the point where the shared drive becomes a liability rather than a tool. The patterns that work past that point are not what most studios expect.
A senior designer at a Calgary agency spends two hours looking for the brand assets for a client they have worked with for four years. The files exist. They are on a shared drive. They are in three different folders, all named “Brand,” none of which are inside the client’s project room. By the time the designer finds the right version of the wordmark, the project manager has rebuilt half of it from a PDF screenshot. This is not an isolated event. It is the predictable consequence of an asset library that grew by accretion and never had a system imposed on it.
The shared-drive era of agency work has an upper limit. We see it at fifteen to thirty staff, depending on how many concurrent projects the studio runs. Below that scale, everyone roughly knows where everything is. Above it, institutional memory fragments. The asset that lives in the head of the senior designer who left last spring is no longer findable. The cost of that fragmentation is real, and it grows quietly until somebody runs a stopwatch on a search.
What a structured asset library actually is
An asset library is not the storage itself. It is the layer of structure on top of the storage that decides what goes where, what is shared, and what gets archived. The same NAS that is unusable today can become productive next month if the structure on top of it changes.
Three things make a library work:
Folder hierarchy with intent. A clear separation between client work, internal templates, brand assets per client, and archived projects. The hierarchy should be discoverable in under three clicks for any active asset.
Naming conventions. Every file follows a predictable pattern. Client code, project code, version, status. A senior designer should be able to look at a filename and know what it is without opening it.
Retention policy. A defined point at which active project material moves to archive. Without this, the library bloats indefinitely and the search slows year over year.
Accretion-Based Storage
The pattern most agencies start with:
- One shared drive grew over the years without a structural pass
- Naming conventions vary by designer
- No retention policy, so completed projects sit alongside active ones
- Brand assets live in three different places
Result: search becomes the bottleneck, and the cost compounds as the team grows.
Structured Asset Library
The pattern that actually scales:
- Top-level hierarchy: clients, projects, brand, templates, archive
- One naming convention everyone follows
- Quarterly archive pass moves completed projects out of the active tier
- Brand assets per client in a known canonical location
Result: any team member can find any asset in under a minute, and the library scales as headcount grows.
When digital asset management tools earn their cost
A folder hierarchy with conventions takes a studio surprisingly far. Most agencies under thirty staff and under five thousand active files do not need a dedicated digital asset management (DAM) tool. They need a structural pass on what they already have.
The breakpoint for DAM tooling shows up at one of three thresholds. The library crosses ten thousand active files. More than three project rooms are simultaneously active across the agency. Brand assets get reused for more than one client in a way that needs version tracking the file system cannot provide.
When those thresholds are crossed, options like Air, Brandfolder, or Frontify provide tagged search, usage tracking, and brand-asset distribution that folder hierarchies cannot match. The cost is justified by what is recovered in search time and version errors. Below those thresholds, the tooling solves a problem the agency does not actually have, and the team is unlikely to adopt it consistently.
The hardest part is the transition
The technical work in moving an agency from accretion to structure is straightforward. The operational work is not. Every designer on the team has a mental map of the old library, and most have personal habits the new structure breaks.
The transition that works has three parts: a frozen old library that is read-only after a cutover date, a structured new library that becomes the only place new work goes, and a person inside the agency who owns the convention. Without ownership, the conventions drift back to the old patterns within a quarter.
We have seen agencies attempt this transition without the ownership piece. The new structure stays clean for three weeks. By month two, designers have started reverting to old habits. By month six, the new library looks like the old one, and the exercise has to be repeated.
When to think about this
The right time to think about asset management is before the next search across the library takes longer than the work itself, before a junior hire reaches the second week without knowing where anything lives, or before a senior designer leaves and their mental map walks out the door with them.
An asset library is operational infrastructure. The studios that treat it that way move faster than the studios that do not.
Thinking through this for your business?
RIPEDA helps Apple-first organizations make these decisions every day.
Get in touch
