Liferay Digital Experience Platform (DXP) vs. Planview IdeaPlace

Liferay Portal is a framework which comes with a fine grained security/permission model, (Web) Content Management, Authentication and Authorization, outbox portlets with different features to manage content or users. So if any business application has below questions then I can recommend not to use Liferay as a platform.

• Application is big but not content or user driven.
• Application with few static contents.
• Application with batch transactions(DB) i.e. insert , update db records in batch.
• Application with ERP capabilities.
• Application with Big Data support.

If you have a community with more than 100 active users, and you're looking for ideas around operational improvements that can be acted on in a 6-12 month window, Spigit will work great, and it's one of the best options out there. If you're trying to customize the platform much, you should plan on paying Spigit's service group to do that for you, because it's not easy to do yourself. If you're looking for ideas that will take more than about a year to implement, Spigit is as good as anyone else because that's a really tough thing to do in an innovation community!

Incentivized

• Personalization
• Business to client relationship
• Customer management is better.

Incentivized

• Acknowledges and supports the culture around the problem and market it is trying to serve. Just using the platform won't solve our problem, we need a cultural shift and Spigit has helped support that process.
• Customer service - just overall amazing service. Responses are very quickly turned around, they've gone the extra mile many, many times. They are also very open to platform improvements and take feedback very seriously.
• As the system administrator, I feel their platform incorporates a great balance of templates, out-of-the-box formatting, etc., and customizable content. In a nutshell, we are able to do what we want but we don't have to spend forever to do it. We can use what they have or we can add in our own design.

• Harder to get started
• Enterprise level of options can cause confusion
• Development documentation could be better

Incentivized

• There are many ways to configure the solution. Some features make more sense to use at times and should be hidden from users at other times. It would be nice if Spigit had pre-defined configuration templates that reflect the experience and knowledge of their current customer's experience using the software and not just a 1 size fits all base configuration. The good news is with a little experience, these configurations can be created as saved templates.

We are currently using Liferay Portal and plan to keep using it.

Incentivized

Most platforms had a nice UI, this wasn't the differentiator. What it came down to was mostly around we don't know what we'll need in the future:

• Market leadership: on stable ground, not going anywhere
• Thought leadership: improving the software, inspiring new ways to use it
• Highly configurable platform: supports use cases we don't know we even need right now
• Strong services if you need them: always there if you run into trouble or are short staffed

• Create a good environment
• Resolution is not so much better.
• Have a long things to do.
• Content management is better off.

Incentivized

• Firstly, it is hard to define or describe an ROI for an innovation project (and tool) that is in its experimental phase... But a positive is the impact in the overall engagement of employees, especially in overpopulated structures where it is not easy to "become visible, and the smart ones wait for a chance like this platform.
• Where a clear and strong sponsorship is in place, this platform can stimulate ideas that can potentially have a great impact in services improvement
• Based on our specific limits in engaging top management, we still cannot see a speed in products or processes improvement.

Incentivized