Visio Reviews

Visio is mainly used for documentation purposes. For example, drawing flow charts or network diagrams. It can also be used for defining schemas or application development.

In my organization, people from multiple departments use it, especially the IT team. They prepare documentation on the network architecture. Additionally, the data team uses it to create flow charts, sequence diagrams, and schemas.

The solution is easy to understand with some hands-on experience.

Microsoft should include Visio as part of their Office 365 offering.

I have used Visio for approximately 10 years.

The solution is stable.

The solution is scalable and flexible.

We have approximately 15 people using the solution.

Microsoft technical support is convenient. They have an online community for Visio and if we have created a ticket with the support they always respond promptly. We have not had any problems with the support.

The installation is easy, it only takes approximately five minutes. You only need to go to the vendor website and download an executable file and then it is straightforward.

We did the implementation ourselves. The solution does not require a technical team for implementation.

You can purchase a corporate license for more users to use the solution. We have purchased a stand-alone license and which could be cheaper.

I rate Visio a nine out of ten.

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 are end users of this solution. I'm a senior director of the company and a digital engineer.

The solution has helped us get our life cycle diagrams right and show the accountability across groups. It affects the business process sometimes at a very high level. Although it's not a BPA tool, a management tool, it has been utilized in some of those aspects and has been helpful to draw the handoff and the handshake across teams and across roles as we draw the life cycle diagram. With the various tools that come out of the box, it's been pretty helpful to get that in a pictorial fashion as it makes it easier to explain.

I like that it's simple to use and a very intuitive solution. The tools that it provides out of the box are pretty good. The out of the box categorization of flow charts helps. Its ability to take it to PowerPoint is easy as well. 

I'd like to see the portability simplified from Visio to PowerPoint and vice versa. With other products coming on the market, Visio is losing a little ground and as a result, I mainly use PowerPoint now and Visio much less. The user interface could be simplified enabling non-technical people to use it. There's something about it that makes it complicated to use. 

I've been using this solution for a few years. 

It's a pretty stable solution, I haven't had any issues around it.

I haven't seen any issues from a scalability perspective. 

I have previously used Confluence, PowerPoint and Precio, which have similar features in terms of what they're trying to do. They may not be out of the box, but you end up drawing it yourself. Visio is really a complementary solution as it merges when you're drawing deeper  solutions, more technical and when you're wanting clip art and pictures. It's being more in that space rather than really drawing technical stuff.

It's important to understand your objectives, understand who the audience is and your needs. You can then make a call as to which solution suits. It's not an easy solution for non-technical folks and is generally used by technical staff in technical IT departments within corporate companies. I started as a technical person so haven't had issues with it. I really like that it's easy to draw stuff out. You don't need PowerPoint for a standalone diagram that you have only from a collaboration perspective, like the confluence etc. If you're doing a standalone diagram, trying to communicate the message in a visual format, Visio is great. 

I rate this solution a seven out of 10. 

I wrote some Visual Basic for Applications (VBA) scripts in the background to graph with my stencils and use the database at the back. In general, I'm using stencils, and I'm using Excel database in the background. With those tables, I am able to grab the data out in the stencils, and then I place it Visio. So, the main drawing area is in Visio, but it uses data in the background.

I am not using its latest version. I am using one version back.

I use it for computer architecture. I make diagrams of various engineering domains such as mechanical systems engineering and electrical systems engineering. It is used for that purpose, and we're able to better organize our architectures to pictures.

The fact that you could program in VBA is most valuable. 

It is easy to use out of the box. It requires little training, which is readily available. You can learn things easily.

We need the place and route capability for the lines when we have a database. I use it for architectures, and between the boxes, there are lines or interfaces from one tool to another. I wish those lines could be easily drawn without having to place them mechanically. I wish that there was some kind of place and route capability, so I just press a button, and all the lines get drawn. 

I have been using Visio for at least 10 years.

It is definitely good. It works.

It scales, but there is a limit. There is only so much that you can do with the nature of it.

We don't have any intentions to increase its usage, but it is used as a standard tool.

I did use Microsoft technical support before but not necessarily for Visio. In general, they're pretty prompt.

In general, I have been using Visio.

It was straightforward to deploy. It probably took hours in reading instructions and so forth.

It was an in-house job.

We have an enterprise license. I'm not sure what the cost is. 

I would rate Visio a nine out of 10. 

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.

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.

I build either diagrams for solutions or use Visio to create illustrations for slide decks and white papers.

There's a much better library of stencils than there used to be. But I still have to create many composite objects to illustrate a software-defined data center or software-defined networking. I like that once you create what you need, you can group that, at least within that drawing, and you have access to that new stencil object or that custom object throughout that drawing.

I do know that Microsoft has extended the ability of Visio to interact with other Microsoft applications. I know you can use Visio elements in spreadsheets and Excel. I know that doing a copy and paste from Visio into a PowerPoint slide is very easy and clean now. It used to be a nightmare.

The auto-routing feature could be better. Around 2018, the auto-routing of lines was pretty close to perfect, but it's started to go downhill from there. Keeping the lines attached to endpoints while you manipulate how they run and how they interact with other shapes or near other shapes is becoming very tedious. I would like them to give us the option of opening up the rules for auto-routing and make checkbox selections of what rules we want to apply and what rules we don't.

I've been using Visio for about 20 years.

Visio is stable. It's gotten to be much more robust since Microsoft took over. It used to freeze or crash with very complex drawings, and I haven't had a freeze or a crash in years.

I think it's scalable. I don't think I challenge what it can do the way I used to. I think Microsoft has probably improved how it uses memory, or they may have solved some memory leak problems because I did not have any issue with the size of a drawing. 

I've never reached a limit on the size of a drawing, and usually, autosave is turned on by default. Again, right about the time Microsoft acquired Visio, the autosave function took much longer than it does now. I can also open more additional applications while Visio is running, but it used to hit its limits on that. They have improved its ability to run in the same environment with other big apps.

The initial setup is getting much easier. The deployment piece was actually just part of my license. The IT team can set up definitions of which engineers get what features in Microsoft. That was completely transparent to me this time.

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

I am a health and safety professional. I use it for flowcharting, but I also use it for drawing diagrams. 

I will do a technical assessment of a workplace scenario of equipment as well as noise measurements, and I will use Visio to draw out the scale.

There are many images that you can put in there and data to create images of workplace exposures.

It has improved the way our organization functions.

It's a tool that helped me diagram complex procedures. More as a picture versus words. 

It also for training and letting other people know how to do that same procedure.

It works really well for flowcharting, it can label.

Also, being able to pull the finished drawing out and put it in a Word document is easy, and very useful.

It allowed me to do some things and save them really well. And I found many different things to do with it. It's beyond flowcharting.

The latest version has taken some transitioning and it's a bit of a workaround, but it's also been good. I found the ctrl 1,2,3 buttons that I didn't know about and have been very useful. If you hit ctrl 3 it lets you do your line draw.

I just uploaded the latest version and using it now, and I'm struggling with it. It's very different than the other version I have used, and I haven't done any tutorials. 

The previous version was easier. It was easy to intuitively figure out what it did. I learned it on my own and it didn't require the review of tutorials. But with this updated version, I am definitely struggling with it. I need to go through the training and go through the tutorials. So far it seems more complex, but maybe it's just different.

It may handle images well, but I don't know yet. It is something that I would like to see in this solution.

It should be easier to transition into a new version without having to spend so much time in just one area. Providing information on what has changed and how to do it would be very helpful.

I would like the option of going back to the way of doing things in the previous version. I don't understand the block system. I had the favorites that I have to build again because somehow they got lost with the upgrade.

In my favorites, I had shapes, fans, and other things. You pull up all of your basic images or search for them, and you could drag them over into your diagram.

I have been using Visio for approximately eight years.

We are using the latest version.

I have not had any issues with stability. It's a stable solution.

It is easy to scale this solution.

I have never contacted technical support.

Previously, I did not use another solution. It was a discovery. 

I came across Visio, I saw what I could do with it, and I just continued to expand my uses.

The initial setup is straightforward. With this new version, it is a bit confusing. 

With the previous version, I was able to have all of my favorites, I was able to pull objects and do an arrow as a connector, and I had to stop and learn how to do that.

I like the way it was earlier, but it could be just my learning curve.

If you have a need for flowcharting, organizing, or creating diagrams, I think you should check it out. It's worthwhile.

Based on my previous experience with the previous versions, I would rate Visio a nine out of ten.