Visio Reviews

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.

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 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.

It's been an extremely reliable solution for me for a very long time. It's quite mature.

If you are a knowledgeable individual, the initial setup isn't too difficult.

There are plenty of very good third-party tools.

The stability is fairly good.

The solution can scale to meet the needs of any project.

The issue I have with this solution is the same issue I have with all the products by Microsoft. They depend on many solutions by third parties for too many things, from my point of view. Maybe there should be more basic, fundamental resources incorporated into their products in general - not just this product.

A basic user may have issues trying to install the solution.

There are a lot of patches that sometimes change how one version will interact compared to another.

It would be great if, in the future, we would be able to use numerics and graphics cards. If there already this functionality, they need to make it more publicly known, as I don't see it right now.

I've been working with Microsoft products for 30 years or so. With this product, I've used it from time to time, when I've needed it. I'm not sure the exact amount of time I've spent with it over the years. It's likely much more than ten years.

The solution, for the most part, is very, very stable. There is one problem in that there are so many upgrades and patches and so on that are critical and must be applied that it makes for a few issues in terms of practical use. I was facing such a very specific problem. The project was functional in an older version, yet the same code was not functional in the newer version. Therefore, to troubleshoot, I used both older and newer versions of the software and had to acquire all the patches for both. There is no clear answer as to why the same code behaves differently within these two APIs. That's a problem. However, it's not really a stability issue.

The solution is quite scalable, and great to use for any project of any size or scope.

I only use the solution for my personal use and therefore don't have access to technical support. I can't speak to how helpful they are, or how responsive, as I do not use them. I don't have any practical experience to speak to.

That said, having dealt with Microsoft technical support in the past with other solutions, I can say that, in general, they are very capable and have many experienced people on staff to assist. I've been satisfied with them in the past on other products.

The initial setup is pretty simple and straightforward for those with knowledge or training. Basic users may have problems, however.

For myself, with so many years of experience with many types of Microsoft solutions, I found everything very straightforward.

It's not that the process isn't intuitive, it's just that, if you don't know what to do or look for, it can become a bit confusing. You must study many new terms and methodologies before you can get around to beginning the process as a completely new untrained user. There may be ways to watch videos online to learn a few tricks and to help you visualize the process.

I have many years of experience with Visio and Microsoft, therefore, I can handle the installation process myself.

I primarily use the solution myself for my own projects. I'm a customer and end-users.

In general, I would rate the solution at a six out of ten.

I would recommend this product, however, at the same time, I suggest to everybody to know and practically use several tools, so as to keep up their overall knowledge and skills. For some purposes, it is easier and more reliable to use one tool, and for other purposes, it is more reliable to use another. I do not recommend to anybody globally to work alone with one tool, separately from all the world.