Visio Reviews

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.

My primary use case is for designing the architecture diagram and the network diagram. 

The most valuable feature is how easy it is to use. 

Visio could be improved by adding more features. If you look at draw.io, they have more features. Also, if you want to design something for the cloud, Microsoft Azure still isn't enabled, so you need to install the plugin. This prototype is easily available, though. 

I have been using this solution for almost ten years. 

The stability is quite good. There is not much maintenance really required. If it's on your desktop and something goes wrong, it is usually available to repair again. You don't need anyone else to maintain it. 

I previously used the Sparx System Enterprise Architect, but my experience with it was limited. It was discontinued because they stopped the licensing. 

The installation was straightforward. It takes about five to ten minutes and you can do it yourself. 

I implemented myself. 

I pay for the license and it is very expensive. If you're only going to use this tool from time to time, you can save money by just using the available online tools. But if you plan on using it heavily, then it's worth it to invest. 

I would rate this product an eight out of ten. I recommend this product to others because it's a useful tool for designers and architects. 

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. 

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.

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.

Visio is mainly used for documentation purposes. For example, drawing flow charts or network diagrams. It can also be used for defining schemas or application development.

In my organization, people from multiple departments use it, especially the IT team. They prepare documentation on the network architecture. Additionally, the data team uses it to create flow charts, sequence diagrams, and schemas.

The solution is easy to understand with some hands-on experience.

Microsoft should include Visio as part of their Office 365 offering.

I have used Visio for approximately 10 years.

The solution is stable.

The solution is scalable and flexible.

We have approximately 15 people using the solution.

Microsoft technical support is convenient. They have an online community for Visio and if we have created a ticket with the support they always respond promptly. We have not had any problems with the support.

The installation is easy, it only takes approximately five minutes. You only need to go to the vendor website and download an executable file and then it is straightforward.

We did the implementation ourselves. The solution does not require a technical team for implementation.

You can purchase a corporate license for more users to use the solution. We have purchased a stand-alone license and which could be cheaper.

I rate Visio a nine out of ten.

I'm an architect; I primarily use Visio for drawing diagrams.

The most valuable aspect of the solution is the exterior interface. The exterior application interface and the keyboard shortcuts available help me to do some major work and diagrams.

Since Microsoft did some updates a while back, I've found the solution to be very stable.

Technical support seems to be pretty good.

The initial setup is pretty easy.

The application could be lighter or it could be faster with documents. That just comes down to the user's CPU power and how big your document is. 

I'd like it if there was some sort of web integration, where you can deploy VST diagrams or at least SVG diagrams or something to the web. It might be useful. I'm not sure if it does it right now, I haven't looked recently. 

I've likely dealt with the solution for 15 years or so. It's been well over a decade. It's been a long time. It's likely been for however long it's been on the market or for however long Microsoft has had it.

The solution's stability is quite good. It struggled a bit in older versions, however, Microsoft has update dit and it's been very, very good. There are no crashes or freezing. There aren't bugs or glitches. it's reliable. The performance is good. Ever since we've been using it on Windows 10, it's been great.

It is scalable. I've used it and try to compare designs, so it's a fairly simple environment, and it's roughly the same. Again, that kind of depends on your GPU, on the power of your workstation that you're using. If you don't have as powerful of a workstation, you have issues with larger jobs.

Those that use it in my organization are mostly architects. There might be around 100 or so users in my company, although I don't have exact numbers.

I'm not sure if we have plans to increase usage.

It's my understanding that the solution has pretty good technical support. I haven't dealt with it personally, however, my colleagues have and it's always been very positive in terms of the comments we've received regarding Microsoft tech support.

The initial setup is not overly complex. That said, I've been using it for so long that I'm fairly comfortable with it. It's my understanding that the setup today for that tool would be fairly easy for a new user. It should be noted that that's coming from myself, as a person who's dealt with the product for so long.

The deployment of Visio to my workstation was as simple as requesting the download from our central section and it downloads within 10 to 15 minutes. The deployment for my workflow is fairly trivial for me. That's due to the fact that we're using an internal package from the site.

I'm not sure what kind of maintenance is required. It would be an automated packaging process. We would have some sort of a tool chain, where the tool is packaged, and then unpackaged and then deployed to our location.

I don't deal with billing or licensing aspects of the product. I can't speak to the actual costs or if it is expensive or cost-effective.

I'm not sure what type of business relationship our company has with Visio. My role usually revolves around working with Visio and various website engines.

I'm not sure which version of the solution we're using.

One of the key things for a company considering Visio would be to establish some guidelines for how Visio should be used and how it's used to augment existing workflows for the customer company. For users, it would just be to gain comfort with the tool shortcuts and get to know the tools, strengths, and any weaknesses. That you may perceive and just understand them and the solution becomes easier to work with.

I'd rate the solution at an eight out of ten. It's just a reliable workflow for me so it's a pretty good tool. Lately. it has also been pretty stable.

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.