I would rate the scalability 8 out of 10.

The solution can scale well. Currently, we have 400 users on Visio. We likely will double users in the coming year. 

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've never heard of any concerns regarding scalability. 

I can't say a thing about scalability. 

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.

In my experience, Visio is highly scalable. I've used it within an organization that utilizes Microsoft OneDrive and Teams for their operations. This allowed for easy integration of Visio with the organization's existing Microsoft software and made it simple to share diagrams and visualizations with anyone in the company, regardless of their position or location within the organization.

We have approximately 1,000 people using the solution in the branch of the company I am working in.

It's a one-to-one application. I don't think there's a need to scale. It's expensive to deploy too many seats, especially if people only need it a few times a year. 

The solution can scale. I'd rate the scalability seven out of ten. It could be a bit more scalable. 

We have 4,000 to 5,000 users on the solution.

We have approximately 10 people using this solution in solution.

I rate the scalability of Visio a nine out of ten.

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.

I don't have any input on that. In terms of the number of users, we probably have a couple of hundreds of users of Visio. They are from the IT and the infrastructure side. We have Applications users and Human Resources users. We have a manufacturing organization, so we have program managers who manage various customer products, and they use it as well.

It is used fairly extensively throughout the organization. Our usage is okay for now, but we're always one acquisition away from that going out the window.

Scalability is not applicable.

It is a scalable solution.

In my company, 48 people use the product.

I rate the tool’s scalability a six out of ten. I do not need to scale it much.

Visio is a scalable solution. We have around 20-25 users for the tool.

In terms of scalability, Visio is single user, right? There's no challenge in terms of scalability.

It's open for everybody. It's a part of a package that we negotiated as a part of our licensing agreement with Microsoft. It's available to more or less all the users.

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. 

Scalability is fine. It runs on each individual client. I haven't used any of the team integration hooks. We have a lot of technologists that use it and we're trying to make a move to move those architecture diagrams to be more driven by code by leveraging C4 and then model driven design through MagicDraw and that's a new journey for us. I think there are still going to be a large number of teams that still end up using Visio as it's very versatile. 

It is easy to scale this solution.

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

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

We have 30 Visio users in our organization, but soon, we will roll out the product for about 200 users. It is scalable.

Scalability is okay. It's like everything else, most people they use at most, 30% of the product's capabilities, so there's a lot of stuff in Visio that doesn't necessarily get used. You don't know that when you do the typical installation, that a good part of the product capabilities are never going to get used. The default configuration is to load everything, as opposed to custom, and it's just easier just to let it deploy everything. As a result of that, there's a lot of functionality that gets pulled in, and memory and CPU that may be consumed that the user would never benefit from. That's just the nature of the beast.

I give the scalability an eight out of ten.

It scales, but there is a limit. There is only so much that you can do with the nature of it.

We don't have any intentions to increase its usage, but it is used as a standard tool.

I believe Visio is scalable.

The scalability could be better for the cloud version.

I rate the scalability of Visio a six out of ten.

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.

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. 

It is used to buy a single user at a time because it is meant to be client-side software, so scalability does not apply to it.

For my company, we have around one hundred licenses.

I don't know what the license cost is, but we are not planning to extend the usage of the solution in our company.

Visio is not as scalable as other tools due to the proprietary restriction. You cannot customize it or scale it up like the way you do with Trello or Jira. Microsoft places restrictions on things that you can do with Visio.

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.

I haven't seen any issues from a scalability perspective. 

The solution is easy to scale.

We currently have around 20 users.

The solution is scalable and flexible.

We have approximately 15 people using the solution.

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.

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.

I'm just a small consulting firm. Basically, it's just me and a group of trusted subcontractors that I network with across the country. The biggest project and the biggest team of people I've ever had on a project is 25.

We don't have enterprises that we deploy to. We just put it all on our computers or on our laptops and that's it.

There are no scalability issues. We are a nationwide company, and there are around 5,000 users.

The product is only scalable if utilized with additional software.

Of course the solution is scalable. This depends on how a person designs his infrastructure and if he makes use of his work solutions.

For my use case, there's not much need to scale it up in any meaningful sense. When I'm writing a proposal or preparing a report for a client, I try only to put in a sufficient number or well-considered graphics to get my point across.

I typically create my graphics and place them in a Word document. And then I hope they stay together as I move things around during the editing and review processes. Sometimes they do, sometimes they don't. So, in terms of scalability and accuracy, Microsoft could improve integration and consistency between their Office applications.

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.

If they allowed cloud deployments, you could scale it laterally or vertically.

When it comes to scalability, I suppose that Visio is like any other product. One of the drawbacks of any Office product is its design for a single person. There exist ones on the web which allow for online editing in Excel, but many of the features I use do not exist in this version. This is a pain point.

We are talking about a one-person product, but the fact that you can print it off as a PDF and share it with others is a good feature of it. Visio differs from a real modeling tool, an expensive one such as, say... erwin Data Modeler, in that the latter has its own repository for storing models, which another person can access and use for modifying the relevant model. The model can be split into an overall one and a subject area. This way, two people can work in different subject areas. As long as two people are not working on the exact same object they will avoid stepping on each other's toes. Visio is akin to any other Office products, in that it involves a single person at a time per document.

From my clients' perspective, it's really scalable. It can be used in any type of company. I think it's really useful for any person that is working for a company with a wide range of processes. I'm the only person in my company who uses it and I'll continue to do so because it's so user friendly. 

I haven't pushed the limits of Visio. For what I have used it for, it has been able to handle everything I've thrown at it.

There were some scalability issues. While new shapes can be added, there is still the issue with compatibility problems with other versions of the Visio software.

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.

The scalability could be improved. When I was in school, it wasn't possible to collaborate with others. 

We have had no problems with scalability.

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.

The scalability is average. It's not as scalable as other options. Organizations that need to expand it may run into issues.

We have about five to ten users on the solution at our company.

I'm sure Visio is very scalable. From my personal use, I've had absolutely no issues with scalability. I'm able to go on and develop complex processes. 

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.  

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

Visio is scalable.

The solution is scalable. We're a global company although I'm not sure how many in the company use this product on a regular basis. 

Every group in my organization can use Visio and approximately 150 people use it. It is a tool that design engineers and architects teams use most. We have approximately 150 people that use it.

Visio is a scalable solution. Around ten users, including the major project manager and their colleagues, use Visio in our organization.

The scalability has limitations. It could not model large sets of entities. 200 is probably a reasonable limit.

There were no scalability issues experienced.

The solution is quite scalable, and great to use for any project of any size or scope.

It's easy to scale. We have not implemented permissions so that may be more complicated. 

This solution would be more scalable with this inclusion of additional features.

We have around 12 Visio users in our organization.

I don't think scalability is particularly relevant to this product as I use it.

It's a scalable product.

I find that it's very scalable from a small organization to a large organization.

This product is a desktop application, but coupled with SharePoint, it allows for concurrent editing of files without any issues.

This is an area that we did not explore as it was not necessary for us to scale. It was not a requirement.

We had 10 customers using this solution.

We don't have plans to increase our usage. I am with a different company.

Given that it's a desktop application, you can't scale it. You can't do much and sometimes, sharing is an issue.

The product is highly scalable for the design.

The solution is scalable. 

Not too many people use the solution in our organization.

In companies where I have worked, its adoption rate among people in similar job functions to mine is often left to the individual. Some may be more comfortable using other solutions (Adobe Acrobat, AutoCAD). I have not seen the Visio product ever rolled out across an entire company's engineering staff. However, I suppose that this could happen.

It is scalable. We are a small organization. We are a part of a startup, and there are about five to seven users who use it, which is not a big number, but it is enough for us. Architects and web designers are some of the users of this solution.

Visio is a scalable product. We have perhaps 300 users in the company.

There were no scalability issues.

We have around ten users from IT, engineering, and HR. HR uses it for flow charts or organization charts.

The solution is scalable.

I have found Visio to be scalable.