Step 2. Resource Audits

Resource Audits are a more focused assessment which involves an in depth analysis of the current state of your business.

The goal is to identify the who, where, what and how within your company; who are your main stakeholders, where are all of your assets and metadata stored, what kind of assets and metadata do you have / produce and how are you ideating, creating, curating, analysing and archiving assets, and utilising metadata.

Resources includes every valuable entity your company utilises; People, Information, Systems and Processes.

To construct and deliver a successful strategy you must understand what you have and how all of the pieces fit together. With the information gathered it is much easier to transform the way you handle content and the way your business operates.

A crucial part of resource audits is identifying stakeholders within different business units who will help guide, manage and deliver on the strategy both before and after software implementation.

Stakeholders are likely to have very different roles, skill sets and use the DAM for different purposes.

The five pillars of the asset lifecycle aims to align stakeholder roles, focusing in on how they interact with assets in a broad sense rather than looking at specifics…

  • IDEATE
    Capturing the expression of an idea
  • CREATE
    Taking that idea and turning it into a tangible asset

  • CURATE
    Sharing that tangible asset with a wider audience

  • ANALYSE
    Gaining insight from that audience on your asset

  • ARCHIVE
    Preserving that asset safely and securely

Stakeholders may fulfill one of these roles or all five.

The importance of the five pillars is recognising that all Creators are likely to have shared needs and requirements, as will Ideators, Curators and so on.

It also places the asset at the core of DAM strategy, something that every successful content-driven company must do.

Stakeholders are both the backbone of DAM from an organisational standpoint, but also play a key role in directing requirements gathering and achieving user buy-in.

Engaging with stakeholders early on ensures that decisions made further along are backed by the people using the DAM system.

STEP 2
Step 1
Step 3