TrustRadius Insights for Microsoft Visio are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Ease of Use: Users have consistently praised the ease with which they can create professional-looking diagrams and charts in Visio. The intuitive interface and user-friendly tools make designing efficient and straightforward for a wide range of users.
Grid Layout Assistance: Some users find the presence of a grid in Visio to be highly beneficial, as it simplifies the layout process and aids in aligning elements precisely. This feature contributes to creating visually appealing diagrams with ease.
Seamless Integration with Microsoft Products: Many customers value Visio's seamless integration with other Microsoft products, such as Word and Excel. This integration not only streamlines workflow but also enhances collaboration by allowing for easy sharing and editing across different platforms.
Documentation of existing networks and network upgrades/modifications that occur at corporate and remote locations. These include rack layouts, floor diagrams, power and wiring layouts and geographical location specifics to assist technical team members understand work efforts that need to be delivered for the project on the "big picture" and detailed level.
Pros
The rack elevations and placement of components
The cross connect capabilities of components
The additional notation details that can be added
Addind specific images if needed for clarity
Layered linking to other pages
Cons
Integrated coding or scripting for object for basic config notes
Integration notes for implementation ticketing
Integration with project management
Likelihood to Recommend
As a standalone product it works pretty well, finding additional add in stencils takes a little more work. Once the libraries are built and exceptions noted it works well. It would work better if it could query devices and pull some info out as a starting point, but I have not found that magic bullet yet.
VU
Verified User
Consultant in Information Technology (1-10 employees)
We use Microsoft Visio in our organization for multiple purposes, we draw new network diagrams, or modify existing ones with new updates. We also create traffic flow diagrams for in house applications, or on cloud apps, this allows the teams to have knowledge of dependencies of the applications and the network TCP/UDP ports used per application. We have many scopes for Microsoft Visio since it allows to use it internally and for customer deliverables as well. The problems it solves is definitely the gap of knowledge to understand how things are designed, work together and also micro application communication and dependencies.
Pros
Allows for Multi-vendor product stencils to be used and create a physical diagram
Allows for rack layouts to be created in detailed.
It works online now, so you can update one diagram and it keeps the version updated.
Allows to create connection points in a stencil so you can draw and connect multiple devices to it.
Allows for flow diagrams
Cons
More flexibility like apps draw.io online
Connection points need to be created manually while other apps do it automatically in the stencil.
Stencil upload manual process, while it would be better to exist an online menu of stencils,
Uploading a diagram from draw.io to Visio breaks the original diagram
Likelihood to Recommend
Well Suited: - Corporate level diagrams such as network, data base, applications. - Deliverable to customers that also have Microsoft Visio. - Internal on-premise documentation of physical network, or physical data center, rack layouts.
Less appropriate: - When the customer uses an online tool for diagraming, and they need a draw that stays consistent, - Convert Visio diagrams to other tools extension. - Online Rack layouts.
There are two primary tasks that we use Visio for in our Orgnaization. First, we use it to Value Stream Map the processes at each of warehouses every 18 months. From this Value Stream Map we create in Visio, we will then develop our Contiuous Improvement Roadmap.
We also use Visio to create Swin Lanes for new processes and projects that are rolled out in our network to give our users a good visual representation of what they will be doing and how the process should flow.
Pros
Built in templates to do Swim Lanes for new processes.
Built in templates to do Value Stream Mapping Sessions.
All of the shapes need to build out detail process maps for new or updated processes.
Cons
Using the arrow shape to connect boxes sometimes does not follow the direction you are trying to make it go.
Coverting to a PDF for non-Visio users sometimes cuts off key pieces of the process map.
It would be nice to see more native integration with the rest of Office 365.
Likelihood to Recommend
Visio is by far and away the best tool that I have used to do Value Stream Mapping sessions with the warehouse I support. It has all of the shapes needed built in to be able to represent all areas of the processes. I also like how you are able to make the drawing as big as needed and when printing it out of Visio you have the ability to use the necessary paper size.
The biggest complaint that I have with the software if how it can be cumbersome for non-Visio users (that is, people without a license in the orgnaization) to interact with the Visio Map. We normally have to dedicate one Visio SME to be able to make the changes that Process SME's find since they do not have access to the software.
VU
Verified User
Engineer in Professional Services (1001-5000 employees)
Visio is a tool that help me to model business processes and communicate efficiently my ideas and solutions to my colleagues. I create many diagrams for architecture meetings and for development documentation. The creation of diagrams is fast and easy, I always find the icons for any required diagram.The creation of mental maps and ideas is really easy and useful for my daily activities. Actually, many times I create diagrams to clarify my ideas by using mental maps.
Pros
Mental maps for new ideas
Architecture diagrams for cloud deployments
Class component diagrams
Cons
Some icons for cloud diagrams are not easy to find
Likelihood to Recommend
Diagrams for architecture meetings, technical documentation. Class component diagrams. Mental maps. Data flow diagrams. Draft ideas.
Now appropriate for complex graphs such as social networks connections or origin-destination matrix.
Need to visually show clients their existing solutions and the solutions that we recommend for them. Helps to present technical setups so that the proposals are easier to understand. Mostly used to help sell technical solutions.
Pros
Integrates well with Office apps
Lots of variety for icons/symbols
Easy to use
Cons
Have a Mac version
Stop auto-connecting lines when drawing
Too hard to select groups of icons. used to be easier with older versions
Likelihood to Recommend
Well suited for laying out diagrams of IT solutions. Not well suited for drawing org charts
We use Microsoft Visio mainly as a process mapping tool, creating mostly cross-functional swim lane diagrams for discrete processes or application integrations. Through the use of templating and agreed shapes and other artefacts, Microsoft Visio is used to create a large portion of the training material and system analysis documentation before development and deployment.
Pros
Templating
Cross-functional swim lane diagrams
PDF creation
Process mapping
Training materials
Cons
Infinity board (e.g Miro or Lucid)
Training seminars
Collaboration (e.g Miro or Lucid)
Likelihood to Recommend
Understanding and then documenting a business process or system integration. Analysing a process for single points of failure. Creating contextual diagrams to visualise how multi system architectures work. Producing training materials to allow those unfamiliar with a system or process to quickly understand it. Creating organisational templates for process diagrams.
Microsoft Visio was long the go-to tool for architecture diagrams. I invested significant time creating stencils of my most frequently used icons and logos, which became a standard adopted by colleagues. For me, one of Visio’s key strengths was the ability to define and distribute standards through reusable templates and shareable stencils. Over time, however, it became increasingly difficult to ensure everyone had the appropriate licensing, and even more challenging to maintain consistent usage across the organization. In addition, while Visio can produce very clean diagrams, it can be somewhat finicky; the quality of the final output is often directly proportional to the time and attention the author invests. Visio also isn’t well-suited to “live” diagramming during meetings and offers limited support for real-time collaboration. This summary reflects my personal opinion only and does not represent my company's views.
Pros
Clean diagrams.
Easily shared through email.
Editable by the receiver.
Generally accepted as a standard.
Cons
Finicky, quality of the result proportional to time and care invested.
Large files become unstable.
Not good for collaboration (internal or external).
Likelihood to Recommend
If I wanted to produce best-in-class deliverables, particularly for an external-facing document where presentation quality matters, I would use Visio. For an organization that wants to standardize and ensure consistent deliverables across teams, I consider Visio a strong option. However, if I need a quick illustration of a process flow or architecture, I would use another tool to avoid spending more time than necessary.
We use Visio for creating network design diagrams and flowcharts for planning projects and operations. It helps organize processes and represent planning in a concise graphical presentation.
Pros
Diagram process flow.
Diagram network layout.
Graphically represent project progression.
Cons
For our use cases we don't see any issues needing improvement at this time.
Likelihood to Recommend
I am not sure how others are applying Visio to their needs. For my firm, we use Visio regularly, but only for very specific needs, which it fulfills perfectly. These would be flowcharting and network diagramming.
VU
Verified User
Engineer in Information Technology (11-50 employees)
I am part of an engineering development team that uses Microsoft Visio for system and use case modelling.
Pros
Clean modeling design
Good exporting functionality
Easy to pick up and use
Cons
Collaboration between multiple team members
Visio diagram navigation
AI incorporation for diagramming assistance
Likelihood to Recommend
Microsoft Visio is a great, simple, tool for diagramming algorithm flows and systems states for a team that is designing software algorithms or larger systems. We have used it for everything from use case diagrams to system diagrams.