What many site owners feel is not a shortage of features. It is the sense that much of what exists is almost done.
WordPress is rarely short of ideas. Every year brings new editor capabilities, new design tools, new APIs and new ways to connect it to other software. What many site owners feel, though, is not a shortage of features. It is the sense that much of what exists is almost done: it works in the demo, then surprises you on a real site.
The thesis here is that WordPress, and the ecosystem around it, would serve site owners better by finishing what it already has than by adding more. That means clearer settings, fewer surprising defaults, consistent interfaces, better error messages and workflows that carry you all the way from start to end. It is an argument about priorities, not about talent. The people building WordPress and its plugins are capable. The question is what the next hour of their time is spent on.
What “unfinished” actually looks like
“Unfinished” can sound like an insult, so let us be specific about what we mean. A feature is finished when a person who has never seen it can use it, understand what happened and recover from a mistake. It is unfinished when any of these is missing.
- Dead ends. You start a task and reach a point where the interface offers no next step, or sends you to a different screen with a different design.
- Silent failure. Something does not work and nothing tells you why. A form that does not send, a setting that does not apply, an import that stops halfway.
- Inconsistency. The same action is called different things in different places, or the same setting appears twice with different effects.
- Option sprawl. A settings page offers forty toggles, most of which only a developer could explain.
- Missing edges. The feature works for the main case and falls over on the second: a long title, a right-to-left language, a keyboard-only user, a slow connection.
None of these is a missing feature. Each is a gap between a feature existing and a feature working. Most site owners lose more time to those gaps than to anything the product cannot do.
What WordPress itself says it values
The argument is not foreign to the project. The WordPress philosophy page on wordpress.org states that “Every time you give a user an option, you are asking them to make a decision,” and sets out a principle of designing for the majority, describing many end users as non-technically minded people who do not know what AJAX is, nor do they care about which version of PHP they are using. On simplicity it says: “We’re never done with simplicity.”
Those lines describe finishing, not accumulating. A project that treats simplicity as never done is committing to continual refinement of what exists. Whether the real roadmap lives up to that is a fair question, and different people will answer it differently. The point is that the standard is already written down, and it favors the approach argued for here.
Why features win the incentive contest
If finishing is so valuable, why does it lose so often? Because of how work gets noticed.
A new feature is an announcement. It has a name, a release note, a demo video and a line in a comparison table. Finishing work is the opposite. Fixing the wording of an error message, aligning two screens, or making a settings page shorter produces no headline. Nobody writes a comparison chart about it.
The same applies to commercial products. A plugin vendor competing for attention in a marketplace is tempted to add checkmarks, because checkmarks are visible on a feature table. A vendor who spends a quarter on polish has little to show for it on a screenshot. Reviews might reward it eventually, but slowly and indirectly.
Open source projects have a variant of the same problem. Contributors tend to work on things that interest them or that they need. A bug in a rarely used corner of the interface is nobody’s passion. This is a structural pressure, not a personal failing, and it explains why the same rough edges can survive for years.
Where this shows up for site owners
You see it in daily work, not in roadmaps.
The editor. The block editor is powerful, and it keeps gaining capability. But owners still ask basic questions: why does this block look different on the front end, where did that spacing come from, why is the list view hiding what I need? Our advanced guide to patterns and the Query Loop block shows how capable the tools are, and also how much understanding they ask of you. If you are new to it, our tutorial on block editor basics is a better starting point than the feature list.
Settings and plugins. Plugin settings pages are the clearest example of option sprawl. When a plugin exposes every internal switch, it passes its design decisions to you, and you are usually in a worse position to make them than its author.
Updates. Updating WordPress, themes and plugins is a routine every owner needs, and it is full of small anxieties: what changed, what could break, how to roll back. Our guide to the risks of automatic updates exists because that routine is not smooth enough yet.
The admin. Slowness in the dashboard, notices that clutter every screen and menus that grow with each plugin all fall under “finishing.” Our piece on fixing a slow WordPress admin covers some of the practical fixes, and the fact that such a guide is needed says something.
The strongest counter-argument
The obvious objection is that WordPress has to keep adding capability to stay relevant. Competing platforms ship new things constantly, and a project that stopped adding features would fall behind. That is a serious argument, and part of it is right.
Some features are not optional. Security improvements, accessibility requirements, performance work and support for new web standards have to be built. And new capability sometimes opens up whole categories of use that polish never would. A platform that only refines what it has can become a very well-sanded museum piece.
There is a second point in fairness. WordPress’s scale makes finishing hard. It runs on a huge range of hosts, PHP versions, themes and plugins, and any change to a screen has to survive that variety. Backward compatibility is a real commitment, and it makes some kinds of cleanup slower than they would be on a platform that controls its whole stack.
So the claim is not that features are bad. It is a claim about balance and about a failure mode. When capability is added faster than it is finished, the unfinished part compounds. Every new feature inherits the rough edges of the layers beneath it, and every plugin built on top has to work around them.
Finishing is also a competitive advantage
The “stay relevant” argument can be turned around. Ask why people leave a platform. Rarely because it lacks one feature. More often because it is frustrating: confusing, slow, brittle, or unpredictable.
Site builders who feel in control of the tool, and clients who can edit a page without calling someone, are more loyal than people who admire a long feature list. A smooth, boring, predictable workflow is the product many owners are trying to buy. A plugin that finishes the unglamorous work, such as sensible defaults, clear errors and a short settings page, can beat a bigger rival on exactly the points that matter after the first week.
That applies to WordPress as a whole as well. A reputation for reliability is harder to build than a reputation for capability, and harder for a competitor to copy.
What you can do as a site owner
You cannot change the WordPress roadmap, but you can apply the same standard to your own choices. Here is how.
- Judge products on the second week, not the first hour. Install, set up, break something deliberately and see how the product responds. Does it explain the problem? Can you undo it?
- Prefer shorter settings pages. A plugin with a few clear options and good defaults has usually made more of the decisions for you, and made them deliberately.
- Read the changelog for fixes, not just features. A changelog full of fixes and refinements suggests a team that finishes. A changelog of only new modules deserves a question or two.
- Test on staging. Rough edges show up when updates meet your real combination of plugins. Our staging site guide shows how to set that up.
- Report problems well. A clear bug report, with steps to reproduce and your versions, is the most direct way for a user to help finishing happen. Maintainers cannot fix what they cannot reproduce.
- Keep a maintenance routine. Our maintenance checklist turns small anxieties into regular habits, which is its own form of finishing.
- Do not install a feature you will not finish setting up. A half-configured plugin is the owner’s version of an unfinished feature.
Defaults are where finishing hides
The clearest test of whether a product is finished is what it does before you touch a setting. A default is a decision made on behalf of every user who never opens the settings page, which is most of them. If the default is poor, the product is poor for most people, whatever the options allow.
Good defaults are slow, patient work. They mean deciding what the typical site needs, testing it, and being willing to leave out the clever option that would please a handful of power users. They also mean having the discipline to change a default only when the evidence is strong, because changing it affects everyone who relied on it.
When you evaluate a plugin or theme, install it on a clean site and do nothing. Look at what appears on the front end, what the admin adds, and what you are asked to configure before anything works. A product that needs twenty minutes of setup to reach a sensible state has pushed its unfinished work onto you.
The edge cases are the product
Features are usually built for the main path and tested there. Real sites live on the edges: a post with no featured image, a menu with forty items, a name with accents, a visitor using only a keyboard or a screen reader, a phone on a slow connection. Each of those is a place where a half-finished feature shows its seams.
Accessibility is the clearest case. It is not an extra feature to add later. A form that cannot be used with a keyboard, or a control with no accessible name, is simply a form that does not work for some people. Treating those cases as part of the definition of done is what finishing means in practice, and it benefits everyone, not only the people who need it most.
What it would take
For the ecosystem, the change is cultural more than technical. Teams would need to treat error messages, empty states and default settings as first-class work. Release notes would need to credit fixes as much as additions. Marketplaces and review sites, including ours, would need to look past feature tables and ask how a product behaves when things go wrong.
None of that is simple, and none of it is exciting. That is the point. The work that makes software feel complete is usually quiet, and it is rewarded only when it is missing.
Conclusion
WordPress does not suffer from a lack of capability. It suffers, in places, from a lack of completion: dead ends, silent failures, inconsistent screens and settings that ask too much. Those cost site owners more time than any missing feature.
The project’s own philosophy points the same way. Fewer options, designed for the majority, never done with simplicity. The most useful thing you can do as an owner is to apply that standard to your own stack: choose products that finish what they start, test them before you rely on them, and report what is rough. Fewer features, better finished, would be a very good year for WordPress.