Visio Reviews

I use it for high-level detailed and high-level conceptual drawings for leadership. I also use it for small drawings when I'm doing documentation, policy creation, or building some kind of a spec.

It is installed on my personal machine. In terms of the version, my Office suite is 19, so I assume the Visio version is whatever is packaged with Office 19 suite.

It improved the way our organization functioned years ago, but right now, people are trying to find other ways to do what they're doing in Visio because the tool is stagnant and really not moving. It hasn't for years. They've added features but really not much. They're more pulling those into higher-level tools such as Azure Development Studio and things like that.

What I like about it is that the templates are easily findable and usable, and they are usually created for other software packages. It seems to be pretty much widely adopted in the industry. 

It is a visualization tool, so database visualization is pretty static in it. They haven't moved the ERDs very well. They haven't adopted any real visualization like what you have in Hackolade for JSON or other data patterns. It has none of that. If you go onto broader patterns, you can actually label and integrate with a data set, if you want, for Visio, but it's very clunky and very difficult for me to assign that to another user. I can't assign it to a junior or a documenter. They really haven't cleaned up and made their tools simpler to use when linking to data, which is primarily what you're trying to do.

The versioning has always been a bit messy. You can't have a state of how it is to how it was without having two drawings. You can layer, but layers don't work very well for the most part. They just haven't progressed the tool. The tool isn't keeping up with the architecture that people are forced to do. So, more and more people around here are abandoning it and moving to alternate tools. It is now being used for just basic drawings. It is no longer an enterprise-quality development or documentation tool. It can be, but you'd have to work pretty hard at it.

It doesn't have autosave features with respect to the way some of the other Office tools have it. It is pretty clunky if your machine crashes or gets shut down because of a low battery or something like that. To make sure that the changes persist, you need to look at the last version of it. It has still got on-premise features, and it still has that same paradigm of clicking "save", and you better keep clicking "save" to make sure it doesn't get corrupted. It is very old school for cloud tools. Any Office tool, Google tool, or Apple tool is going to save all your work because it's basically updating via messages, but that's not how Visio works. It is very old school. They just aren't spending any money on it.

I'd love them to get back to being able to do true data flow diagrams that are easy to use and that actually can be pulled from data lineage. In lineage diagrams, you can pull the data and actually reflect them in the right drawing. There is a little bit of that going on in some of the drawings but not much. I want to be able to do database design documents, if necessary. I've got people doing those. I'd like to do network drawings with multiple layers in a simpler way and to the point where the layers have displays of viewpoints as most systems do. 

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

It is very stable, but there are no autosave features in it.

There is no scalability to it. It is on your machine. You could put files into Teams and somewhat scale through Teams, but it is not scalable. You don't have the ability to have team cooperation and repositories. You can do repositories, but it doesn't have any of the features that allow you to regulate and have all the things you'd have or expect in any enterprise quality development tool or design tool. It doesn't have any of those features. You have to broaden the suite and buy about nine other Microsoft things to somehow attempt to get those features.

Its usage is declining. We used to have about 150 users. Now, we probably only have about 50 or 60 users. We're buying tools that knock out some of the edges of what Visio would do. Enterprise architecture is really no longer done in Visio. It is done a little bit, but for the most part, we use other tools for it. Although it can make the boxes, it can't really work a process in enterprise architecture. It is not a development or life cycle management tool.

I've never been able to queue up technical support on it. We don't allow our internal people to directly communicate with technical support. It goes through an internal layer.

It is easy to set up. It is also easy to add libraries to it.

I know you can pick it up in retail for under a thousand per person. You can also pick it up for cheaper than that. Microsoft has about 7,000 licensing models, and you get certain percentages off specific licensing. If you're a partner, you get specific numbers of licenses with the partnership price.

Visio was owned not by Microsoft. It was its own company way back, and it was actually moving very well. It had ERDs and was actually developing very well. Microsoft bought it. They picked it apart and started moving those tools into other things and downgraded the tool. I don't think it has met the level of expertise and the level of technical proficiency that it had 15 years ago. It was downgraded, pure and simple. A lot of those pieces are used in other things now.

I would advise others that just don't try to make it more than what it is. Find a tool that is enterprise-worthy if you're trying to move to that level, but don't try to make it into an enterprise tool.

I would rate it a six 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.

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.

I use Visio for visual rendering of technical concepts. I use the stencils that depict different workflows, data flows, or architectural structures from an IT perspective that I could render in other documents like PowerPoint or Word documents.

Since we work in IT, we deal with very technical abstract concepts. So having the ability to visually depict a concept that we're trying to get across is helpful. When we write documentation, we have to write it for the broadest audience possible. If you can reduce the number of words, either in technical documentation manuals or others, and do it visually, that seems to register with the targeted audience.

The thing I like most about Visio is the stencils. As the product has matured over time, it comes with more stencils and objects that you can just pick out of the menu and go with. 

It thinks that it knows what you want to do, but it doesn't. It has a way of behaving that can be very frustrating from time to time. Either it moves things about because it thinks its placement should be at a certain place, or it's keeping track of things that you don't necessarily see, so it moves something elsewhere. So when the software requires more keystrokes than one would think to either capture or register a placement, or a drag and drop function that you think should be easily executed, it sometimes doesn't always work that way. Regardless of the skill, the user experience can sometimes be interesting. The predictive behaviors of it at times can be a little bit of a drag.

I've been using Microsoft Visio for twenty plus years.

More often than not, stability is not an issue, it's a fairly stable product. I've noticed that when I have multiple products open, like PowerPoint, Excel, Microsoft, and a couple of others, sometimes it begins to act flaky and then I have to start cutting down services or closing things. In general the Office suite, sometimes it can let you know that it's going to start acting funky, or the behavior begins to be flaky. You have to just know by experience that's your cue to cut down services, close windows, close applications, because the robustness of the applications are not allowing you to be as multitasking as you want to be.

Scalability is okay. It's like everything else, most people they use at most, 30% of the product's capabilities, so there's a lot of stuff in Visio that doesn't necessarily get used. You don't know that when you do the typical installation, that a good part of the product capabilities are never going to get used. The default configuration is to load everything, as opposed to custom, and it's just easier just to let it deploy everything. As a result of that, there's a lot of functionality that gets pulled in, and memory and CPU that may be consumed that the user would never benefit from. That's just the nature of the beast.

Setup is mostly straightforward, but there are occasions where the installation process can be prone to some issues that may not always be apparent until after you deploy it. Sometimes the installation experience requires expertise. Sometimes it's not always clear if you're going to have compatibility issues with the 32-bit version or the 64-bit version, there's been those type of subtleties in the past.

Since I've worked in different shops, sometimes I have installed it from my own product license that I purchased. So I've deployed it from a physical media and I've deployed it from an on-site provider because I purchased the key and there was no physical media. Then there are other times where the company that I worked for, their end user computing team, or their desktop support team, because they have to keep track of the licenses, they own the deployment and the push down to the user and make it part of their image. Because there's a cost to deploying that product in some variation of the product packaging, they tried to keep control of that. 

Just be mindful that the software, while it's helpful, it can behave in ways that can be a little frustrating. A lot of companies say go and find a Visio-like product that can do 70% of what Visio does, for free. There have been companies that I've worked for that said we will not pay the license fee for Visio, go and get a similar product that you can download from the web that can do 70% of what you need it to do. 

I would rate Visio an eight out of ten. It's a product that's been known. Many people use it. It's got an established install base. It's not flawless by any means, but since it does allow some intimacy with the Microsoft products, that's probably its greatest thing, and in a business environment, that's important. Because of its cost structure, a lot of organizations are trying to figure out if there are alternatives out there, which there are. Those other products can do much of the heavy lifting that Visio does at a cost point that, in some cases, is very attractive.

I utilized Visio to craft visual aids for my presentations, including diagrams that visually illustrate data, such as flowcharts. Additionally, the solution was used to generate diagrams that showcase a series of connected ideas using arrow charts.

A major benefit of Visio is its user-friendliness. Upon opening the program, you have access to a variety of pre-made templates, saving you time and effort. All you need to do is input your data into the template and you're ready to proceed with your project.

One issue I've noticed is that when working on a shared video link with a friend for Visio, there can be a delay in changes reflecting on their screen after I've made them. This also occurs when we're working on the same document. It would be beneficial if changes could be reflected in real-time. Additionally, I've experienced some text size issues with the flow task feature. Sometimes when I enter text, it appears very small, and increasing the size causes it to extend beyond the diagram, creating formatting issues. It would be helpful if these text and formatting issues could be addressed.

I have been using Visio for approximately a couple of months.

The solution is stable. I did not face any crashing or issues.

I would recommend Visio to individuals who don't necessarily use Microsoft software. With Visio, they can create visualizations and diagrams easily. Additionally, they have the option to download and share their work on their preferred platform, such as Google. Visio can be used for multiple platforms, regardless of whether you use Microsoft, Google, or other cloud-based services such as Amazon Web Services.

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

In my experience, Visio is highly scalable. I've used it within an organization that utilizes Microsoft OneDrive and Teams for their operations. This allowed for easy integration of Visio with the organization's existing Microsoft software and made it simple to share diagrams and visualizations with anyone in the company, regardless of their position or location within the organization.

We have approximately 1,000 people using the solution in the branch of the company I am working in.

I have not faced any issues to need support.

Setting up Visio is a simple process. You can access it via the website and generate a link, which can be shared with others in just a matter of minutes.

I can do the deployment of the solution.

My organization has paid for the solution. However, I have used it personally without payment. There is a free option available.

I rate Visio a nine out of ten.

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 the solution primarily for making high-level and low-level diagrams and making any other diagrams that might have some items available that we can quickly turn around architecture with.

I like that I can copy and paste icons and drag and drop items. It has a lot of great features.

It is very stable. It's reliable. 

The solution can scale.

It is easy to set up.

There should be more items available from a variety of other products that can be integrated. 

Architectural diagrams could be enhanced further.

The icon support is limited. We'd like third-party icons available to us.

I've used the solution for five years. I've used the solution for a while at this point. 

The stability is great. I'd rate it nine out of ten. There are no bugs or glitches, and it doesn't crash or freeze. 

The solution can scale. I'd rate the scalability seven out of ten. It could be a bit more scalable. 

We have 4,000 to 5,000 users on the solution.

We have used other solutions in the past. There is a product called Lucidchart that I've used. It's more flexible in terms of icons we can use. 

The initial setup is very simple and straightforward. It is not complex or difficult. 

While we have an on-premises deployment, the cloud is available on Office 365. 

The pricing is fairly reasonable. I'd rate it six out of ten.

We are Microsft partners.

I'd rate the solution seven out of ten.

People should consider the solution. However, there is a lack of customization available. 

I am using Visio for migration and application development. Additionally, we did a Microsoft Azure landing zone for companies to implement CICD pipelines. 

We typically do hybrid deployments because of the data security issues that can arise. However, there is a lot of opportunity coming for native cloud deployments.

The most valuable feature of Visio is the credential management, endpoint manager, and active directory for Microsoft Azure for our hybrid infrastructure. Additionally, there are plenty of features available.

Visio could improve by simplifying the application to allow the business user more understanding. This will allow us to bring the solution deeper into the organization for use. It can be difficult to navigate and some users tend to rely on third-party applications for auditing, compliance, and policy configuration.

I have used Visio for approximately four years.

I rate the stability of Visio an eight out of ten.

We have approximately 10 people using this solution in solution.

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

The support from Microsft has been great. I receive direct calls from support to resolve our issues. They have been responsive and helpful.

I do not have experience with other solutions in the same category.

The initial setup is easy. I have been doing it for many years.

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

My advice is this solution is scalable and easy to deploy. It is an asset for an organization, which is looking for an immediate infrastructure to be built on a project.

I rate Visio a nine out of ten.