@Ken Newman -... Mr. Gallagher prefers WordPress and was frustrated with having to go with another software, and so listed the faults/limitations that made him do it. What’s wrong with that?
[emph. added]

Mr. Gallagher asserts that he is going to resolve the (primarily business/personnel) issues he has encountered using WordPress, by using a different software solution in its place.

Well. The current representatives of a long line of Celtic retrogrades assured me as a child; "If you salt a bird's tail, you can catch it".

More than a scatter of those following this discussion, hear the leader of KevinJohn Gallagher enterprises claiming he is going to fix the problems he ran into with WordPress, by salting a bird's tail.

Drupal? Joomla? In-house roll-yer-own?

There are certainly problems involved in deploying any of the alternatives to WordPress. It is always a mix of advantages & frustrations, with any solution that is chosen.

If there is more than one personnel in an organization, any CMS-type tool that is deployed organization-wide will please some and not others. And if it is a one-person show, the solution will please her in some contexts, and have her hammer-throwing her monitor through the window, in other contexts.

It is too convenient to assert that one has at hand a solution to fundamental/universal issues, which has eluded thousands of other top-level professionals, while demurring to reveal anything about the solution.

As soon as Mr. Gallagher lets on what he will do instead of WordPress, his listeners will be able to table solid arguments that his selection will also be the source of friction & frustration within his organization.

What is this alternative solution?