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.

The solution is primarily used for diagramming. I use it for a couple of different things, however, it's mostly for diagramming and documenting data center infrastructure including racks, wide area networks, logical designs, physical designs, and conceptual models.

The ability to clearly demonstrate and create labels has helped the organization immensely. To be able to create and to provide detailed configuration guidance on what ports to plug wires into, et cetera, is useful.

We use it to discuss design, network, and configuration options, as well as provide detailed guidance to the engineers on how to connect and how to configure our data centers.

The product itself is useful due to the fact that it's widely accepted. I can go out on the internet and I can pull down stencils in VisioCafe. I can easily get pre-drawn stencils for whatever I need and that makes life a lot easier.

The initial setup is pretty straightforward.

The solution is stable. 

There are too many features. One of the things I find most annoying about Visio is the automatic connections. They're just like everything Microsoft does. They overdo it. There are too many features - especially when I have people who are not familiar with the tool. 

Users will start creating text boxes for objects that already have a text feature. For example, if you've got a computer and you take a picture of a computer or a stencil of a rack-mounted server, people wind up putting text boxes next to it instead of double-clicking on the box and adding the title there. It's mostly user error, however, it's overwhelming for new users. They don't realize what can be done.

I've been using Visio since before Microsoft bought it. It's been anywhere from 15 to 30 years. I've definitely used it for more than a decade. It's been a while. 

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable for the most part.

I use the desktop version of the product and cannot speak to how scalable the product is. It's only limited by the resources of the laptop itself. 

In our company, we have 10,000 users on the product. It's used extensively. All departments use it.

I can't say if the organization plans to increase usage or not. 

I never need to call technical support. I cannot speak to how helpful or responsive they are. 

Our organization has used the solution for decades. We haven't used anything else. 

The initial setup is very straightforward. That said, I've also been doing this for three decades and therefore have had a lot of experience handling the process.

It's installed pretty cleanly. It's a Microsoft install and there's not really a whole lot of issues. If I don't have a stencil for what I'm drawing, I can go on VisioCafe and a couple of other websites to get them. You can get stencils for network devices, switches, routers, hubs, servers, and all sorts of fun stuff.

I cannot speak to the exact pricing. It's not an aspect of the solution I handle. 

We're a customer and an end-user.

Visio is one of the only approved products where I work, and it's one of the best.

I don't know if there's a newer version out, however, the only one I'm allowed, the only one the government provides me with is, is the 2013 version.

I'd rate the solution at a nine out of ten. The only real problem is that there are too many features and it's somewhat overdesigned. 

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.

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 use the solution for process mapping and improvement.

The solution is user-friendly.

The performance sometimes lags and has room for improvement.

The price has room for improvement.

I have been using the solution for a few years.

The solution is stable.

I give the scalability an eight out of ten.

The initial setup is straightforward. The deployment took under 15 minutes by following the documentation.

The implementation was completed in-house.

We pay annually for the Visio license and it is expensive.

I give the solution a nine out of ten.

Visio is user-friendly and I recommend the solution to others.

I use Visio to elaborate on the workflows and use cases that I see for my product, and also to illustrate specific processes for users of the product. In essence, I use Visio to help visually represent processes and as a communication tool that lets me explain things to end users in a simple manner.

At the same time, I also use Visio as a base from which to communicate with my technical team so that they are able to better understand the user's perspective while they are developing the product. I use it on both fronts, especially since I have been in a role which is more on the consulting side while having to liaise with both the end users and the technical team. For all these use cases, Visio has been a key tool which has been very helpful to me.

The tools tab within Visio has been amazingly useful, and it is updated quite frequently. Along with how Visio handles components and everything else, I would call it an easy-to-use tool. Anyone with years of experience in IT who has just been introduced to Visio won't feel like they want to shy away from it because the entire tool itself is self-explanatory.

I have personally used Visio across three different organizations that I've been in, and I have been more happy using Visio than any of its competitors.

From my perspective, Visio could probably add more help guidelines for users, and I would prefer to see more intuitive user interfaces to help with dragging and dropping, using the right components, etc. For example, more tooltips would be appreciated, such as when hovering over a component with the mouse.

It would also be helpful is there were an option to customize the fields and diagrams based on the color, because sometimes you get a black and white coloring with your diagram, whereas I would prefer to have it set to my corporate template and color scheme, which can be a bit difficult to get right. 

I have been using Visio for more than eight years.

I would give Visio a nine out of ten for stability.

Based on my own personal usage, I find Visio very scalable as there are a lot of a options available to explore. Because of this, it is often used by people like myself who liaise between product users and other people such as technical architects who need to communicate their architectures.

I don't know the exact figure, but I would say there are around 10-15 people who use it in my company.

I would give it an eight out of ten for scalability.

I haven't yet needed to reach out for technical support.

Before Visio, I used Enterprise Architect (EA).

I had my IT team help me so it was pretty straightforward. I would rate it an eight out of ten for ease of setup.

My IT team took care of the implementation, so I don't know the technicalities of it all. The IT team's work in implementing it was an organization-wide activity.

We have about 10 to 15 people with Visio licenses in my company, but I wasn't involved in the direct negotiation of the prices and since this was taken care of by my administrative office.

I would definitely recommend Visio and I would rate it an eight out of ten.

There is a limitation in Visio. The solution is not aligned with a database. I can't submit more than one request at a time or do any calculations or have multiple users, or multiple procedures.

Microsoft needs to put more effort into data analysis around the tips and workflow related to the number of skills, procedures, and any small analytical information.

I would like Visio to use AI to evaluate the processing side because currently, it is not logically based.

I would like to have reports added to the solution. For example, if I drove a business process that related to a service, and this service related to another service, I would depict some servers. Reports which predict that from more than the related service would be very beneficial. These related procedures or related processes would take place on the solution's servers, database, and application.

I have been using the solution for ten years.

I give the stability of the solution a ten out of ten.

The solution is easy to scale.

We currently have around 20 users.

The technical support is easy to access and receive resolution.

The initial setup is straightforward.

I give the cost of Visio a five out of ten.

I give the solution a five out of ten.

There may be other solutions that are better than Visio on the market but when we complete an analysis we can conclude that the cost and ease of use of Visio are good.

I recommend the solution to other users.

The company uses Visio for a maintenance project occasionally. I use Visio for infrastructure architecture and create data models on it.

The most valuable feature of Visio is diagram creation. If you have a presentation, you can create your data model using Visio. The tool has Microsoft components you can find in Microsoft Power BI, particularly the drag-and-drop functionality and link creation between the two components.

An area for improvement in Visio is pricing. It's a costly tool for my company because it only uses Visio occasionally.

I've only used Visio four or five times in the ten years it's been in my company.

Stability-wise, Visio is an eight out of ten.

I didn't see the option to scale Visio because it's one user at a time and installed on your local machine, so I'm not sure about its scalability.

The initial setup for Visio is easy because it's a Microsoft product.

Visio is a pricey tool. It's a five out of ten, cost-wise. It would be great if it had a pay-per-use licensing model because my company uses it sparingly. If Visio had a two-day use license, that would be helpful.

My company uses Visio, but not very frequently.

My rating for Visio is eight out of ten.