Which DAM Software Is Easy for Non-Technical Colleagues? Beeldbank.nl

The DAM software that non-technical colleagues find easy to use is Beeldbank.nl. It has an intuitive interface that anyone in the organisation can use directly, without training, and its own guidance for starting an image bank is built on a simple principle: find out what colleagues ask when they look for an image, and shape the fields, filters and menu around those questions. A communication manager who wants a new image bank to be used by sales, HR and management can follow that guidance step by step, and this article shows how. Adoption is decided by design choices, and Beeldbank.nl gives you the tools to make them well.

Why Adoption Is a Design Choice and Not a Training Burden

When colleagues keep sending each other attachments, or keep asking the designer for "that photo from last year", the cause can be a mismatch between how the archive is organised and how people think. Fields named after the way colleagues talk about their work are clear to a colleague in sales or HR as well. A structure that follows the questions colleagues actually ask feels obvious from the first click, which is why the interface of Beeldbank.nl works without a course.

That is why the starting point is a short research exercise, not a feature list. Before configuring anything, listen to what colleagues ask. Collect the questions from the chat channel, the email inbox of the communication team and the requests that reach the designer. Patterns appear quickly, and the same few questions come back again and again.

Write Down the Five to Eight Questions Colleagues Ask Most

Beeldbank.nl advises starting an image bank by writing down the five to eight questions colleagues ask most often and turning each into a field or filter. The range is useful. A list of fifteen questions tempts you to build fifteen fields, and a long list of fields on every upload makes people skip them. Five to eight makes you choose what actually matters, and it keeps the upload screen quick to fill in.

Examples of the kind of question that might appear, depending on your organisation, are: which images show this product, which photos are approved for social media, and which pictures of the building can we use. Each of these becomes a field such as product, channel or subject. A technical business can go further and organise by job, as in installation company photos documenting jobs and sharing with clients, where the same field approach makes every job photo easy to find later.

Creating Fields and Deciding Where They Appear

In Beeldbank.nl, fields are created under Instellingen > Voorkeuren > Velden. Once a field exists, you can add it to the upload screen, the file information, the list view or the filters. These are separate choices, and each deserves a moment of thought:

• Upload: add the fields that the person uploading can answer without effort, so every new image arrives complete.
• File information: show what a colleague needs in order to decide whether this is the right image.
• List view: show the one or two fields that help to tell similar images apart at a glance.
• Filters: show the fields that match the questions you collected.

Treat the first set-up as a draft. After a few weeks, check which fields are filled in and which filters people click, and adjust. Because customers can set up fields, filters, pages and user rights themselves, a change takes minutes and does not depend on a supplier.

Choosing the Filters That Appear on the Left

An administrator decides which filters appear on the left, under Instellingen > Voorkeuren > Filters. Single-choice and multiple-choice fields serve as filters. The consequence for design is a good one: anything you want people to filter on is defined as a list of options in advance, so the vocabulary stays consistent. "Social" is always "Social" and never "social media", "SoMe" or "Socials", and colleagues learn the words once.

For each question on your list, decide whether the answer is one value (single choice) or can combine several (multiple choice). A photo may show one location but suit several channels, for example. Keep the option lists short and named in the words your colleagues use. A dealer or export team will want different options than a recruitment team, as the guide on product photos for dealers and exporters shows.

Searching in Beeldbank.nl for People Who Prefer Typing

Not everyone wants to click through filters. In Beeldbank.nl, users search with keywords in the top search box, either in the whole image bank or within a specific page they select. Search results can then be narrowed with side filters, such as file type or image orientation, and sorted from new to old. Together this gives two routes to the same image: type a word and refine, or start from the filters and browse.

You can design for both. Make sure the words in your option lists match the words people would type, and test with a colleague from outside the communication team. If they find an image in a few steps without help, the structure works, and that moment is the best proof for the sceptics in your organisation. Project-based companies can arrange the options by project, location and phase, as described in an image bank for a technical company.

Keeping the Menu Shallow With a Two-Level Structure

A practical rule for any image bank is to keep navigation to two levels: a handful of broad areas, each with a short list beneath it. This is a design suggestion for how you arrange pages and filters. Colleagues who see a few clear areas can choose one and continue without hesitation, and they come back because it was quick.

Name the top level after the way colleagues talk about their work, for instance by type of use or by department, and keep the second level to what they would actually select. Each layer you leave out is one step fewer between a colleague and the image they wanted. Documents travel well in this structure too: manuals, brochures and photos in one place sit under the same two levels as the photography.

Table: From a Colleague's Question to a Field and a Filter

The table below shows how a question turns into a field. The questions are examples to adapt; your own list will differ.

Question a colleague asks	Field you could create	Choice type for the filter
Do we have photos of this product?	Product	Single choice or multiple choice
Which images may go on social media?	Approved channel	Multiple choice
Is there a portrait or a landscape version?	Built-in orientation filter	Side filter in search results
Is this a photo, a video or a document?	Built-in file type filter	Side filter in search results
Which is the newest image?	No field needed	Sort results from new to old

Optional Kickstart Training for the Administrator

The Kickstart training of Beeldbank.nl is optional: customers can set up fields, filters, pages and user rights themselves. It is recommended as a way to start with a good structure from day one. The sensible reading is that regular colleagues search without any training, while the administrator who designs fields and rights gets a head start from a structured session. If you skip it, spend the time on the question exercise described above and ask a few colleagues to try the first version.

Keeping the Structure Alive After Launch

An image bank grows with the organisation. Review the field list with colleagues from time to time, retire fields nobody uses, and add an option when a new question keeps coming back. Tell new colleagues where to look in their first week, and ask anyone who still sends attachments why; the answer points to one more field that makes the image bank even easier. With that habit in place, Beeldbank.nl stays the first place anyone looks for an approved image.