Ask a marketing team why the homepage still describes a product the company stopped leading with eighteen months ago, and you will get a technical answer. The site is mid-migration. The CMS makes that section awkward. It is in the backlog.
None of that is the reason.
The reason is that the sentence in question belongs to nobody. Changing it means deciding what the company is now, and that decision sits above the person who noticed the problem and below the person who could settle it. So it waits.
The pattern
The same shape shows up in most engagements:
- Someone spots that the site says something no longer true.
- The fix is small, so it gets filed as a small task.
- The task turns out to require a positioning decision.
- The positioning decision requires alignment between marketing, product and sales.
- Nobody schedules that alignment, because on paper this is a copy change.
The work is sized as an implementation problem and blocks as a decision problem. That mismatch is why it can sit for quarters without anyone behaving unreasonably.
Why it matters more now
A stale sentence used to cost you the visitors who read it. Now it also feeds the systems that answer on your behalf. A language model summarising your company works from what it can find, and it has no way to know that a paragraph is three strategies out of date. It reports it as current, and so does everyone who asks it.
The delay has stopped being cosmetic.
What to do about it
The useful move is not a faster CMS. It is separating the two kinds of change and routing them differently.
Changes that only need execution (a broken link, a missing description, a page that will not index) go into the normal backlog and get done.
Changes that encode a decision (what we call ourselves, who we say we are for, which product leads) get escalated on day one as decisions, with a named owner and a date. Not as tickets.
Most companies have no route for the second kind, which is why everything travels by the first and arrives late. Building that route is usually cheaper than any of the technical work that gets proposed instead.
