ProcessMaker - Best for the Basics and New Users
Overall Satisfaction with ProcessMaker
I reviewed ProcessMaker as part of an initiative to find the best fit for a local school. They had an issue with efficiency and spending time on the right tasks. They were spending too much time in trivial things which could be automated, and doing these things on paper, so they were easily spending at least a full day's worth of time doing these things. My role was to come in and find a solution which addresses both their efficiency issues and making sure the process is more refined. They wanted to spend more time working on the relationship with customers and not simply filling out paperwork day after day.
Pros
- User interface. It is clean and easy to understand. You won't get overwhelmed the second you log in.
- The workflow maker. With a drag and drop interface, you can easily visualize and implement what you want on the screen. Out of all the programs we tested, this one had the easiest process maker and designer.
- Ease of understanding. My biggest recommendation would be that this program is easy to access for anyone. There are complications (see negatives) but this program can be implemented quickly and efficiently, and nearly anyone can learn to use it. You will not feel like you are in the dark with it.
Cons
- Complications when you get to the more advanced pieces. When trialing, I found that the more advanced a process got, the more complicated it got for me in coding. When you begin using the more advanced features, you will find that you need to have a basic knowledge of coding - otherwise you won't go any further. This was my sole issue. Unfortunately, it was one that would have brought the school to a grinding halt if they were to ever get more complicated than they were.
- This would have been the easiest program to implement. It would have been the quickest, and the one that most of the employees would have been able to master. That alone would have saved countless dollars in time investment.
- Unfortunately, the environment doesn't support knowledge of coding. So, they would never be able to advance further than a certain degree before having to bring someone else in again. It would have saved money at first, but then would have ended up costing in the long run.
In the short run, ProcessMaker blows KiSSFLOW away. It is easy to understand and use. But in the long run, once you get into more complicated actions, they equal out. The price was right, and while we eventually went for another option, ProcessMaker would have been the next choice had it not implied a future where they would stand still in the face of more advanced options.
Comments
Please log in to join the conversation