Six standing beats cover the subject area. Bylines here are not invented per article: each author writes inside a stated area, and where a piece crosses two, it goes to whoever owns the load-bearing part of the argument.
Adaora Nwachukwu
Beat: DAM strategy, operating models, maturity and adoption.
Adaora works on the part of digital asset management that no budget line covers: who owns the library, what contribution actually costs the people doing it, and why a technically successful rollout can still be dead within a year. She is unsentimental about the fact that a DAM is a cost to contributors and a benefit to consumers, and that programmes which do not fund the first side do not survive.
Writes: what enterprise DAM actually is, DAM, PIM, CMS and MDM, why DAM rollouts fail, the requirements checklist.
Henrik Ostberg
Beat: Enterprise architecture, integration, system boundaries.
Henrik has spent a decade drawing lines between systems that all believe they own the same record. His recurring theme is that “single source of truth” is an architectural property you either have or do not, and that most estates promising it are running replication with a favourite. He is also the person most likely to tell you that you do not need a DAM.
Writes: why the shared drive stops working, integration patterns, single source of truth is an architecture, alternatives to a traditional enterprise DAM.
Claudia Feng
Beat: Metadata standards, taxonomy, cataloguing, lifecycle.
Claudia came to this from library and information science, which shows in her insistence that vocabularies need owners and that deprecation is a state rather than a delete. She argues, with data, that a twelve-field schema at ninety-five percent completeness beats a forty-field schema at twenty, and that most taxonomy workshops produce structures only their authors can navigate.
Writes: the metadata schema an enterprise actually needs, designing a taxonomy people actually use, the asset lifecycle.
Marcus Delacroix
Beat: Information security, rights, compliance, audit.
Marcus is interested in the gap between a control that is documented and a control that operates. His test for any governance framework is whether the evidence is a by-product of normal work or something four people assemble under deadline, and his test for any access model is what happens when somebody leaves, which is the control nobody exercises until it fails.
Writes: a governance framework that survives an audit, rights and expiry as first-class asset data, access control, SSO and audit trails.
Yusuf Rahimi
Beat: Platform engineering, APIs, automation, migration.
Yusuf builds and moves media infrastructure. He has migrated enough libraries to be firm about two things: the file copy is the easy part, and most of what makes an asset useful lives in folder paths, filenames and spreadsheets rather than in the file. He is the one who checks whether a vendor’s interface is built on their own public API.
Writes: headless DAM, migrating a million assets, delivery is part of your DAM.
Elena Kowalczyk
Beat: Procurement, TCO, vendor evaluation, change management.
Elena works on the cost lines that never appear on a quote. She builds business cases that survive a finance review, which means treating productivity claims with the scepticism a CFO will apply to them anyway, and comparison frameworks that separate platforms rather than scoring five vendors at ninety-four percent.
Writes: what enterprise DAM costs, the DAM business case your CFO will sign, platforms compared by who they are for.
Questions and corrections go to editors@enterprisedigitalassetmanagement.com, as set out on the contact page.