What a smart DAM means for marketing teams
Find existing assets from an image description or the work you are making, and inspect brand-aware reasons where recommendations provide them.
Updated 23 October 2026: Clarified the current Library search and separate social Post Intelligence workflows. Original publication date retained.
You remember the image, but not its filename. You try another folder, change the search terms, and open several plausible files. Sometimes the next step is asking the colleague who knows the library. A smart DAM should help you find the existing asset and understand its relevance to the work.
Begin with an image or the work
An image description is a legitimate starting point: an olive jacket beside a river, with no visible logo. So is a social post idea that needs an outdoor image with a quiet, practical feel. Neither requires a formal brief.
Brand context adds information about the audience, positioning and visual cues. It helps explain why an asset may fit the work. It must not erase literal requirements: product, color, version, format and exclusions still matter.
Finding and understandable relevance belong together
Natural-language search, contextual search, automated tagging and useful metadata can all help people explore a library. Competitors offer overlapping capabilities; contextual discovery is not unique to Daryl. Adobe’s asset discovery documentation, for example, describes conversational and contextual search.
Finding plausible files is useful. Reasons can help someone inspect those files more closely: what the image shows, which brand cues it reflects, and where it may conflict with the request. A recommendation should make disagreement possible, without pretending creative judgment is certain.
The same image can suit one piece of work and be wrong for another. A group photograph might support a community story while distracting from an announcement that needs a clear product view.
How this works in Daryl today
Daryl has separate workflows:
- Library search: describe an image to search the existing library.
- Post Intelligence: supply a social post or post idea. It uses that direction and supplied Brand Context to recommend assets with reasons you can inspect.
Do not assume one entry point automatically routes every request, saves it as Work or transfers an asset and reasoning into Compose. Check the supported next actions in the route you use.
Reasons support review. They do not establish usage rights, approval status, the current product version or campaign performance. Check those requirements against the actual file and your records before using it.
Keep the library and source visible
A useful asset experience keeps candidate files visible, with source information and available metadata. Teams can use Daryl’s native library or review supported connections. Import, sync, access and follow-up actions depend on the source and workflow; they are not identical across every connection.
Documents such as PDFs, decks, text and legal files are not imported or analyzed by Daryl’s current media workflows. Keep those in your document system.
Questions to ask in a demo
- Can I find a supported asset from my own library using an image description, without knowing its filename?
- Can I include precise product, color, version and exclusion requirements, and inspect whether a result actually meets them?
- Where is brand context used, and what evidence supports each recommendation?
- Which file types, sources and next actions are supported today?
- How do I check rights, approval and current-version status separately from creative fit?
Test the same real requests in each candidate and in the tools you already use. Record gaps as well as useful results. Do not substitute an unexplained score or a vendor’s promise for inspecting the assets.
The standard is understandable relevance
Find the assets you know you have. And the ones you forgot. Then inspect why they may fit your brand and the job at hand.
Describe an image or tell Daryl what you’re making.