Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Microsoft Visio
Score 7.7 out of 10
N/A
Microsoft offers Visio, a diagramming tool for building flowcharts, diagrams (e.g. network diagrams), org charts and floor plans, available online as a subscription and also in enterprise level packages (e.g. Visio Professional).
$5
per month per user
Pricing
Nintex
Microsoft Visio
Editions & Modules
Enterprise - Process Platform
$480
Minimum 1,000 users per user
Visio Plan 1
$5.00
per month per user
Visio Plan 2
$15.00
per month per user
Visio Standard 2024
$309.99
one-time fee On-premises diagramming solution, licensed for one PC
Visio Professional 2024
$579.99
one-time fee On-premises diagramming solution, licensed for one PC
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. …
We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
Visio is by far and away the best tool that I have used to do Value Stream Mapping sessions with the warehouse I support. It has all of the shapes needed built in to be able to represent all areas of the processes. I also like how you are able to make the drawing as big as needed and when printing it out of Visio you have the ability to use the necessary paper size. The biggest complaint that I have with the software if how it can be cumbersome for non-Visio users (that is, people without a license in the orgnaization) to interact with the Visio Map. We normally have to dedicate one Visio SME to be able to make the changes that Process SME's find since they do not have access to the software.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
Microsoft Visio is excellent for organizing thought processes related to our more complex research.
The diagrams created with Microsoft Visio are ideal for graphically displaying the internal organization of work and research groups through flow diagrams.
Microsoft Visio is a great tool for managing our students' activities by creating flowcharts that help us graphically visualize the steps of their group work.
If you are creating a process with parallel subprocesses, there's no way to see, in a single view in Nintex, all the steps for the subprocesses. You have to view each sub-process in its own view, so it's hard to see what's going on at a high level.
There isn't an easy way to filter the processes by another user (not yourself) in Nintex. There is a report that shows processes and objects by user, but that's not as convenient. This is something that I've seen in other tools (OpenPages by IBM) so I am surprised that it is missing.
Nintex doesn't really have a way to capture iterative processes (which we have a lot of). It's designed for linear processes.
When navigating through swim lanes, the user must be careful between switching from the point to the connection features as it can be difficult to remember which mode you’re in.
When drawing “decision points,” it can be difficult to type words like “yes” or “no” between the connection lines.
The exporting options aren’t ideal. They are hard to create in PDF format.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
We use Microsoft Visio to keep our diagrams updated and to that end we will need the subscription to keep using the software. Otherwise we will be left with PDF versions of the diagrams.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
I have always struggled with some basics, such as connection points, object alignment, font consistency, arranging layers and their order (bring forward, send backward), and managing overlap. I usually need to create an initial rough draft and then do a separate cleanup pass to bring the diagram up to my quality standards. If I skip that step, the result generally does not look very good. And once a diagram becomes busy or the file gets large, Visio has been unstable for me in the past, including occasional crashes that caused non-recoverable edits.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
Overall, I feel that Microsoft's support is weak. They are now such a behemoth that their model of putting documentation online for their users to sift through is totally outgrown. Given the amount of money you pay for these licenses, Microsoft should provide easy one-on-one support for their products via email or chat. The idea of paying their rates for support incidents is ridiculous. If you have an enormous amount of time on your hands, use their support websites and you will eventually find a solution most of the time.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
Even though it’s a more expensive solution, Vizio is built for the enterprise. Therefore, it integrates perfectly with our existing Microsoft stack, and quite frankly, because it’s such a more mature product, it provides exactly the functionality we need and expect.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
Reduces the amount of time I need to create process flow diagrams. In the past I would use Powerpoint or Word which required a lot more effort and time and never looked as good. Visio just takes that headache away.
Only negative is that I personally believe it should always have been part and parcel of the Office suite, thus giving more users the opportunity to use it rather than specifically having to justify its separate purchase within our organisation. Different now with Office 365 of course!
