Item: Appian
Rating: 9
Author: Verified User

Use Cases and Deployment Scope

Appian is being used to digitize and improve operational efficiencies within our organization. As with all digitization initiatives, Appian is used where a combination of users and processes are involved in business operations. We also aim to move away from legal Excel spreadsheets to workflows.

Pros and Cons

Workflow automation
Rapid time to market of applications
Starting with version 21.1, Appian also does a great job at allowing developers to compare code changes from one version to another and highlighting differences
Learning curve with Appian is lesser than with products like Pega

Appian could introduce version control for certain key components like record types
Parallel development of code with Appian is really hard when multiple developers share the same objects. This is an area where Appian could do better.
Appian can keep getting better at robotic process automation to make it easier for 'low-code' developers without much knowledge of Java programming to implement RPA.

Return on Investment

Rapid time-to-market yielding operational efficiencies

Support Rating

My experience with Appian support (especially premium support) has been stellar. I find that customer support engineers research the question thoroughly and provide appropriate solutions, with multiple options at times. They were also able to promptly engage other subject matter experts where appropriate. They also keep providing timely updates on tickets.

Usability

As mentioned earlier also, Appian comes with its own set of rich user interface capabilities, components, as well as recommended design patterns. End users have at times wanted some flexibility and alternative options that are not provided out of the box. Screens can also take some time to load when significant and complex processing is involved and designing for usability while conforming to 'acceptable' response times can be challenging.

Alternatives Considered

Pega Platform

Appian has a lesser learning curve than Pega. Pega uses a combination of directed and pattern inheritance and architects need to design bearing these in mind. While the intent behind this approach is to allow for reuse of rules to allow for efficient enterprise-wide design, it can result in some over-engineering.

Key Insights

Do you think Appian delivers good value for the price?

Yes

Are you happy with Appian's feature set?

Yes

Did Appian live up to sales and marketing promises?

Yes

Did implementation of Appian go as expected?

Yes

Would you buy Appian again?

Yes

Likelihood to Recommend

Appian is best suited when the need for rapid time-to-market of business functionality outweighs the need for very specific user interface requirements. Appian comes with a rich set of user interface capabilities and implementing a UX design that operates within the realm of these capabilities is ideal. On the other hand, if the UX design is rigid, it makes for a poor use case for Appian.

Fantastic product always striving to become better

Overall Satisfaction with Appian