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 primarily use the solution to make new core designs. I connect the designs to the projects I'm involved with. 

I love that interface a lot. I've been involved with design my whole life, and this solution is an excellent program in terms of assisting with design projects. You can work on quite large projects with Visio.

I've used the solution for so long, and I have so much experience with it, I'm quite comfortable using the technology.

The solution makes it very easy to make exciting pictures and designs. Everything is very intuitive and simple to figure out.

I'm not sure of the features that are missing. It's a pretty complete solution.

In some instances, I do feel that AutoCAD is a better solution to use. I find AutoCAD makes better lines and has a few better capacities.

The maintenance of the solution could be better. It might be better on a PC. I'm not sure.

I'm not sure if Visio is the best for 3D designs. One does have to make a bubble. It's typically better to do such designs in AutoCAD.

I find that, in order to get money, advertisers, etc., AutoCAD is a better solution.

The user interface could be more robust. It can export to AutoCAD, however it doesn't do so very effectively. You really struggle with exports as they end up exporting in different forms. It doesn't translate exactly. What is white in Visio ends up being black in AutoCAD. Ultimately, you have to go and fix everything. It's not that easy. You end up losing quality.

I've used Visio in the past 12 months.

In general, the solution is pretty stable. However, occasionally, we do experience a bug or glitch. 

The scalability of the solution depends on the project. You can only put it on so many devices. We have a rather large company, so we have quite a few people on the solution. Not everyone in our organization uses it. It's just specific departments. We're in telecommunication, and we use it in our department specifically.

I'm a big fan of support. They've been very helpful in the past. I'm satisfied with the level of service they provide to me.

I'm also used to AutoCAD and I can make beautiful designs with it. AutoCAD is more complicated, the final drawings are not better than with Visio. That's the main difference.

However, when you have to sell something like Architectura, the screen isn't as clean on AutoCAD.

The initial setup isn't too complicated. It's straight forward.

You have to spend your time with it in order to funny understand the solution in the beginning. It can be a little crazy at first due to the fact that there are a lot of rules we don't use. That said, it's not difficult to learn.

I'm not sure what the pricing is for the solution. I know that AutoCAD is very expensive, therefore, it's possible Visio is comparable.

I'm using the latest version of the solution.

I use Visio now, and I'll use it going forward. I imagine I'll always use it. I have used AutoCAD, however, I prefer Visio. It's my favorite as I'm so comfortable with all of the aspects of the solution after working with it for so long.

Overall, I'd rate the solution nine out of ten.

I'm into designing, so I'm using Visio for creating diagrams. Mostly it's for network, architecture, or data flow diagrams, depending on what the customers need.

What I like best about Visio is that it's flexible.

Sometimes, if I need to draw quickly, I use Microsoft PowerPoint, but if I need icons, which Visio has, I use Visio.

I also like that the solution gives me a much more powerful range of options.

The improvement I want to see in Visio is being able to edit it more quickly, particularly when pulling it out of another software and then editing it on that non-Visio software. Currently, the process affects the overall performance because it's not as quick as I want it to be.

If I were to add a new feature in Visio, and if I went wild, it's the feature of creating new diagrams from Visio, even if I'm on another document. If Visio is running in the background while I have another document open, it would be interesting to be able to draw diagrams on that document.

I've been using Visio for a few years now.

I didn't contact the Visio technical support team, and from what I know, the IT team didn't have to contact support either. Once, there was a bug, and the IT team couldn't do the installation until the next day, but even then, there was no need to contact the Visio support team. As a product, it's intuitive.

Setting up Visio is easy because you just need to check the block, click, and then it'll be set up, but that's because my company uses Microsoft 365. Setup-wise, I'm rating it as eight out of ten.

I'm not involved in the licensing of Visio for my company. However, for Visio licenses for my customers, I am.

Around fifty people use Visio within my company.

People in the company use Visio whenever necessary, but I use it more frequently. I talk to customers a lot, and I'm part of the sales process, which means I need to create diagrams, so I use Visio a few times a week. My usage is usually greater than other developers in my company.

I don't have any particular advice for people who want to use the solution, but Visio is a user-friendly product and easy to use.

My rating for Visio is eight out of ten because it's a good product.

My company is a Microsoft user.

I'm using only this tool for our full architecture block diagram development. We're using it for our action projects, what are we are running.

It's a part of our process where architecture and detailed document development are needed. That's it. From the architecture and flow diagram preparation perspective, when it comes to detailing the documentation before implementing other components can be done in Visio.

The solution is stable.

The scalability is good. We can reuse it as a model. It can be modified.

The tool is user-friendly. 

We are able to bring out what we want in terms of our architectural or detailed block diagrams.

The installation is easy.

I'm now used to the user interface. I like it. 

I can't speak to any missing features. It's been fine so far.

I've used the solution for a while. 

The product is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable and the performance is good.

We have found the solution to be scalable. If a company needs to expand it, it can do so.

Most people in our organization use the solution. It is meant for all engineers and then architects. Managers also use it when it comes to representing some project flow processes from the point of view of management.

We haven't dealt with technical support. I cannot speak to how helpful or responsive they are.

The initial implementation is very easy. However, I cannot recall how long it took to actually deploy it.

Our IT team handled the implementation in-house. We did not need outside assistance from integrators or consultants. 

It's just a supporting tool. I can't speak to any direct ROI.

While I know that we do have to pay a licensing fee, I can't speak to the exact details. I don't handle that aspect. I'm not sure if there are extra costs on top of the license itself.

We're a customer and an end-user.

We're using the latest version of the solution.

I'd recommend the solution. It's always a useful tool. Instead of using other drawing tools, I'd say that this one is likely the best option.  

I'd rate the solution at an eight out of ten.

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 am an HRIS (Human Resources Information Systems) specialist. I use Visio for a variety of things.  

• I do work charts on it.  
• I do WiX (Windows Installer XML).  
• I do all swim lane mappings.  
• I do process mapping.  

That pretty much covers it.  

The ability to do my mappings is the most valuable feature in the solution. It is the reason I have and use the product.  

I am fairly happy with the program. That would be about 90 percent happy. There is not really much that is wrong with it.  

The only problem I tend to have is that sometimes when I am moving objects around within the interface I lose the formatting or it changes type or linking. You have just got to get used to the connectors not staying in the right spots or how they behave as you work with it and know how to repair it. When you are moving stuff around the joins sometimes just do not go where you want them to. That is the join arrow or shapes or connectors might intuit what you are trying to do in another way than you might intend.  

It is an issue with learning the user interface and working within the behaviors of the program. When you move stuff around and it might move off the visible page, you just have to know to resize to make it fit in the view again. That part of the interface could be more intuitive or left to the control of the user.  

We have been using Visio for least eight years although I think it is closer to ten, actually.  

It is a pretty stable solution. I do not experience much in the way of bugs or glitches.  

I do not really have experience with scalability when it comes to this solution. In my department, it is just me using the program. Outside my department, I guess our IT department and our business analysts use it. I know because we are involved in doing some work with the IT department and they use Vizio extensively. I would say there are like five or six business analysts in that area who use it. I guess if you need to scale usage, you buy another license.  

I have not had to contact technical support.  

Before using Visio, we did not use to do a lot of process mapping and our work charts were done in Excel. I was already fairly familiar with Visio, so that is why we got a Vizio. Vizio is a part of the package for the Microsoft suite, but it is an additional cost. So Vizio is not in the standard package but it is a product that is very compatible with familiar components in the Microsoft Office suite.  

The initial setup and installation were easy. It was even less than an hour, I think.  

Visio is about a $180 dollars to purchase. It is a one-time licensing fee.  

The only real comment I have for people thinking of adopting Visio is that it is pretty easy to use if you are looking for this type of solution.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate Vizio as an eight-out-of-ten.  

Mostly, we're using the solution for working with objects and network diagrams and all the charts. I'm the deputy manager of quality assurance and we are customers of Visio. 

Most of the time we're dealing with designation so that feature we find very easy and useful because we have a continuation for the required flow symbols. It also provides access for profile pics for the designation. Sometimes there are other options, such as timelines, that I also use but less often. 

The inventory feature could be improved. On projects, there are sometimes inventory tasks that are lacking. Imagery could also be improved. I'd also like to see increased visibility. 

I've been using this solution for 15 years. 

The stability of the solution improves from version to version, although sometimes it doesn't feel very user friendly. Inserting visual formats creates issues with stability. That aside, it is stable. 

Scalability is good. At the project level, we have supposedly 1,000 users that interact with Visio. It's used extensively. 

I'm satisfied with the technical support. The documentation is reasonable.  

The initial setup was not complex because we had support and Visio assisted us with the deployment although it was actually carried out by our own company. 

The fee is per license and there are no additional costs.  

I'm comfortable using this solution and I would recommend it. 

I would rate this solution an eight out of 10. 

We use the solution mainly for designing purposes. It helps us design activity charts, sequential charts, and other diagrams.

They should improve the solution's customer support service.

We have been using the solution for more than twenty years.

The solution is finely stable.

The solution's customer service team could be well-equipped with the required information.

We used PowerDesigner earlier.

The solution's initial setup is straightforward.

You have to purchase a license to use the solution.

I rate the solution as a six.