Choosing a CMS Around the People Who Will Use It

CMS comparisons tend to focus on features: integrations, plugins, APIs and pricing tiers. Those matter, but the success of a website often depends on something simpler: whether the people who update it find it pleasant and predictable. A CMS that editors avoid leads to stale content, workarounds and frustration.

Start with who edits and how often

List everyone who will publish or update content, how often they do it and what they typically change. A marketing team publishing weekly has different needs from an office manager who updates opening hours twice a year. Both deserve a system that suits them.

Write down real tasks

Create a short list of representative tasks:

1. Create a new page using existing components.
2. Update a service description and preview the change.
3. Add an image with alternative text.
4. Schedule an article for future publication.
5. Revert a change made by mistake.
6. Update a value used across the site, such as a phone number.

These tasks become the basis of any evaluation.

Test with the people who will use it

Ask actual editors to perform the tasks in a trial environment. Watch where they hesitate, what they search for and what they get wrong. Their experience is more informative than any feature matrix.

Preview is not optional

Editors need confidence that what they publish will look right. Good preview shows drafts in the real site design, on different screen sizes, before anything goes live. For headless setups, preview requires deliberate configuration, so confirm it works before committing.

Roles and workflow

Consider who can draft, who can approve and who can publish. Some organisations need a review step; others want to keep publishing simple. Make sure the CMS supports the workflow you need without forcing one you do not.

Structured content versus free layout

Structured content, with defined fields and components, keeps pages consistent and makes reuse possible. Free layout gives editors control but can lead to inconsistency. Most teams benefit from a middle path: a library of components editors can arrange, with sensible limits.

Media handling

Check how images are uploaded, cropped and described, and how files are organised. Large media libraries benefit from search, folders or tagging. Alternative text should be easy to add and hard to forget.

Ownership and maintenance

Hosted CMS services handle infrastructure and updates for the CMS itself, while self-hosted options give more control and more responsibility. Neither is automatically better. Decide who will maintain the system and choose accordingly.

Plan training and documentation

Even a well-chosen CMS needs onboarding. Short, task-based guides with screenshots of your actual configuration help editors far more than generic documentation. Schedule training close to launch and offer a follow-up session after editors have used the system for a few weeks.

The best choice is the one people use

A CMS that fits your team's habits and skills will keep your website current. Choosing around the people, then confirming the technical fit, leads to better outcomes than the reverse. Record the results of your trial tasks so the decision can be explained later to anyone who asks why a particular system was chosen.