Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
Jive-x (Discontinued)
Score 4.3 out of 10
N/A
Jive-x (formerly Jive Engage) is Jive's external facing community platform for prospects and customers. It is a leading product in the space and most often competes with Lithium Community and Telligent Community.
So one of the primary focuses in the company has been SEO, and it does not seem well suited to SEO. For instance, how we set up the alt image tags. It's pretty tricky and there are multiple steps to do that. So I would like to see an Adobe Experience Manager that is more focused on out-of-the-box solutions for SEO, schema coding, alt image tags, and other sorts of SEO functionality to have that more built into the vanilla version of the product. Well suited? It's very good at scalability. And because we're managing such a large number of hotel properties, it works well for an enterprise.
Jive-x is great for external communities for support deflection or customer communication and document sharing/editing. If you spend the money on the available add-ons and integrations, you could use it for customer education/learning. It's less appropriate for use as a revenue -generating tool or a lead-generating platform.
It is able to support our incoming volume. We're one of the largest in what we do in the country, and we've not had any issues in terms of how it performs, or how it scales our customers coming in. It's a fairly stable platform. It is also a very intuitive platform in us being able to give our business users the ability to come make changes and request additions without going through a huge lift in getting those requests implemented. It has also been a very developer-friendly platform for my team to be able to develop, adapt, and build. We're also expanding on being able to use AEM both as a pure content management solution and also as a headless content solution. So that way we are trying to build a unified content platform that would allow us to create, publish, and manage content across channels from one place. So it's fairly intuitive that way. It's fairly scalable. Obviously, the modern tooling helps, but overall I think it's been a good experience.
I write these from the perspective of the Community Manager - You can choose your level of moderation on Jive to match the policies of your organisation. From full on content pre-moderation to to completely reactive moderation, you can take your pick. We chose the latter end of the spectrum, trust your colleagues to be professional and you will be rewarded with professional content.
The ability for users to set up their own groups very easily with out the need to revert to developers is great as this allows individuality. This allows for organic growth with out impact on the budgets of departments and teams to get their work done on Jive. The option is always there to get 'someone in to fancy it up a bit' however you will find that your own people will develop those skills themselves. Your users will also learn from each other and you should actively encourage stealing of best practice from across your organisation.
The knowledge repository or Question and Answer features are the most value-adding for me. Having searchable history that allows your to get answers quickly so the next question can be asked is the reason why you should have a collaboration platform in the first place, Jive makes that easy.
Single Sign On has been a excellent addition for us, if Jive does not make your colleagues lives easier then they won't use it.
You can customize and brand Jive to reflect your company identity.
I think some of the key things that can be done better is today we have more point solutions for different things like personalization. We have Adobe Target and for email marketing, we have Adobe Campaign Marketer and all that kind of stuff. But truly I have worked both as an implementation partner for Adobe as well as now I'm a client of Adobe. Being in both those shoes, I can say that we can do a lot better in terms of beefing up the capabilities of AEM, bringing personalization and search and content search experience closer together. It would definitely put Adobe Experience Manager in a different league if we can bring all those personalization capabilities together. I think initially the content management systems, the market was mostly meant to serve static sites. It never matured into that full-scale content personalization being married together. I think that's one area where if those integrations rather than being point solutions, if those capabilities can be made more native to AEM, I think it would definitely be a big sell for a lot of customers.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
For a large company the cost can quickly escalate so this must taken into account when renewing. For me, the decision to review will be taken with upgrading to the cloud version in mind as well. My power users love Jive for it versatility but it is important to note that you must be prepared to constantly train and coach the non-power users
From our learning curve until we got better. I'd say as we're moving forward and we're making more customizations and we're getting used to it, I'd say it's about a seven or an eight. But as more innovations and more information comes out from Adobe as they make more changes and they make improvements, I'd say they're getting probably about an eight right now.
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
It works wonders. My only gripe would be that there are some customizations you can't make without hiring a vendor with coding experience to implement them.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
The support has been fantastic when we have been trying to code our own apps. Jive have went above and beyond what was required to help us out. Bugs fixes are generally very good and they are upfront when they are unable to help or a 'problem' is actually in need of Professional Services
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
At Canadian Tire Financial, in the time I've been there, we've always used AEM, but in past places I've used WordPress, I've used Squarespace. Things that are more general user-friendly where you're like building your own blog or you're creating a small business website where it's basically just text, you're not intaking information or something like that. I think the customization options in AEM are huge. My experiences with WordPress were pretty straightforward. Again, it was like, I don't know, like college newspaper website or something like that where you're just like putting content up for people to look at. You're not necessarily taking in any other information. Maybe you might allow people to log in or something and save articles or something pretty straightforward, but then even then I remember that stuff taking me forever to do, to figure out and scroll through tons and tons and tons of documentation. It's just not fun. No one enjoys doing that and then even then you might not have the answer available to you. And that's so frustrating. Hey, it's super user-friendly, figuring out the content editor is pretty straightforward. You're not clicking around and being, "what the heck am I looking at?" Or you're not looking at a bazillion menus to be like, "maybe the thing I want is in here." I can't stand that. I want to be able to look at a page, see what I'm going to be getting in production, and then publish it. I don't want to look around in menus to figure out how to add something to a page.
For the money, it just happens to fit best with our original use case. Now that it's been sold to Aurea, which essentially halted any support or dev for the product before selling it off to Lithium, we will have to eventually move off of it (this assumes Lithium won't hire devs for code they didn't build, and that's not a bad assumption). So, while I recommend it, it's with the caveat that it's been sold and will be evolving in the near future.
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
This actually has been great for our websites. In the time that I've been with the company, we've seen at least the profitability of our websites because we are measuring that through analytics. We've seen it double since using it. We were using it when I first started with the company, but we've gotten better at how we're using it and really optimizing the use as well as the design. I think that that's made a huge difference. We've seen a huge jump in the performance of our websites with maintaining users and the e-commerce side of it.
Hard to quantify the results...but I also left the company before we had built a mature instance of Jive in-house so the final results/impact were yet to be fully realized and measured.
The use of Jive brought together multiple-departments for the first time in our 50+ year old company to truly build an "end-to-end" approach to our marketing/sales/fulfillment/customer service engine. It was truly phenomenal to watch how the internal life-cycle of a prospect-turned-customer literally transformed and unified our inter-departmental teams through the use of Jive Engage.
