Thursday, May 30, 2024

Common Pitfalls of a CMS Purchase

Whether you evaluate a CMS utility as part of a typical internet site redesign, or your commercial enterprise is scaling up, and you’re equipped to jettison your Excel spreadsheets, I desired to the percentage a few commonplace pitfalls you would need to avoid.

Common Pitfalls of a CMS Purchase 1

Choosing a Geek pleasant CMS

In an attempt not to alienate my IT pals, let me clarify the title: permitting an IT man or woman to be the sole selection maker inside the CMS buy is a horrific idea. Please, don’t throw your mouse at the display screen- it’s not anything personal! However, it should be said that, at the stop of the day, selecting a CMS is content material and technical exercise – no longer strictly IT.

Although it is essentially a software program software, individuals from both the technical and non-technical administrative teams must be included immediately in the initial requirements definition section. However, it should be considered in every subsequent section at some stage, with a slightly faded entrance until the actual buy. The point is that you need to ensure that the content material team and other give-up users are introduced immediately as well. Side be aware: make certain that the opposite give customers are ed- depending upon your needs, this can even consist of HR or the CFO.

While this wasn’t the case, what I’ve seen play out is twofold. Suppose the content crew is excluded early on. In that case, the requirements tend to be primarily based totally upon the wishes of the technical group, and perpetually, what happens is that the actual admin interface and workflow worries tend to be minimized. Conversely, suppose the technical crew is excluded early on. In that case, the users’ needs are reflected, and the technical necessities get left in the back, simplest to be introduced to mild at some stage in the implantation section. Either way, moving ahead as a united front is much simpler than looking to dance backward. In a few worst-case eventualities, I’ve seen the CMS take months versus weeks to enforce, with the net result being a loss of capability revenue.

At the top of the day, there needs to be a nice compromise reached among the two aspects. The IT branch will get a robust, scalable gadget, and the administrators get a cleaner-to-apply interface whose workflow abilities will mirror those already in life. As a result, the end consumer – your target audience – will win because their desires will be satisfied by using top-notch, engaging content material that is effortlessly available at all times.

I think that pre-constructed is better

A fundamental part of building usable systems entails knowledge of the everyday workflow of the staff interacting with the website online and how it pertains to the tasks they need to complete. This choice to provide a device that incorporates the cease-user’s real wishes is often at odds with the pre-constructed systems presently in the marketplace (e., G. Joomla, Drupal, WordPress, etc.).

These systems sell an overload of features and try to portray everything to anybody’s ideal. The problem I’ve seen growing is that only a small percentage of functions ever grow to be used. I’ve looked through a few Admin panels that could be used to navigate The Space Shuttle Atlantis. But, after scoping out the real everyday workflow, it became apparent that those capabilities tended to distract and frustrating because of lack of use and knowledge.

The best analogy is MS Word and all its multitudinous functions that observe you in the face every time you open it to begin a new file. Go beforehand, look up at the top of your screen, and start poking around – what number of the real capabilities do you use daily? It’s cool that they may be there; however, if your revenues have been tied to MS Word’s performance, how many of them might you maintain?

Common Pitfalls of a CMS Purchase 2

Bigger (greater features) isn’t always higher. That’s why so many organizations, in the end, move the custom-designed CMS direction. Ultimately, it boils down to your wishes – your workflow, not someone else’s preconceived notions.

Yes, I get it; many massive groups use pre-built CMS systems to start, and it’s constantly reassuring to be in an appropriate agency. You may not realize that those groups also have internal teams reconfiguring the systems to fulfill their wishes, run the real everyday capabilities, and use common safety updates. Translation: they were given a free template as it’s easy, but they spend huge amounts of money because they want to tailor the systems and preserve them easily.

Although I’ve maxed out my analogy card, I will play my bonus analogy for the freeware mode of thinking: the open-supply Linux OS. Many groups insist on strolling Linux – if handiest because they do not want to be tied to Windows. Yes, it works for them, but at the end of the day, they’re all paying developers to customize it to their wishes – best the download became loose.

Being Short-Sighted

It is vital not to forget what you want currently but what you will need the CMS to aid inside the destiny. Do you have plans to encompass extra content – or build online bureaucracy or surveys? Perhaps there is an aim for additional e-commerce functionality on your web page within a year. Maybe a part of your business enterprise’s approach consists of frequent mergers or acquisitions (consequently requiring a CMS that scales easily and gives a legitimate technique for repository aggregation).

Make certain you outline known (and a few speculative) destiny requirements as part of the requirements-amassing technique. Otherwise, you can find yourself looking for a substitute CMS nicely before you’ve gotten the go-back on investment out of the first.

Asking ‘how,’ no longer ‘what’ questions.

The choice manner must focus on asking ‘how’ questions rather than ‘what’ questions to build clear expertise in the goods’ strengths and weaknesses. This is achieved by taking things back to the underlying commercial enterprise need and asking your improvement companion to outline how they can build that CMS to suit that want.

In practice, the success of the CMS venture rests on how nicely the answer suits the daily requirements of the authors and site directors. This comes back to how the product works in detail. While stating: “The CMS should provide effective and bendy workflow skills” in your RFP – or inner documentation – sounds appropriate; however, in the factor of truth, how are the workflow capabilities simply going to be used, and by whom?

Flesh it out, be unique – take a survey on your workplace and chart out the answers. The funny factor is that this process might expose redundancies or disclose weaknesses before the purchase. How does the blog truly get written, after which it is located on the website? How does the individual liable for pictures locate, save, and retrieve gadgets? How does your Facebook web page get up to date?

Common Pitfalls of a CMS Purchase 3

Asking the ‘how’ will assist in clearing away some of the smoke and mirrors often related to pre-packaged CMS applications. It is a nice way to get the total benefit of customizing the CMS to suit your workflow and no longer get slowed down with capabilities that could grow to be redundant (and steeply priced).

RFP files should serve as a substitute recognition of the important of selection standards to drive the evaluation and differentiation of the products. There are hardly ever greater than a dozen key selection standards in the middle, at the side of helping requirements (documented as being of lower significance) – persist with them.

Are there extra problems that can crop up? There is no doubt about it, and that’s not even considering the technical troubles regarding integration. While this wasn’t meant to be exhaustive, it needs to get your questions in the right direction and, with a bit of luck, attain a solution that drives your commercial enterprise ahead and simplifies the lives of these behind-the-scenes.

Jenna D. Norton
Jenna D. Norton
Creator. Amateur thinker. Hipster-friendly reader. Award-winning internet fanatic. Zombie practitioner. Web ninja. Coffee aficionado. Spent childhood investing in frisbees for the government. Gifted in exporting race cars in Orlando, FL. Had a brief career short selling psoriasis in Ohio. Earned praise for getting my feet wet with human growth hormone in Minneapolis, MN. Spent several years creating marketing channels for banjos for farmers. Spent 2002-2010 merchandising karma for no pay.

Latest news

Related news