I think Adobe Experience Manager can be improved by making it simpler to use. I do not have anything specific in mind regarding needed improvements. I chose seven because if the app were simpler, I could give a nine or a ten. Adobe Experience Manager is not so simple to use, so others should have some experience with similar programs.
Senior Technical Program Manager /Senior Lead Solution Architech- Product Technology & Gen AI at a insurance company with 10,001+ employees
Real User
Top 10
Oct 24, 2025
Adobe Experience Manager needs more optimization. The frequency of components where we have vitals of a page or an app needs to be optimized because these are heavy Java codes along with some AEM developments. The code language should be optimized or they should have some string functions or web plugins to create a lighter version rather than implementing large amounts of code lines. They should start implementing industry best practices which are not currently offered. We perform our internal development for customization at our own pace. We have multiple frameworks that help us in various ways. We are advancing in terms of AI integration. We have already started our own POCs before Adobe implements these features.
Digital Asset Specialist at a retailer with 10,001+ employees
Real User
Top 20
Aug 25, 2025
Improvements could be made, though it's difficult to pinpoint because Adobe Experience Manager has been part of my world for the past several years. Many people complain about the price as it's one of the most expensive tools. I think it might be worth the money for large companies, and I think large companies are going in that direction, but for smaller companies, it would probably not be worth the money.
Infra At Idealake IT Pvt Ltd Head at Idealake Information Technology Pvt. Ltd.
Real User
Top 10
May 15, 2025
The content is created as Adobe Experience Manager has an author, publisher, and dispatcher. However, there is a feature missing where if content is created on the UAT environment and needs to be transferred or synced to the production environment, there is no direct way of doing the sync. Currently, the developer has to create a package and install it on the production environment from UAT to production. There should be a direct sync between the UAT lower environment to the production higher environment. They should optimize Adobe Experience Manager.
While there are many aspects that could be improved, discussing them would require more time. The licensing model is opaque, and technical support could be improved, especially for smaller companies.
Adobe Experience Manager could improve by allowing the reuse of components like a progress bar across multiple pages to make the development process more efficient. Currently, changes have to be made on all the pages manually, which is time-consuming.
In terms of improvement, it's an industry practice for organizations to move towards Adobe Experience Platform (AEP). One of the major benefits is that all marketing efforts for customer engagement, campaigns, etc., are based on server-side implementations. In AEP, we have a very SDK model through server-side implementations. That would be the normal benefits where, without third-party cookies, we can use first-party cookies for our marketing efforts. So that would be another benefit of AEP. There is a little room for improvement in the support.
Area of improvement for Cloud Service: For the last four years, I've been working on AEM as a Cloud Service. I feel the tool has all the features needed for production, but the problem is with skills. Depending on the skill level of the developers building the components within Adobe Experience Manager, you can have a very streamlined implementation or a very difficult one. Tool-wise, the Adobe Experience Manager support team is not very responsive when the user faces issues in AEM as a Cloud Service. If I reach out to Adobe for something, they create a ticket, and then I might wait three to four days for a response. When I have issues, I want an immediate response. On AEM as a Cloud Service, this is the one thing I think Adobe needs to improve. They should resolve issues within a day so everything runs smoothly for the user. Area of improvement for on-premises: For on-premises AEM, everything is managed by us, but since Adobe Experience Manager was not a very big market earlier (though it's growing now), there are limited clients. The cost of the tool is high, and maintenance is heavy – it's very costly. So, the developers working in AEM development might not always have the proper skills to develop the components. For example, in a normal website, we often see carousels which represent your website in a very dynamic way. Now, suppose you have two carousels on the page – one at the top and the next at the bottom. They have different purposes. If I'm a skilled developer, I'll create one component and serve both banners with the same component – a single, dynamic component. This makes it easy for content editors in the production environment to drag, drop, and change the content. But, if I'm not an experienced developer or I don't have knowledge of AEM, I might create two components – one for the top and one for the bottom. Maintenance becomes heavy, and it's harder for the content team to understand which component to use. A less experienced developer might create multiple components for the same function, increasing complexity and challenges. Over the last three to four years, this lack of resources and skilled AM developers has created these kinds of issues.
Senior Technical Consultant at FinXL IT Professional Services
Real User
Oct 12, 2022
The latest trend is to render everything in the client-side framework. For example, SPA or single page application. This is a feature that needs improvement. The cloud deployment pipeline needs to be improved as well.
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.
Chief Technology Architect at a tech services company with 1,001-5,000 employees
Real User
Aug 4, 2020
The programming model could be improved, it's a monolithic solution and that's what we don't like. Some features are badly defined in the solution. It's difficult integrating so we're forced to develop other APIs in order to simplify things. It's a weak feature of the product.
Adobe Communique 5 (Adobe CQ5), currently manifested as Adobe Experience Manager (AEM), is a web-based content management system which is developed to help businesses in offering high-end digital experience to their customers.
I think Adobe Experience Manager can be improved by making it simpler to use. I do not have anything specific in mind regarding needed improvements. I chose seven because if the app were simpler, I could give a nine or a ten. Adobe Experience Manager is not so simple to use, so others should have some experience with similar programs.
Adobe Experience Manager needs more optimization. The frequency of components where we have vitals of a page or an app needs to be optimized because these are heavy Java codes along with some AEM developments. The code language should be optimized or they should have some string functions or web plugins to create a lighter version rather than implementing large amounts of code lines. They should start implementing industry best practices which are not currently offered. We perform our internal development for customization at our own pace. We have multiple frameworks that help us in various ways. We are advancing in terms of AI integration. We have already started our own POCs before Adobe implements these features.
Improvements could be made, though it's difficult to pinpoint because Adobe Experience Manager has been part of my world for the past several years. Many people complain about the price as it's one of the most expensive tools. I think it might be worth the money for large companies, and I think large companies are going in that direction, but for smaller companies, it would probably not be worth the money.
The content is created as Adobe Experience Manager has an author, publisher, and dispatcher. However, there is a feature missing where if content is created on the UAT environment and needs to be transferred or synced to the production environment, there is no direct way of doing the sync. Currently, the developer has to create a package and install it on the production environment from UAT to production. There should be a direct sync between the UAT lower environment to the production higher environment. They should optimize Adobe Experience Manager.
While there are many aspects that could be improved, discussing them would require more time. The licensing model is opaque, and technical support could be improved, especially for smaller companies.
Adobe Experience Manager could improve by allowing the reuse of components like a progress bar across multiple pages to make the development process more efficient. Currently, changes have to be made on all the pages manually, which is time-consuming.
The licenses are very expensive. Customers don't want to invest so much.
In terms of improvement, it's an industry practice for organizations to move towards Adobe Experience Platform (AEP). One of the major benefits is that all marketing efforts for customer engagement, campaigns, etc., are based on server-side implementations. In AEP, we have a very SDK model through server-side implementations. That would be the normal benefits where, without third-party cookies, we can use first-party cookies for our marketing efforts. So that would be another benefit of AEP. There is a little room for improvement in the support.
Area of improvement for Cloud Service: For the last four years, I've been working on AEM as a Cloud Service. I feel the tool has all the features needed for production, but the problem is with skills. Depending on the skill level of the developers building the components within Adobe Experience Manager, you can have a very streamlined implementation or a very difficult one. Tool-wise, the Adobe Experience Manager support team is not very responsive when the user faces issues in AEM as a Cloud Service. If I reach out to Adobe for something, they create a ticket, and then I might wait three to four days for a response. When I have issues, I want an immediate response. On AEM as a Cloud Service, this is the one thing I think Adobe needs to improve. They should resolve issues within a day so everything runs smoothly for the user. Area of improvement for on-premises: For on-premises AEM, everything is managed by us, but since Adobe Experience Manager was not a very big market earlier (though it's growing now), there are limited clients. The cost of the tool is high, and maintenance is heavy – it's very costly. So, the developers working in AEM development might not always have the proper skills to develop the components. For example, in a normal website, we often see carousels which represent your website in a very dynamic way. Now, suppose you have two carousels on the page – one at the top and the next at the bottom. They have different purposes. If I'm a skilled developer, I'll create one component and serve both banners with the same component – a single, dynamic component. This makes it easy for content editors in the production environment to drag, drop, and change the content. But, if I'm not an experienced developer or I don't have knowledge of AEM, I might create two components – one for the top and one for the bottom. Maintenance becomes heavy, and it's harder for the content team to understand which component to use. A less experienced developer might create multiple components for the same function, increasing complexity and challenges. Over the last three to four years, this lack of resources and skilled AM developers has created these kinds of issues.
The solution's pricing and stability could be improved.
Adobe Experience Manager's pricing could be improved.
The latest trend is to render everything in the client-side framework. For example, SPA or single page application. This is a feature that needs improvement. The cloud deployment pipeline needs to be improved as well.
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.
The programming model could be improved, it's a monolithic solution and that's what we don't like. Some features are badly defined in the solution. It's difficult integrating so we're forced to develop other APIs in order to simplify things. It's a weak feature of the product.
With the default template design, it is difficult to manage the different resolutions of images.