Why confident Editors are your CMS’s best UX test

A CMS is only successful when it’s confidently used.

And there’s no better way to test that than to look at the people using it every day.

You don’t need a redesign. You need to support the humans using it.

A few years ago, while completing my UX Design diploma, I learned something that now shapes how we approach nearly every project:

You don’t always need to build new things to make an experience better. You need to observe how it’s being used—and remove the barriers in the way.

That same thinking applies to content management.

Your CMS might be perfectly capable. But if the Editor feels overwhelmed, unsure, or out of step with the system, it won’t deliver what your organisation needs.

Editors evolve. Your approach should too.

We’ve worked with Editors for years, and we’ve noticed a clear pattern in how they grow.

We first shared this model at the Plone Conference in Eibar in 2023, and it still holds true today:

• Emerging Editors need support, structure, and encouragement.
• Excited Editors need space to explore, ask, and learn.
• Expert Editors need trust and room to lead.
• Endorsing Editors need to be heard—because they’re often your best advocates.

This isn’t a hierarchy. It’s a cycle. And your support (training, workflows, check-ins, quick fixes) is what keeps Editors moving forward.

When we treat Editors like users with evolving needs, we stop handing over tools and start building confidence.

The best CMS is the one your Editors actually want to use

When Editors enjoy using the system, content gets updated more often. Pages stay relevant. Campaigns run more smoothly. Reports are easier to find.

When they don’t? You start seeing band-aids, workarounds, and long gaps between updates.

A CMS can be powerful and secure and beautiful on paper, but if your Editors are hesitant, then it’s failing quietly.

Confidence isn’t a side effect. It’s the outcome you should be aiming for.

Try this: treat your Editors like users

You don’t need to start over. You just need to start paying attention.

Here are a few practical ways to do that:

• Start by talking to your Editors. Not just during handover or training—but regularly. Ask them what’s working and what isn’t. What tasks feel harder than they should? What’s frustrating, clunky, or confusing?
• Don’t just ask—watch. Sit with them while they update a page or post a story. You’ll notice where they slow down, where they repeat steps, and where they hesitate before clicking. That’s the best kind of user testing you can do.
• Act on what you learn. Maybe it’s a workflow issue. Maybe it’s a permissions tweak. Maybe they just need a new content pattern or shortcut. The fix isn’t always technical—but it is always worth making.
• And when Editors grow in confidence, celebrate it. Encourage them to share tips. Give them space to suggest improvements. Let them shape how the CMS is used—not just follow instructions.

And if, after all of that, you realise that the platform you’re using is getting in their way instead of supporting them, we’d be happy to introduce you to Plone.