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.

Our primary use case for Visio revolves around business process re-engineering, as-is process, to-be-processed, and then time and motion study, value stream mapping, and in collaboration with everything together.

Visio has improved our organization through an essential collaboration with the other Microsoft applications like SharePoint and Excel. In the earlier days, what used to happen was that a majority of the organization captured all the as-is processes, the time and motion data in the form of Excel and then they used to create process diagrams using other freeware applications. However, collaboration allows easy and convenient sharing with other stakeholders, that is really helpful with Visio.

The features I find most valuable are the integration with the other Microsoft applications, specifically Excel.

The one particular thing which I would like to see improved is in comparison to other products in the market, and is still lacking in Visio, is publishing on a web application. For example, there is a freeware application business process modeling tool, Bizagi. This tool has a very good interface. It also provides visibility allowing users to publish on SharePoint directly. Then the entire product gets converted into an HTML format which provides a one-click on all the attributes of every task, a detailed description, direct visibility, which I find is still lacking in Visio.

An additional feature I would like to see included in the next release is the implementation of web publishing. For example, for any task or any flowchart diagram that I create, example "talk to the customer." Now using "talk to the customer," return adding attribute like "this is a step-by-step document file that you should follow" or "these are the setup questions that you should follow while talking to a customer."

These documents can be attached to that specific task, and when I submit this on the web, users will get all the description, along with the attachment.

5 years

As far as the stability of the solution I think it still needs to grow up when it comes to the interface usage.

My impressions of the scalability of this solution on a scale of one to five I would rate the scalability a 3.5, with five being the highest.

I know of 50 users working with this tool. Some of them are engineers. For the people who are not technically sound, for them, they find Visio quite complicated so they try to avoid using it. That is still where Visio needs to grow. In terms of user interaction, UX, and user interface. There is some obstructive complexity. 

I did use previous solutions, like as I mentioned one of them was Bizagi Modeler, which is growing in the market. Currently, I'm using IBM Blue.

The reason why there was a switch from Microsoft Visio was because of the user interface and easiness to UX. It's a complete BPMN solution, however, Visio can be used for multiple purposes. Now depending on the kind of audience, it was quite easy for them to use Bizagi Modeler. That's the reason why I introduced Bizagi Modeler in my organization. 

After switching organizations, I've found that Microsoft Visio was quite challenging and a little too complicated for the users. Irrespective of understanding the complete utilization and the power of the tool, people are switching to different solutions, so we were using IBM Blueworks.

The initial setup was straightforward. It's quite easy. I worked on a couple of projects which took two or three months to complete because they required extensive organizational level detail, like from top to bottom. Using Visio, it's quite easy and I like it.

The IT team takes care of the installation and deployment of Visio.

Before choosing I did a market evaluation. I performed a needs evaluation as the first step in our market evaluation. We considered what kind of solution we wanted and if it was okay to go with a freeware solution or is it right to go with the licensed software. Initially, we were Microsoft Platinum Partners, so that's why we had Microsoft Visio well established in our organization. However, again, when it comes to the kind of usage and along with the maturity of the process that we had, it was a simple move from my end because you're paying for a license and if you do not use the overall potential of it, including the user interface, I think it's not worth to pay for those applications.

The only additional advice I would give, Visio is one very powerful tool in the market. Not just the application, but also its effectiveness to collaborate with other applications. Everyone is using Microsoft applications; it's how you work across platforms, and this collaboration makes life easy.

The individual applications have a lot of functions an features that's the reason why each of these applications is quite complex. You need to understand the functions before getting the full value of this tool.

On a scale of 1 to 10, with ten being the best I would rate this product an eight-over ten because it's a tool what works in collaboration with other applications very well. I'm deducting two marks because it's still complicated for the very generic user. The solution should be developed with a variety of end users in mind. It needs to be user-friendly and easier to use for all different kinds of users and user experience levels.

I use it for diagramming networks, racks, data centers, data flow applications, etc.

I am using its latest version. We have an M-365 membership, so we can access it in the cloud, but we download the application because it works better.

It is a useful tool to map data flows, network objects, and computer science technology and show to clients. It does what I need it to do. It's a tool I've used the longest, so I know it the best, and that's probably the claim to fame.

Sometimes, there is a little bit of a learning curve with it, especially while doing complex network diagrams and getting the lines to snap the way you want them and not overlap or be confusing. It would be great if there was a built-in tutorial. It is not that you can't YouTube, but it would be nice if they gave you some free training. I've been using it forever, but every now and then, I got to do something complicated with it and I wonder how do I do that again. Maybe they do have such information, and I don't know. I have not done research on it because a bunch of people work for me, and some of them are better at it than I am, so I just ask them to do this for me.

There are some applications that you can run in an environment, and they will run through, do auto-discovery, and map the network environment. It would be great to see something like that in Visio, but Microsoft probably doesn't want the hassle of having to deal with it because all the ones out there don't work that well anyway. In order to work well, you have to give them a ton of access to your routers and switches, and nobody wants to do that because it is a security issue.

I have been using this solution for 15 years.

Its stability is excellent. It is a very stable application.

It is basically a client application, and it has one to one ratio in terms of the application being installed on the client. So, I'm not sure how it scales.

We have 15 users. All are technical architects and engineers. Its usage is moderate. It is just an as-needed tool, but everybody in our two teams needs it.

I never had to contact Visio's technical support.

If I did, it was a long time ago. Sometimes, we use PowerPoint for simple diagrams. Obviously, it's not nearly as powerful, but in a pinch, it works.

It is pretty basic, but I've been using it for 15 years. So, you get some stencils, and you build some templates.

We probably have an M-365 E3 license.

It had the same struggles the entire time it has been around. It is a good tool, but it got a little bit of a learning curve. Sometimes, you got to figure out how to make the line snap correctly so it is not really confusing, but it is a valuable tool. People want to use it.

I would rate it an eight out of ten. It is a really good application for what it does. I'm sure there are one or two other solutions out there that are pretty good, but I don't have a lot of exposure to them.

On-premises

I use Visio to create diagrams and provide consultation services to customers. I position the icons of devices in diagrams with descriptions such as the name, brand, type of connections, and speed using Visio.

Visio allows me to create detailed diagrams that provide value to customers by giving them a clear view of their network and devices. This feature enhances trust and confidence from clients as they see that we understand their environments well. Customers appreciate the detailed drawings of their network.

The visual icons and shapes for different vendors like Cisco network could be improved. Often, I have to contact vendors to get specific icons to use in Visio diagrams, which makes the process cumbersome.

I have more than twenty years of experience with Visio.

Based on the size and complexity of customer requirements, deployment time can vary from a few minutes to a significant effort.

The new versions of Visio are very stable, unlike previous versions that had significant bugs.

Visio has high scalability, and I rate it ten out of ten.

We generally resolve issues internally within our IT department rather than contacting Microsoft's technical support. However, reaching Microsoft team support directly can sometimes be difficult.

Neutral

The initial setup of Visio is easy.

I recommend Visio to others based on my experience. Overall, I rate the solution ten out of ten.

On-premises

I use Visio for high-level network design, and I use it for home planning since it is easy to use.

With Visio, one of its core features stems from the fact that you can get plugins for Cisco, Microsoft, etc. In general, Visio provides a plugin for sample diagrams, graphs, etc.

It will be a great improvement if Visio gets upgraded to provide its users more in the area of 3D. With Visio, when I plan for a house and the height of its walls, I should be able to view the walls in a 3D mode, which can be a huge product improvement.

SketchUp is a program that is not as easy as Visio to build 3D models. If I want to build a house in 3D mode with Visio, then I should be able to do so with one click that allows me to change the house model from 2D to 3D. I don't have the latest version of Visio, but in the version of Visio I use currently, I don't see any 3D mode provided to users.

There are some issues in Visio with the connectors, and it gets tricky when you want to connect objects with each other. The aforementioned aspect of Visio can be considered for improvement.

I have been using Visio for fourteen years. I don't have the latest version of Visio. I don't remember the exact version of the solution.

It is a stable solution. Stability issues only crop up in Visio when there are some normal issues related to Windows or Microsoft Office, which may arise in cases when the system hangs.

Scalability-wise, I rate the solution an eight out of ten.

I am the only person who uses Visio in my company.

Visio is the first solution I have ever used, which is one of the major reasons why I still stick to it.

The product's initial setup is really simple.

The solution is deployed on an on-premises model.

If I want to buy Visio for myself, I think it will be around 80 to 120 USD, though it is important to consider that I am unsure of its actual costs.

I rate the overall product an eight out of ten.

On-premises

The solution is easy to set up.

The stability is okay. The performance is pretty good.

It's a very flexible solution. 

It requires a lot of skill to get into it. 

It requires more simplicity. You have two options. Either you go very simple, then it's quite a hurdle to get into it or you go very complex. It's a hurdle too. However, when you decide to go complex, then you know exactly what you're doing. Therefore, the gap between, let's say, a common user and an experienced user is large. For Draw.io, I can point anybody to Draw.io and they can just get in there and do whatever they want to do, and it works for them. Visio requires someone to be more experienced.

There's also a solution called TAG for writing documents, which is awesome. It's mainly used in universities, education areas, and big pharma. It's an awesome tool. It takes a lot of time to get in there, but when you are in there, you can do basically almost every kind of document without any issues. Visio is much more similar to this. There's complexity and yet you can do anything within it.

I'm not used to the new versions of Visio. There is a standard version. Always when I get in there, I get frustrated as I can't do the things that I like. The usability could be improved.

Stencils are always an issue, however, this depends on the vendors.

The stability can get iffy if you are doing very complex things. 

I've used the solution quite extensively during the last ten years. It's been a long time. 

The stability really depends on what you're using and what you're doing. When you get complex, you can get some crashes. I have never figured out why that is. It may happen when you have different cards or registers with a lot of things linked together and grouped. For standard usage, it's awesome. When you do more complex things, well, you might have issues.

I can't say a thing about scalability. 

I can't speak to technical support as I don't deal with them. We have in-house support and our in-house support is abysmal. What happens after them, I really can't say. If you call them to ask questions, they just say, "We have to look it up." And that's the last thing you hear. That, however, is an internal issue. It's nothing to do with the quality of the support in general.

We did not previously use a different solution. 

I do now use Draw.io a lot.

The implementation process is quite simple and straightforward. 

Deployment times vary. It depends on how you manage it. If you do a good management process, with document templates and everything, it takes a lot longer. We basically just made packages and rolled them there, using the variables. I'm not a package filler, however, for us, it was easy.

I can't speak to how many people now manage the solution as it is completely outsourced. We don't manage it ourselves. 

We handled the implementation in-house. We did not need to hire any consultants or integrators.

I can't speak to the cost of the solution. We are using just the standard licensing terms for an enterprise license agreement with Microsoft, where we basically have a lot of things in there. I don't think it's included in any Office Microsoft 365 licenses. We basically just have a subscription for every license we're using, however, I can't speak to pricing or terms. 

I have to let Visio go as most often it's too complex and it takes too much time. I'm rather using Draw.io, which is by far enough for almost everything I do expect if I am really drawing up complex cabling things in a building, for example.

I'm just an end-user. The company I work for is a customer. We don't have a special business relationship with Visio.

I'd give new users the same advice I do for every tool. Be really clear on what you want to achieve. Be really clear that when you do it and do it in a strategical and tactical way. Don't do a single deployment and don't just install it and let users do their thing. Agree on templates, stencils, et cetera, that you're using within the company, and keep it simple and crisp, as simple and crisp as possible.

After using the solution for ten years, I would rate it at an eight out of ten.

On-premises

I primarily use Visio for creating mind maps and other visualizations.

I also use it for process modeling, but we are searching for a specific business process modeler because Visio doesn't have the full scope of capability that we need.

The most valuable feature is the set of diagramming tools.

It is quite flexible and easy to use.

The big downside to Visio is that it's very difficult to push the design through to Power Automate, to become a workflow that you can use.

The process modeling capability would benefit from a quick modeler tool, such as one where you use a table that is populated using the BPMN 2.0 format.

In the future, I would like to see a connection with the workflow so that you can create your model and then execute it.

I have been using Visio for about ten years.

The stability is good.

Scalability is something that needs to be improved.

The models are not linked together, so unless you're using SharePoint or you've defined your own workflow, there is no version control. This makes it more difficult to collaborate, link models, and make sure that everybody is using the latest version. Essentially, you have to build your own framework from scratch in order to do that.

We have about 100 users, most of which are end-users. It requires minimal administration.

We have not had to contact the vendor for support.

This was the first proper diagramming tool that we have used.

The initial setup is straightforward. Our IT department installed it, and I think that it took a couple of hours to deploy.

Our in-house team is responsible for the deployment, maintenance, and providing support.

Our license for Visio is including with the Office 365 subscription.

This is a product that I can recommend, albeit for limited use. If you just want to draw basic models and create systems diagrams, and not do anything too clever and link it together, then it will work well because it's quite flexible and easy to use.

I would rate this solution a seven out of ten.

Public Cloud

Microsoft Azure

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.

Hybrid Cloud