Add comparison

Likelihood to Recommend

Adobe Experience Manager

If you have a number of smaller parts of your organization that you want to maintain the same look & feel as the rest of the organization, it is easy to create a base site and then let them customize. Also, if you have contributors of content who are not involved in the web site maintenance - our professors, for example - they can enter the text on a basic page which is then incorporated through tagging

Likelihood to Renew

Adobe Experience Manager9.0

Based on 5 answers

If I had the choice to renew, I would. Adobe CQ is one of the better CMS's I've been able to use. It's well organized, fast and easy to use. Although it is a little high in price, the fact that it does a good job justifies the decision to renew

Usability

Adobe Experience Manager10.0

Based on 2 answers

I personally feel that AEM is very intuitive to use from an authoring standpoint. The entire CMS was engineered around the author. Everything about AEM is geared to helping authors generate and maintain content. There are ways that tool tips can be customized so that any individual could simply hover over and be guided step by step on how to author web content

Implementation

Adobe Experience Manager8.7

Based on 2 answers

Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint

Alternatives Considered

We selected Adobe CQ mostly for the ease of page authoring in brought to our non-technical staff. Powerful and simple UI widgets made it very simple for our merchandiser to create, edit and publish new pages. It also allowed us to customize those widgets to fit their needs while keeping the same clean experience. We also saw a plus in the ability to run activation workflows based on our own organization hierarchy, which helped make sure the right pages were exposed to the right eyes before going live. Overall, it was the mixture of user-friendliness of the authoring interface with the robustness of the technology stack that convinced us to go with CQ.

Each project has a specific set of requierments and these drive our CMS decisions. I tend to think of DNN Platform as a good option when the hosting requierments are complex or specificly defined and there needs to be a level of custom options created. The roles and credentialling is also somewhat better than most.

Return on Investment

Our direct business landing pages have seen an increase in ROI since switching to Adobe Experience Manager.

Our non-direct pages have seen a severe drop-off in traffic and conversions since the switch to Adobe Experience Manager. The more creative, editorial-type content that used to be imperative to our site is now relegated to second tier. Just getting a "content hub" with this site was a beast of a project.

The overall efficiency of our web team has increased with bulk edits, so that they can make single updates and impact our multiple sites. This is a huge money-saver for team staffing.