Visio Reviews

We primarily use Visio for creating business process diagrams and flowcharts.

Drawing flowcharts is the most valuable feature of Visio.

Visio can be more user-friendly.

I would like to have a drag-and-drop option within Visio.

I have been using Visio for many years across various versions.

Visio is stable.

I believe Visio is scalable.

We have an enterprise agreement with Microsoft that includes premier support service.

Our IT department completed the initial setup and deployment, which was straightforward.

The implementation was completed in-house.

Visio is included with our Microsoft enterprise license.

I give Visio a nine out of ten.

We have over 300 users.

I recommend Visio.

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. 

As process improvement professional I map out current state processes either at the value stream or swim lane level, at times both. With current state I identify pain points and bottlenecks do root cause analysis, identify possible solutions, and make recommendations on which ones I think would be the most effective. Then incorporate them into a proposed future state. 

Once we developed custom templates and shape libraries it provided a common look and feel that our stakeholders have come to understand, which is helping them to develop a continuous improvement mindset. 

We are all familiar with it, and it is easy to use. There is a lot of flexibility, and you can create custom templates with standard shapes. 

It would be nice if we could develop a custom database. We have looked into this functionality, but all of the other solutions that have a database are very locked down, and you have to use them their way. You can't define your own systems, tools, and inputs etc. For example, if we have systems that are used in multiple processes, and we want to know what processes use those systems we should be able to query the database for processes that include a specific system. A uses case could be system X being phased out so we need to know what processes will be impacted, so that we can ensure that those processes are all taken into account in any decisions to replace that system.

Additionally, Visio should have the ability to capture metrics such as demand, work time, cycle time, .. for each step in the process. Then those metrics should be able to be linked to a spreadsheet to enable data analysis that remains aligned with the process map so that changes remain aligned between Visio and Excel. Other systems attempt to provide this functionality, but the spreadsheet functionality is not as robust as Excel. 

I have been using Visio for six years.

It is stable.

There are no scalability issues. We are a nationwide company, and there are around 5,000 users.

I never had to contact them.

I never used another solution long-term, but I have evaluated various and continue to see Visio as the best option. 

The initial setup was easy. It has been around for so long. All of us have used it before, so it is not like it was new to us. 

Good. 

Most other tools are expensive.  

I was already using Visio for years before evaluating other options.

I advise standardizing the file naming conventions so it is easier to find what you need when you need it. 

We use the application for process mapping through architecture. It helps visualize the activities and interactions between 3,000 different systems on the network.

The product efficiently visualizes various business processes, including building and networking architecture. It is quite intuitive, and there is a lot of training documentation available. We can import an Excel Spreadsheet with all the essential data, and Visio can build the diagram using it.

In terms of features, it could provide more automation to display data flowing through architecture. It should give a real-time data update.

We have been using Visio for 20 years.

It is a stable application.

We have 30 Visio users in our organization, but soon, we will roll out the product for about 200 users. It is scalable.

I take help from our internal IT staff in case of technical issues. If they need further assistance, they approach Visio’s technical support team.

I have used Draw.io before. It is free software and designs diagrams quickly. However, it has very limited functionality and is not suitable for enterprises. I would recommend Visio for working on business processes on a day-to-day basis.

The product is easy to deploy and maintain. It takes a few minutes to complete the process and requires one admin executive to work on it. It received automated updates.

The product is inexpensive if you already have Microsoft products in your environment. The license encompasses all the required services.

I recommend Visio to others and rate it a ten 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 use Visio when I'm writing a client report in Microsoft Word, and I want to put in a simple graphic to supplement the text or better explain something. Visio's graphics are not complicated. They're quick and easy to create, so I use them mainly for what I would call static graphics, like simple charts and diagrams.

Visio has improved my workflow by making it easy to create charts, diagrams, and essential illustrations to use in my client reports and proposals. It has saved me a lot of time I would otherwise spend creating visuals for clients manually.

One of the most valuable features is the online support from Microsoft. Whenever I'm stuck with a problem, I can contact customer support. They will almost certainly get back to me within a reasonable time frame. They're good with that.

It is easy to use online tutorials and training videos provided by Microsoft and elsewhere, such as on YouTube. So, if I want to create a new diagram, add some shapes, or increase the weight of a connection from one object to another in my graph, I can easily find out how to do that.

Another aspect that I enjoy is the seamless online integration. For example, there's the ability to download all sorts of extras like different shapes, stencils, objects, etc., for free directly from Microsoft into Visio. Also, I like that you can drag and drop online pictures straight from the Web into Visio.

There could be better integration between Visio and Word, especially when it comes to importing graphics from one to the other. Visio's graphics don't seem to play well with other applications. Sometimes I move a business process graphic to a Word document. It doesn't copy the picture correctly, or it leaves some of the connectors off. Or it puts the wrong one in or changes the font for no apparent reason. That's a pain in the neck, and it's one of my biggest complaints about Visio.

Moreover, when I connect a caption to a drawing and move the drawing, sometimes the caption gets left behind. And if you shrink the size of a drawing, I'd like Visio to scale the font automatically. Small details like this would significantly improve the product.

Aesthetically speaking, the graphics can be a bit crude and simplistic. The graphics are sufficient for most purposes, though dated in their appearance. Visio is a static program that tries to keep things simple for most users. However, I would appreciate it if Microsoft made an allowance for at least slightly more complicated graphics. As they are now, they do not inspire or motivate interest in the subject. People don't look at the graphics and say, "Wow, that's a great graphic." They look at it and say, "Uh-huh, move on. Next!" It's a lot of the sameness.

I would also love to see Visio with a more intuitive and reliable data linking feature. I shouldn't have to program or develop any complicated code. Just press a button, connect to the spreadsheet, and update it. For me, sometimes it works, sometimes it doesn't. You should trust your application so that when you need it to link, it links. It would help to know that Visio is using the latest data, mainly because you don't want to embarrass yourself in front of a customer with wrong or outdated data especially when you have a time crunch and have little time to verify if an application worked as you wish it would.

I like dynamic programs. I want to take inputs from other places and have the application automatically update my chart and know that it's correct. And not only do I want it updated, but I wish to document updates, so I can see what updates were selected and used. So, if the document references a spreadsheet or an Access database, it shows where the data came from, what version it is, and the date. If you're doing a nice bar chart in Visio and you want all the bells and whistles, you can see the source material and revision of the chart so that you don't have to go back and say, "Is this right?"

I want to create my objects and my object library more easily. I think you can do some of that, but it's not that simple. I haven't had a lot of experience creating objects, but when I did tried, it was awkward.

The support is okay, though not super great; I wouldn't expect it to be. Visio is not a program where you need a lot of hand-holding for most tasks. It's quite suitable for those who want to drag and drop, so support isn't too crucial, though there is room for improvement.

I have been using Visio since it first came out in the early 1990s.  It hasn't improved much in that time.

It's very stable. I have never had a crash in Visio ever.

For my use case, there's not much need to scale it up in any meaningful sense. When I'm writing a proposal or preparing a report for a client, I try only to put in a sufficient number or well-considered graphics to get my point across.

I typically create my graphics and place them in a Word document. And then I hope they stay together as I move things around during the editing and review processes. Sometimes they do, sometimes they don't. So, in terms of scalability and accuracy, Microsoft could improve integration and consistency between their Office applications.

I haven't had to use technical support very often at all over the years. I might have used it only once or twice in the past twenty-something years. I'd rate the support I received as a five out of ten. Not too good, not too bad. Thankfully, they've gotten rid of a lot of the need for that kind of tech support by putting better help and documentation online.

Microsoft offers training videos online that teach the basics of Visio well enough. I can also go on YouTube if there's something unique or unusual that I need to do. Frequently, somebody's already done it, and I can quickly learn how they did it.

Suppose you do want technical support. In that case, Microsoft has a reasonably active Visio user group. However, it's not real-time help, and you may have to wait a little while for a response. If you want somebody to help you live, you're going to have to pay a third-party company for that kind of support. I don't use Visio so much that it's worth going that route.

Neutral

I used a similar solution to Visio many years ago, designed for business flowcharts and business processing. The company that built the software went out of business.

It's easy to get started with mocking-up simple flow charts and diagrams. Still, it can get very complicated when setting out anything a bit more detailed—especially when getting titles, labels, and font sizes to match up. Suppose you want to make a custom organizational chart or a product line chart with all the details and specifications. In that case, I suspect you'll need to set aside some time to learn the user interface more thoroughly.

In-house.  

I haven't actually calculated an ROI, but I would approximate that I save at least two hours' time of cumulative manual effort for each graphic built with Visio.

The licensing process is a breeze. Buy the license and download the application from Microsoft. Enter the license key in Visio to activate the software.

No.  I've used Visio for many years.  It does what we need it to do and is good enough for the simple graphics we use, but perhaps, we could improve our graphics if we had a more dynamic and creative graphics application.

I like to call Visio a program for the graphically impaired. I use it because I hate spending lots of time preparing graphics, especially when our clients don't spend a lot of time studying them. I would recommend skipping any fancier alternatives unless your business demands it. Most people might benefit from adding quality visuals to their documents but don't have design skills. In that case, I recommend using Visio instead.

As long as you don't have excessive expectations, it will do what you need it to do and do it for a reasonable cost.

I would rate Visio an eight out of ten.

I use Visio for designing diagrams and flowcharts. It is user-friendly and easy to use compared to other options. Although many people in my company use AutoCAD, I am not familiar with it. For all the designing, charts, and diagrams, I use Visio. If someone requests an AutoCAD format, I will design it in Visio and then forward it to our team who is responsible for converting it to a CAD file.

The main reason I choose Visio is that it is easy to use. The user interface is familiar and straightforward. Additionally, it offers a variety of templates, such as those for Cisco solutions, which make it easy to create diagrams for specific use cases. For example, we use a Cisco Meraki switch and we can find the exact template for it, then we can easily drop in the components and connect the cables to create the diagram.

Searching for specific templates within the program can be difficult. For example, if I need a template for an electrical diagram with certain symbols, it can be challenging to find it.

I have been using Visio for approximately three years.

I rate the stability of Visio a nine out of ten.

The scalability could be better for the cloud version.

I rate the scalability of Visio a six out of ten.

I did not use the support from Visio.

I have used some open-source solutions in the past but I prefer Visio.

The setup of Visio is simple.

The solution is expensive. The solution does come bundled in other packages.

I rate the price of Visio a three out of ten.

I rate Visio a seven out of ten.

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.