Visio Reviews

I'm the business process manager and we are customers of Visio. 

The process modeling is a valuable feature for us.

The solution could include better modeling and an interface with workflow capability, better integration would make the Visio to Power Automate connection a lot better. I'd like to see a feature that would enable the creation of a library of process models that could be linked to roles within the organization.

I've been using this solution for ten years. 

The solution is very stable. 

I think licensing costs are reasonable. 

If you're looking for a business process modeling tool, there are other options out there designed with that in mind. Visio is a good general diagram tool, but not specifically for business process management.

I rate Visio eight out of 10. 

I usually use Visio for really high-level conceptual modeling. Ironically, this works well with iServer. But, I use Visio for conceptual modeling since it makes it easy to draw things and is not as strict. This is because, at the conceptual level, one is not properly familiar with the details or constraints. This way, a business person would be able to critique something as being incorrect or not linked or drawn properly.

Visio makes it easier than with other tools to do such tasks as changing things or coming up with one's own visual style for presentation purposes. Mostly, the solution is employed for presentations made to business people, with the aim of facilitating their understanding of the design one wishes to use. Due to its greater flexibility when it comes to how things are joined together with lines, it is possible to put things together that would not work in a physical environment. This reduced constraint is good, as it allows one to initially familiarize himself with his system and ask the appropriate questions for which he may not have answers at the moment. At the minimum, this allows a person to put something up for critique in the event that it is incorrect.

The automated tools exist for making the computer do the dumb stuff. It may be worth going out to the market to see the sort of things people are trying to obtain. The solution integrates well with other tools and one can bring Visio diagrams into Word. Once in Word, a person can open the diagram for editing purposes if need be and then close it again and keep it in Word. So, all the integration capabilities with the other Office products is great. I can't think of much that I wish to add to the solution.

When creating a database, more stringency is required, as the computer is really dumb. A person is a lot more constrained, much more so when using the actual database creation tool, such as erwin Data Modeler. So the solution's flexibility can be perceived as both a strength and a weakness.

Visio is a general modeling tool, which encourages so many things beyond the use of mere data models. I think it's pretty good. Years back, when we first saw Visio being used with social security, the solution promoted itself as the missing piece. Word, Excel and Outlook were available. There was actually a piece missing where they stuck on the Windows logo.

In the late '90s or early 2000s it was possible to buy Visio with and without Office. They then removed this capability. Nowadays, one can obtain 365 but, with Visio, the component must be bought separately. The issue exists more with the purchasing and it would be nice to have it included as a standard feature. I believe they've now checked in Power BI as a standard component with Office, but Visio has so many more uses, since business people can use it to do swimlanes. Regular people and not just those with a technical background can use it for so much more. It should just be part of the enterprise or the professional version of Office. That's what I'd say. It's just so damn useful.

One of the things that was removed prior to it getting spun out was an enterprise version of Visio which could be set up, kicked off and actually go through one's network to ping everything that was attached to it, including printers, routers, PCs, laptops, et cetera. It would then bring all that information back and write a network diagram itself of all of those things. I thought that was a pretty cool part of the product. I'm not sure whether people now have network tools that do the same thing and that's why it's not used anymore. But, it was nice to see this sort of automation.

I have been using Visio since it came out in 1995 or 1996. 

The solution seems to be pretty stable, because I've opened models that I wrote 20 years ago and it still reads them without incurring frequent crashes. I did something flaky the other day which it didn't like. I don't know whether that was because it was going through a virtual machine and have yet to track down what the core issue was. However, overall, things have been pretty stable.

When it comes to scalability, I suppose that Visio is like any other product. One of the drawbacks of any Office product is its design for a single person. There exist ones on the web which allow for online editing in Excel, but many of the features I use do not exist in this version. This is a pain point.

We are talking about a one-person product, but the fact that you can print it off as a PDF and share it with others is a good feature of it. Visio differs from a real modeling tool, an expensive one such as, say... erwin Data Modeler, in that the latter has its own repository for storing models, which another person can access and use for modifying the relevant model. The model can be split into an overall one and a subject area. This way, two people can work in different subject areas. As long as two people are not working on the exact same object they will avoid stepping on each other's toes. Visio is akin to any other Office products, in that it involves a single person at a time per document.

I don't believe I have ever had to contact technical support to get the solution to work. We usually look up things on the internet. For most Microsoft products the help is not too bad. The last time I had to contact Microsoft support was years ago, concerning flowcharts, I believe.

For any issues involving the local installation I would contact our own infrastructure team. This said, I don't believe I have ever had to go out with an actual bug in the product.

I am not involved with the infrastructure side, but my understanding is that the initial setup was relatively straightforward. I had to put in a purchase order when I started this new role, but obtained access to the tool pretty quickly. I'm assuming that it is similar to other Microsoft products, in that there is a standard implementation, with the IT people having a fixed method of configuration, as with other Office products, which are rolled out.

When it comes to the setup, I have a couple of what are referred to as stencils, which are the things on the side that can be used for creating one's own series of diagrams or its components. I have a couple of these which I reuse. This is the only thing worth mentioning were one setting it up from scratch. But, many of the standard objects are pretty good and extensive. As such, the setup is not too difficult. Neither is it difficult to create one's own look and feel. So, it's pretty good.

I believe Visio to be priced pretty reasonably. Erwin Data Modeler may be a bit on the pricey side nowadays. When it was spun off from Computer Associates, they did so as a separate product and someone else bought it. I seem to recall at the time that the price either doubled or trebled, although I don't remember the reason for this. It was not clear to me what extra value was being offered for the price. Likely, the sole problem with erwin Data Modeler is that the price point is a tad on the high side. It can make selling to clients challenging and they are generally put off by the price.

Probably, it would have been better if erwin Data Modeler was the introduction to the environment whose creation is being attempted, meaning the DI suite and all the other parts involved in the governance, their glossary and all the bits and pieces. As the first taste is always free, it might've been better to have erwin Data Modeler at a lower price point. Once a person has obtained this product he would likely feel compelled to buy the other tools that work with it, rather than attempting to obtain something which does not. This would allow one to lower his price for the initial tool and then charge a bit more for those that nobody else has in their possession, such as one's involving data governance. This said, I'm not really involved in sales or marketing, so what I say should be taken with a grain of salt.

Visio is really good for high-level presentations but, when it comes to much more lower-level tasks, the best I've found so far is erwin Data Modeler and the DI, the governance suite that they've put out more recently. I've also worked with Oracle Data Modeler. One can't argue with the price on that one since it is free and presents no issues if money is lacking for other expenditures. If a person can do the drawings and present something to people then he can actually generate databases out of it, which is what one's end game is supposed to be anyway. It's not as pretty and it's a little bit more fiddly to do when things start to get complicated.

When I first started, everything was on-premises, although I do not recall if it switched to Azure at a later point. I believe I used it in 365. I am pretty sure the later ones are part of Office 365 or appear as add-ons, as they are not included.

My advice is that a person first work out what he wishes to use the tool for, to see if it suits his needs. While it's great for presenting information to people, it is not as good in the end when it comes to actually trying to build a product out of it. Of primary importance is that the person come up with his own look and feel for the organization, with a focus on business oriented issues rather than those of a technical nature. This would entail coming up with one's own color scheme or design and then remaining consistent in this domain. It is helpful to present to business people in a format with which they are familiar.

As the product will pretty much do what one wishes, which is nice, the focus should remain more on the presenting side rather than on its use. Certain products pose a challenge when it comes to getting them to comply with one's wishes, but Visio is a bit easier in this regard.

As a presentation tool and a high-level design tool, I rate Visio at least a nine out of ten.

We use Visio for mapping all the processes. It is a BPMN solution for us.

We are most probably using its latest version. 

It is a standard and easy-to-use solution from Microsoft, and you benefit from the general functions of Microsoft solutions. It integrates easily with SharePoint, which is a useful tool from Microsoft.

It is not flexible in terms of functions and modeling deliverables. When you speak of processes, the program has to describe the activities and the deliverables. You have to tell your robots how to deal with and input something, and you should have something more flexible from this point of view.

I got Visio just a few months ago.

I don't know. At this moment, it is just used to map and see where we are. We are just trying to use this. At this moment, we like it, but we'll see with time.

I didn't have to call Microsoft so far, but I might do so in the future.

I have used MEGA, and I feel Visio is better than MEGA because it is a BPMN tool, and it is standardized.

I have also used the free version of Camunda. It is a service, and it is easy and very fast, but it is not so well known. 

It is easy.

It is a free solution for us. It is integrated with our pack. We are trying to use the solutions that we already have. 

I am not sure if I would recommend this solution. It is not perfect, of course, but it is also not so bad. It is just a modeling system. If you want to go further and simulate the processes, you will have to use other tools. 

I would rate Visio a seven out of 10.

I work for BAM, which is the largest builder in the Netherlands. We have approximately 24,000 employees and we have a centralized IT that provides all products for our company. I use the solution for organizing many different types of visuals graphics. It has the ability to make drawings quickly with links, flowcharts, and organizational drawings.

I think the best part of Visio is that you can import drawings very well into Microsoft Word. For example, if you put the Visio drawing into Word, you can double click on it and it opens in Visio. It is a very useful feature and something which I miss switching to Enterprise Architect. In Enterprise Architect, if I import a drawing into Word it does not open the diagram in Enterprise Architect. This is one of the strongest features and the ability to create your own stencils. Additionally, it allowed the importation of AutoCAD drawings which was helpful because I did not have AutoCAD installed on my laptop.

They could improve the drawing function, other solutions provide easier drawing capabilities.

The UML drawings are quite limited, particularly the clause diagrams. You need to put a lot of effort to get everything right, compared to some other products I have tried.

In a future release, there should be more features in UML drawings. Generating drawings that belong to UML is quite an effort, everything is very tedious by hand and I prefer the methods which other competitors use which takes the effort away because some elements are done automatically. It requires fewer clicks with your mouse and fewer presses on the keyboard to accomplish the same result.

I have been using the solution for approximately 21 years.

The solution is stable.

I have also used other UML tools and almost all of them are easier to draw in than in Visio.

The implementation is done by our centralized IT team.

I evaluated Enterprise Architect and have now switched to it.

Visio is that it is a reasonable product.

I see Visio as something similar to Coral Draw, but more vector-oriented. For example, no picture, but vectors. I classified Visio more as a standard drawing program, it tries to be something else. I am drawing more and more diagrams in UML and Visio is not the ideal tool.

If I was going to rate Visio for generalistic drawings, it would be a solid eight. It is a good product, there is nothing wrong with it. However, this is not my main use case.

I rate Visio a five out of ten.

Our primary use case of this product is to create diagrams for the solutions I'm designing. Others may use it to provide graphical explanations of complex topics, or even for organizational charts. We have around 20 users in very different roles - IT, processing, design, or those in more technical roles. We are a customer of Visio and I'm a solution architect. 

Visio helps to depict what's on my mind, it flows between the different components that we're designing. Visio is very good at illustrating advanced topics which helps my team understand what I'm trying to get across

The valuable feature is the simplicity of drawing shapes and connecting them. It's very easy to customize and then group the activities so the solution offers a lot of flexibility. It really provides value. 

I'd like them to include more stencils for new technologies in the solution. There are plenty of stencils available on the web but it requires researching, downloading, and testing what works. There are some common ones such as when you're working with technologies like Microsoft but it takes me some time to download clip art and try to make them myself.

I would love to see an option to drill down collapsed sections of the diagrams as well as an option to navigate through different pages of diagrams, something that can be more easily summarized, and then go on to the details.

I've been using this solution for 10 years. 

This is a stable solution and there's very little maintenance required. We have a software specialist in the company and that person takes care of all the laptops.

The initial setup is straightforward, it takes around half an hour. 

This is a very powerful and useful tool. You can create all types of diagrams and I consider it a must-know option.

I rate this solution a nine out of 10. 

We primarily use the solution for tasks such as work charts, network diagrams, and process flows.

Process flows are probably the task we do the most. It's just how she diagrams, how a piece of software or a process should work. It's improved our organization.

It's pretty basic and fun to use.

You can go to YouTube and watch training videos. There's lots of information online about the product.

The solution can scale.

The product is quite stable.

It's my understanding that the initial setup is straightforward.

It's not the easiest software to use. It's not user-friendly out-of-the-box.

I've been using the solution for about 20 or so years. It's been two decades; it's a long time.

The stability is excellent. It never breaks, and I've used it for 20 years. Its performance is reliable. It doesn't crash or freeze. There are no bugs or glitches. 

The solution can scale. If a company needs to expand it, it can do so with relative ease.

We have around 200 people who use it in the company.

As of right now, we do not have plans to increase usage.

Technical support is fine, as long as you can get a hold of someone. that can be tricky.

Prior to this solution, it's unlikely we had a different product. It was 20 years ago, and therefore it's been a long time.

I didn't directly deal with the initial implementation. We have a team in-house that handles deployments. I can't speak to what the process was like or how easy or hard it was. Likely, setting it up was pretty straightforward and deployment takes a day. At least, that is my understanding.

We have a dedicated team that handles deployment and maintenance.

We have our own in-house team that can manage the implementation. We did not need the assistance of an integrator or consultant.

After 20 years of using the solution, our company has definitely seen an ROI. I don't have exact details, however.

We have an enterprise license. We renew it on a yearly basis. We don't pay any extra fees and we partner with the Gartner group to help us when we have to renegotiate.

I'm using the latest version of the solution. I can't speak to the exact version number.

We use both cloud and on-premises deployment models at this time.

I'd advise any company considering using the solution should first have a Microsoft team in place.

I'd rate the solution at a five out of ten.

We use Visio extensively for creating architecture, network and workflow diagrams. Also used for UML Class diagrams and various types of flow charts 

We use it to create diagrams used for architectural review. It's a great tool to create diagrams to show how an infrastructure or software architecture has being designed and then review that with the other domain architects.

I like the way you can Hyperlink objects to a URL, local file or other tabs within the same diagram. I use this to create an Overview tab with a high level digram and then link objects in the Overview to other tabs with more detail on that object. You can also save the diagram as a html page and then host on a local server to create an interactive diagram. You can also automate the creation of diagrams with PowerShell

Would be nice if visio viewer didn't require active-x.

I have been using Visio for over 15 years.

It's a stable solution. It's Visio. It just works.

Scalability is fine. It runs on each individual client. I haven't used any of the team integration hooks. We have a lot of technologists that use it and we're trying to make a move to move those architecture diagrams to be more driven by code by leveraging C4 and then model driven design through MagicDraw and that's a new journey for us. I think there are still going to be a large number of teams that still end up using Visio as it's very versatile. 

It's all automated for our firm by our department. I run it on my Mac as well, and it's super simple to set up.

We do everything ourselves. We set up and deployed this solution.

It's better than using PowerPoint or something else to draw the diagrams. 

It's not the cheapest product, but it's extremely valuable.

I would tell potential users that it depends on how you use it. You can use Visio for everything from designing networks to organizational charts. You can also use it for so much more as it's a very versatile tool. There are a lot of Visio stencils that are available on the web. Use those.

Just do your homework. But there's just a lot of people who have contributed to creating various open-source Visio stencils. Most product vendors have already created those stencils. You don't need to go and recreate it on your own. You can go to NetApp or VMware, or Cisco and download the stencil for their products. Then it makes it very easy to use and integrate.

On a scale from one to ten, I would give Visio a nine.

Company-wide, it is used a lot for flow charts. From an IT perspective, we use it quite a bit for network diagrams and documentation. The Human Resources team uses it for organizational charts.

In terms of deployment, we have a kind of mixed deployment. I tend to use an on-prem version that is loaded directly on my machine. We are all Office 365, so a bulk of our users use it as a cloud-based downloadable solution, which is a part of their Office 365 implementation.

It helps us to secure business and C-suite leadership approval on projects. For lack of a better term, it dumbs down technical solutions so that everybody can understand them. It provides a nice middle ground. We have a lot of really talented engineers on staff, but they tend to get lost in the technical minutia, and the business gets bored with that. 

A lot of built-in templates are really phenomenal. The templates assist in translating very complex design elements into understandable diagrams that non-technical folks can grasp.

Some of the improvements that have been made in Visio have not been beneficial, at least to me, personally. Too many things have been added to it, and it makes it kind of clunky sometimes. There is an overwhelming desire or competition to continue to improve it when the product is and has been pretty good, and some of what is done tends to clutter it. In some cases, the updates make it more difficult to use. It is already pretty feature-heavy and continuing to add stuff is not productive from my perspective. 

I have been using this solution for 10 to 15 years.

It is very stable.

I don't have any input on that. In terms of the number of users, we probably have a couple of hundreds of users of Visio. They are from the IT and the infrastructure side. We have Applications users and Human Resources users. We have a manufacturing organization, so we have program managers who manage various customer products, and they use it as well.

It is used fairly extensively throughout the organization. Our usage is okay for now, but we're always one acquisition away from that going out the window.

I've never used technical support for Visio.

It has always been Visio. Prior to using Visio, it probably was Paint or whatever program was available at the time.

It is straightforward. It takes very little time to deploy.

It is done in-house. In terms of maintenance, because we're loading it from the cloud, if there's an update, that's taken care of with the regular Office updates. So, pretty much everything is on the front end, that is, getting it from a business standpoint, getting the approval for the license and the cost associated with the license, and getting it installed. Once it is in, it is usually off to the races.

We have definitely seen a return on investment.

We're in a Visio plan that is like $15 a month per user. At the moment, it is just the standard licensing fees that I'm aware of.

Be aware that it is easy to get lost in all the different things to do with it.

I would rate Visio a nine out of ten.