What is our primary use case?
We use Adobe Experience Manager primarily for content management.
How has it helped my organization?
The main benefit of using Adobe Experience Manager in the company is that it lets you easily manage your websites and content. You can also have a static or dynamic website and get any type of content from anywhere. Adobe Experience Manager is also built on Java, so its security is very high.
What is most valuable?
I've used several CMS tools, but Adobe Experience Manager is feature-rich, especially for web security and content management. It's more efficient to manage content on Adobe Experience Manager, and you can do a lot with it, such as updating content at any time, and on any platform, even from mobile or tablet. Adobe Experience Manager is still getting updated daily, and it's the best CMS tool in the market for me.
I like that you can manage assets in Adobe Experience Manager. I also like that the solution has an analytics dashboard that shows you where the traffic comes from, how many clicks come from a specific location, the number of clicks and impressions, etc. Adobe Experience Manager can be accessed by other teams, for example, the digital media department of my company, so the solution can be used and updated per each team's requirement.
Adobe Experience Manager is more than just a web developer tool, as it also allows visibility tracking and has other uses.
I also like that the GUI for Adobe Experience Manager is straightforward and catchy. It has separate folders and icons, so using Adobe Experience Manager isn't tough. The solution is straightforward to use and handle.
What needs improvement?
I haven't seen any areas for improvement in Adobe Experience Manager as it's a full-fledged CMS tool, and Adobe is already working on enhancements for the solution. Adobe is working to make Adobe Experience Manager more valuable and easier to use for any user, even non-technical ones, through multiple components and templates. Day by day, Adobe provides the latest update to Adobe Experience Manager, and if my team needs any particular change, it just needs to be reported to the Adobe team.
As Adobe Experience Manager has a broad scope and a lot of use cases and features, it's a solution that requires some time and effort from you in terms of learning, especially if you're implementing it for different clients, which could be an area for improvement.
For how long have I used the solution?
I've been using Adobe Experience Manager for more than five years.
What do I think about the stability of the solution?
Adobe Experience Manager is a stable solution. It's high-performing and it's better than other CMS tools in the market. Adobe Experience Manager has a quick response time, so within seconds, the server is able to respond to the web browser. In terms of security, the solution is also very secure.
What do I think about the scalability of the solution?
Adobe Experience Manager is very scalable, and it's also customizable. You can customize the template or component based on your requirements.
How are customer service and support?
I'm able to resolve issues myself, so I haven't contacted the technical support team for Adobe Experience Manager.
Which solution did I use previously and why did I switch?
When comparing Tietoevry and Adobe Experience Manager, I'd say that the two solutions are different because, in Tietoevry, the website is only available in English, while Adobe Experience Manager has a multilingual option.
You must create a workspace in Tietoevry before the content gets published automatically.
Adobe Experience Manager is simpler to use, which is why my company prefers using it.
How was the initial setup?
The initial setup for Adobe Experience Manager was straightforward. Not more than four to five people were involved in the deployment of the solution.
How long it takes to deploy Adobe Experience Manager depends on the requirements, but it didn't take much time for my company. You also have the option to schedule the deployment.
What about the implementation team?
We implemented Adobe Experience Manager ourselves, and we didn't need any help because we had keynotes on how to do any test or update any template. We were able to identify what steps to take to deploy the solution. There's also complete documentation on how to do it, and you have the option of getting help. You click, and you'll find relevant Adobe Experience Manager topics, or you can Google or search on YouTube, as content about the solution is available anywhere.
What's my experience with pricing, setup cost, and licensing?
There's a free trial for one month for Adobe Experience Manager, which you can use for learning purposes, then, after the trial period, you'll need to purchase the license. Adobe offers a few plans for Adobe Experience Manager, but I'm unaware of how much my company is paying.
Which other solutions did I evaluate?
I've evaluated the IBM tool, apart from Adobe Experience Manager, and it's a fine tool, but Adobe Experience Manager has more features.
What other advice do I have?
Adobe Experience Manager requires maintenance, but the client side takes care of it. Even during the deployment, the client joined the call, and any needed improvements will be made from the client side, for example, migrating from one server to another. Hence, the maintenance of Adobe Experience Manager is the client's responsibility.
My company has one project on Adobe Experience Manager, with a team of forty people working on different parts.
My advice to anyone planning to implement Adobe Experience Manager is that it has a broad scope in terms of usage, so I recommend that you learn about the solution before implementing it, especially if you have a lot of clients for it.
My company has a partnership with Adobe.
I'd rate Adobe Experience Manager as ten out of ten.
*Disclosure: My company has a business relationship with this vendor other than being a customer: Partner