Appian IS transformative
Updated March 08, 2019
Appian IS transformative
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Appian
We use Appian in our R&D organization. We use it to build solutions for complex processes that require something more advanced to efficiently support them. These are processes that were quite difficult to solution with traditional methods. Appian allows us to address these highly complex processes. Also, there are many solution requests in our backlog that Appian can now efficiently fulfill. These would be spreadsheet or document based processes that are currently inefficient. With Appian, we can build out solutions for them to increase efficiency. Furthermore, the processes can now talk to each other so we can make gains that were simply not achievable before.
- Appian is great for sharing information across processes. The platform is designed such that objects from one application can be simply referenced in another (if your security permits it, of course.) This makes information sharing across processes quite simple from a technical implementation perspective.
- Development cycles on Appian are shorter as compared to traditional methods. We're able to churn out solutions at a higher velocity.
- Building a user interface is fast and simple. It has limited widgets but meets our needs 95% of the time out of the box. Appian regularly enhances there UI capabilities.
- Appian has drag and drop UI building, so a proficient Appian designer can build the interface in real time along side the business stakeholders.
- Advanced functionality requires use of the Appian expression language. The more advanced the logic, the harder it is to build with the expression language. This means development expertise is more relevant if you need advanced functionality, which I imagine applies almost all the time. I would much prefer if they allowed some common language such as JavaScript out of the box.
- Debugging has proved difficult. It’s easy for developers to get the app to or feature to a “working” state but it needs robust alpha testing.
- Deployment can be tricky. When a solution gets big and there are many teams and dependencies, it needs a careful process to ensure things don’t break.
- Reasuability of Appian objects is both a pro and con. Reusing objects across apps may be more trouble than its worth because of creating heavy dependencies. Experience is helpful to strike the right balance.
- We see that complex processes could now be managed on the platform.
- There are certainly productivity gains when we replace manual, spreadsheet based processes with Appian.
- We expect to see great synergy once we have several processes on the platform. We expect that will come from new information sharing across processes that was simply not feasible in the past. There are new doors yet to be opened in this respect.
I have helped in an Appian vs. Pega evaluation. They are both great platforms and I imagine will help any enterprise that leverages them properly. I felt Pega had more features and capability compared to Appian. However, we chose Appian in the end because we felt it's more flexible than Pega. In that regard, we felt we can use it for small apps, complex apps, or behind-the-scenes automated system processes. Appian apps are set up as a bucket of objects, and you use and connect them how you like. We felt we can do "this or that" with Appian. It it can meet a wide variety of uses while remaining pliable such that we can keep our apps up to date with the pace of business change. Also, we felt Appian would be a great partner, which they have been.
Appian Feature Ratings
Using Appian
Research and Development
Evaluating Appian and Competitors
- Product Features
- Product Usability
- Product Reputation
- Analyst Reports
Flexibility. The platform can keep pace with business change.
If given the opportunity, I would have more thoroughly investigated the availability of experienced Appian resources across our global regions. It’s hard to find and retain Appian experience in some regions.
Using Appian
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using | None |
- Interface creation
- Reusablility
- Debugging
Yes, but I don't use it