Digital Asset Manager: Role, Skills and Pay

Maintains the vocabulary and the schema, reviews what is entering the library and how it is described, handles permissions and rights questions, and supports the teams using the system. In organisations without a dedicated role, the work does not disappear — it is distributed and usually done inconsistently.

Commonly from library and information science, archives, or marketing and creative operations. The information professions bring cataloguing and vocabulary control; the operations route brings knowledge of how the assets are actually used. Both routes need the other half learned on the job.

The disciplines overlap substantially and the objectives differ. An archivist optimises for long-term preservation and provenance; a digital asset manager optimises for reuse under current rights. Both care about description, but retention and access decisions follow different logic.

Metadata and vocabulary design, an understanding of usage rights, and the ability to negotiate conventions with teams who did not ask for them. Technical administration of the platform matters, and is the part most easily learned or delegated.

Not necessarily a full-time one, but it does need a named owner. Libraries deteriorate when responsibility for the vocabulary is shared by everyone, because near-duplicate terms accumulate faster than anybody notices. A part-time owner with authority beats a committee.

It is often adjacent and sometimes the same person. Marketing operations owns the campaign workflow; asset management owns the library it draws from. Where they are separate, the boundary usually falls at the point an asset is approved for reuse.

Enough to design a schema and to predict what survives an export: which fields exist in IPTC and XMP, how they map to the platform's own fields, and where a workflow silently drops them. Deep tooling knowledge can be delegated; the schema decisions cannot.

By reuse and by retrieval, not by volume ingested. Assets found without asking a colleague, licences that never lapse unnoticed, and work not recreated because the original was locatable are the outcomes worth counting, and all of them require a baseline taken before the system arrives.

Frequently not, and it almost always requires influencing them. The authority is over the schema and the rules rather than over headcount, which makes stakeholder work the larger part of the job in most organisations.

Towards content or information operations, or deeper into governance and compliance where rights management dominates. Both directions build on the same core: knowing how an organisation describes what it owns, and what it is permitted to do with it.