Your CMS should get out of the way
If publishing hurts, you won't publish. The best content strategy in the world loses to a clunky admin screen, every time.
Try this today. Open your website’s admin, change one headline on one page, and time how long it takes.
If the answer is under two minutes, stop reading and go enjoy your afternoon. If the answer involves a support ticket, a developer, a staging environment, or the phrase “I think only Jeff knows how,” keep going.
Here’s the uncomfortable law of content: friction beats intention. Every time. You can have a beautiful editorial calendar, a committed team, and genuinely useful things to say, and none of it survives contact with a publishing tool that fights back. If updating the site hurts, the site stops getting updated. Not because anyone decided that. Because at 4pm on a Tuesday, with nine other things due, nobody volunteers for pain.
We’ve watched this happen more times than we can count. A company invests in a redesign, everyone’s energized, and eighteen months later the most recent entry on the news page is the post announcing the redesign. The strategy didn’t fail. The tool did, one small discouragement at a time.
A solved problem
The frustrating part is that this is a solved problem. A CMS that respects its editors isn’t exotic or expensive. It looks like this:
- Fields that match how you actually think. A team member is a name, a title, a photo, and a bio, not a blank canvas where you rebuild the layout by hand and hope it matches the others.
- Nothing you can break by accident. Editors should be able to move fast precisely because the design is protected.
- A preview that tells the truth.
- Labels written in your language, not the developer’s. If your team says “locations,” the admin shouldn’t say “regional entity nodes.”
Notice what’s not on that list: infinite flexibility. That’s the trap. The systems that let editors control everything are the ones editors end up fearing most, because every page becomes a design decision and every design decision is a fresh chance to get it wrong. Good structure is a kindness. It means the person updating the holiday hours gets to think about the hours, not the padding.
Where the content goes instead
You can usually spot a hostile CMS without ever logging in, because the content finds somewhere else to live. The case study that should be a page becomes a PDF attached to emails. Announcements go out on social and never make it to the site. Someone maintains a shadow version of the pricing in a spreadsheet because updating the real one is a whole thing. The website slowly turns into a brochure with a copyright year nobody trusts, while the actual communication happens anywhere the friction is lower.
Water finds the crack. Content does too.
There’s a quieter cost, too. When the tool is hostile, people conclude they’re bad at websites, and they’re not. We’ve sat with sharp marketing teams who apologize for their own admin screens, as if the confusion were a personal failing rather than a design one. An editor who dreads the CMS isn’t a training problem. They’re a symptom.
Who the admin is for
So when we build a site, we build the admin side for a specific person: whoever will be using it on an ordinary Tuesday, long after the launch excitement is gone and we’re not in the room. That person isn’t a developer and shouldn’t have to think like one. They have a job, the website is a tool for doing it, and the measure of our work is whether the tool disappears into the task.
Which is the real test of a CMS. Not the feature list, not the demo, not what it can theoretically do in the hands of an expert. Whether the fifth-most-technical person on your team can publish something on a busy afternoon without dread.
A good CMS is like good plumbing. Nobody compliments it. Things just flow.
