Short answer
A DAM selection team works best with five role seats: the CMO, the brand manager, the IT architect, the DAM manager, and procurement and legal. Each seat owns a different risk, from five-year cost to metadata quality. DAMSelection rule of thumb: five to seven people cover all five seats in organisations with more than 20 DAM users, with one named decision owner.
Why DAM selection roles matter
DAM selection roles matter because each seat on the team catches a failure the other seats miss. A CMO sees cost and adoption risk. An IT architect sees API limits and hosting gaps. A DAM manager sees a metadata model that will break search within a year.
Selections that skip a seat pay for it after signature. DAMSelection assessment: two gaps cause the most rework, a missing DAM manager during demos and procurement joining only at contract stage.
The DAMSelection order of work applies to the team as well: data, then process, then people, then tooling. The role guides follow that order and sit within the wider DAM fit framework. The DAM manager designs the metadata model first, the brand manager and CMO define the processes, and IT and procurement test the tooling and terms.
The five roles and what each owns
The five DAM selection roles split ownership along the twelve DAMSelection scoring criteria, so every criterion has one accountable seat.
| Role | Owns in the selection | Scoring criteria led | Role guide |
|---|---|---|---|
| CMO and marketing leadership | Business case, adoption risk, five-year cost | Administration and total cost profile | CMO guide |
| Brand manager | Brand portal, guideline control, regional consistency | Brand portal and sharing; rights and licence management | Brand manager guide |
| IT and enterprise architect | Integration architecture, security, API limits, hosting | API and extensibility; security, hosting and compliance; PIM integration depth | IT architect guide |
| DAM manager and librarian | Metadata schema, taxonomy, migration, daily administration | Metadata and taxonomy flexibility; search and AI discovery; asset ingestion | DAM manager guide |
| Procurement and legal | Pricing archetype, renewal terms, exit, data protection | Commercial and contract terms across all criteria | Procurement guide |
The remaining criteria, workflow and approvals, distribution and CDN, and creative tool integration, sit with whichever seat runs those processes today. Creative operations often joins the brand manager for creative tool integration.
How the roles split the seven checkpoints
Each of the seven Selection Route checkpoints has one lead role and one or two supporting roles.
| Checkpoint | Lead role | Supporting roles |
|---|---|---|
| 1 Map | DAM manager | Brand manager, IT architect |
| 2 Define | DAM manager | Brand manager, IT architect |
| 3 Justify | CMO | Procurement and legal |
| 4 Shortlist | IT architect | Procurement and legal, CMO |
| 5 Test | DAM manager | All five roles attend their scenarios |
| 6 Score | CMO as decision owner | All five roles score their criteria |
| 7 Sign | Procurement and legal | CMO, IT architect |
DAMSelection rule of thumb: plan two to four hours per week per team member during the test and score checkpoints. The lead role of each checkpoint carries more than that during its own checkpoint.
How to staff the roles in a smaller team
A smaller DAM selection team combines seats while keeping each risk owned by a named person.
- Under 20 DAM users: one marketing lead holds the CMO and brand manager seats, one operator holds the DAM manager seat, and an external IT contact reviews security.
- 20 to 300 users: staff all five seats, with procurement and legal often shared as one person.
- Hundreds of users across regions: add a regional brand representative and the PIM or product content owner as a sixth seat.
The PIM owner joins whenever product images and documents flow to commerce channels. DAMSelection assessment: DAM and PIM form one product content supply chain, so the PIM owner reviews the shared data model before Checkpoint 4.
Decision rights for the selection team
Decision rights for a DAM selection fit on one page: who decides, who scores and who advises. Agree them before the first demo.
- Name one decision owner, usually the CMO or a marketing operations director.
- Assign each scoring criterion to one role from the table in this guide.
- Record which roles hold a veto, typically IT on security and procurement on contract terms.
- Publish the scoring weights before demos start.
- Store the charter with the selection team guide outputs and the stakeholder map.
After signature, the same roles carry into the implementation RACI. The DAM manager becomes the daily owner, and the CMO keeps the business case.
All guides in this pillar
- DAM selection for cmo and marketing leadership
- DAM selection for brand manager
- DAM selection for it and enterprise architect
- DAM selection for dam manager and librarian
- DAM selection for procurement and legal
Frequently asked
Who should lead a DAM selection?
The CMO or a marketing operations director usually leads a DAM selection as decision owner, because marketing carries the budget and the adoption risk. The DAM manager leads the day-to-day work in Checkpoints 1, 2 and 5. A single named decision owner keeps scoring disputes short.
How many people should be on a DAM selection team?
A DAM selection team of five to seven people covers all five role seats in most mid-market and enterprise organisations, a DAMSelection rule of thumb. Teams with fewer than five tend to miss a seat. Teams with more than seven slow scoring, so extra stakeholders join demos without scoring rights.
Does IT need to be involved in a DAM selection?
IT needs a seat in every DAM selection, including SaaS purchases. The IT architect checks single sign-on, hosting regions, API limits and integration depth with the PIM and CMS. Without that seat, security reviews start late and can delay signature by weeks.
When should procurement join a DAM selection?
Procurement and legal should join a DAM selection at Checkpoint 3: Justify, when the team models five-year cost by pricing archetype. Early involvement lets procurement shape the commercial questions in the RFP and start the security review in parallel with demos.
What does each role score in a DAM demo?
Each role scores the scenarios and criteria it owns in a DAM demo. The DAM manager scores metadata and search, the brand manager scores portal and sharing, IT scores APIs and security, and the CMO scores adoption. The [Demo Script Generator](/dam/tools/demo-script-generator/) assigns scenarios to scorers.