What is our primary use case?
Our main use for Signavio Process Manager is to document our process and look at how we can improve them. We also use it as a basis for communication, internally and externally, to show workflows and ask for feedback. You can really see what has to be done on both the development and user's side.
How has it helped my organization?
Signavio is very easy to use. I've seen some other products and the modeling in this solution is super fast. I like the QuickModel feature, where I can sit down with someone who isn't into process modeling at all. You can just type out the steps that there are, and then later clean it up into a proper process model.
Using this solution has helped when we work together on a project with a lot of different people. In our compliance environment, you have several people in different roles. There is me, who is the technical person on the team. There are lawyers that bring in the expertise and the content. Then, you have developers that actually build the platform for us. Having a diagram instead of a ten-page document that describes what we want to do gives us a language that everybody understands. We can all sit there, look at the process, and everybody understands what is going on. On the basis of that, it is very easy to talk about what we need to do. It actually surprised me to see how good it is for communication and for simplifying complex topics.
The adoption is good in our own team, although overall, it is not going as we'd like. There are other teams in our company that started using it, but usually, there are only one or two real modelers in each team. This is especially true because of the license, as not everyone is going to get a license for modeling. This means that you always have experts, so to say. Normally, the other users look at the Collaboration Hub and then use comments.
We have not yet begun the integration of process modeling, mining, and automation. In fact, we haven't really begun to optimize yet. We are still in the first process of documenting our current processes and unifying them.
We are trying to work on the process-improvement lifecycle at the moment, but we aren't there yet. I've seen that the Velocity update is going to provide us with something that's going to make this easier and nicer for us to do, especially from a visual perspective. Some users need a nice visual picture and there are some things that come with the update that I think will be very beneficial for us.
With respect to giving all of the users what they need, it is hard for me to say. We mainly have power users, experts, and then we have a few users who only leave comments. We haven't rolled out the Collaboration Hub on the whole company yet.
While we have not rolled out the Collaboration Hub company-wide, I can say that in my team, it has helped create a process-centric mindset. When we do a project, we try to document everything that we want to do in Signavio, including the lifecycle. It really helps to keep us focused on what we want to get and what we have to keep in mind for the whole process.
What is most valuable?
The most valuable feature is modeling. It is very quick and easy.
The formatting features are quite good because you can create very complex models, but you can easily clean them up so that they look very nice.
The customization is very valuable because we use a lot of attributes, which helps us with how we look at our processes and also the steps in our documentation.
The QuickModel feature allows you to start right away, put down a model, and then clean it up later. It's very quick and easy and we like that.
What needs improvement?
As a standard user, I would really like to have more flexibility in the visualization, especially on the main page of the Collaboration Hub to make it easier. I would like it to show cycles and other things, rather than just boxes and arrows.
I would like to be able to include images in the documentation.
What do I think about the stability of the solution?
I generally have not had problems with stability issues. It's running really fast and smooth especially for how complex some of the diagram sketches are. The only problem is that it's online-only, and there's nothing like an offline feature, which means that it is only as stable as your internet connection.
What do I think about the scalability of the solution?
We have set Signavio up in different departments and it is easy to just add more users. There is the option to set up a separate platform inside the company if it is necessary. It has always been easy to do, but we have not yet reached our full potential.
How are customer service and technical support?
Signavio's technical support is very good. They are very nice, helpful, and fast in replying. It is not the case, as with some solutions, where you feel like you are talking to a wall and only get standard replies. Our experience is that we've had a responsible person that has called us back and showed us things the right way. It is very nice and I really like the support.
Which other solutions did I evaluate?
The other solutions that I have seen are BOC ADONIS, Camunda BPM, and some free stuff as well. That had a few nice features, but I really like the way that Signavio functions.
What other advice do I have?
Some of the quality-of-life improvements that I had wished for seem to be included in the new version. My understanding is that things have been made easier for an end-user to just click through it and find the way, like a Wiki.
My advice to anybody who is researching this type of solution is to connect with Signavio and ask them for a webinar or presentation. They are very good at showing things that you might not notice in the normal advertisements, or if you just look at it by yourself. They know the basic application and what you need it for, and they can show you the features that might be of interest to you.
I am very happy with the product. I have seen some other tools, and Signavio is the whole package. It is easy to use, quick to use, I like the features, I like the support, and I like the people who are working behind it.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Which version of this solution are you currently using?