System strategy · Field guide 04
Shared drive or digital asset management?
Folders are durable, understandable and often entirely adequate. The decision changes when the organization needs richer discovery, controlled reuse and traceable context across teams.
What folders do well
A well-managed shared drive is transparent. Staff understand paths, operating systems support it and files can be backed up without a specialized platform. Small teams with consistent naming, stable responsibilities and modest reuse needs may not benefit from another application.
The weakness is that a file usually has one visible place. A photograph can depict a species, belong to a restoration project, come from a specific photographer and be approved for a particular use. Folders force one hierarchy; metadata can express all of those relationships.
Five signs the archive has outgrown paths
- Retrieval depends on one person. Other staff cannot find known assets without asking.
- Copies multiply for every use. Teams create email, web, print and presentation folders with no clear master.
- Rights decisions are invisible. Staff cannot tell whether an image is cleared, credited or restricted.
- Descriptions live outside the files. The folder tree carries context that disappears when items move.
- Several programs need the same collection. Path-based ownership prevents shared discovery or creates uncontrolled access.
| Need | Disciplined shared drive | DAM |
|---|---|---|
| Known-item retrieval | Strong when path and name are known | Strong with identifier or metadata |
| Exploratory search | Limited to names and operating-system indexes | Multi-field, filtered and collection-based |
| Multiple contexts | Often requires copies or shortcuts | One asset can appear in many collections |
| Rights and restrictions | Possible through conventions and permissions | Can connect record-level terms to workflows |
| Portability | Files are directly visible | Depends on export quality and standards support |
| Administration | Low platform overhead; high discipline required | Higher platform overhead; structured governance required |
Use a retrieval benchmark
Before purchasing anything, run the same ten requests against the current environment and a representative system demonstration. Include known-item lookup, broad subject search, rights verification, original retrieval, collection assembly and metadata export. Measure completion time, error rate and questions asked.
A polished demo can look faster because its sample data is clean. Require the vendor to use a copy of your difficult test set, including missing files, inconsistent terms and sensitive records.
Calculate the cost of the current state
Estimate staff hours spent searching, recreating lost context, requesting files from other teams, verifying credits and rebuilding collections. Add the risk of publishing an image without known rights or revealing a restricted location. Compare that with implementation, migration, licensing, storage, training and ongoing administration.
A DAM earns its place when the value of shared context, controlled reuse and dependable retrieval exceeds the cost of another system to govern.
Fix governance first
A DAM will not decide which date is authoritative, who may approve a photograph or how project names should be controlled. Assign collection owners, define minimum metadata, establish rights roles and document export requirements before procurement. Those decisions improve a shared drive today and make any future migration more successful.