I am the regional infrastructure manager, heading the entire IT infrastructure for my company. We are headquartered in Belgium and I work with a subsidiary in India, where we have 23 locations. My job includes taking care of all of the infrastructure-related activities. These are operational and project-related activities pertaining to network security and cloud-based solutions.

I use LucidChart as a brainstorming tool. It helps to ideate the organizational structure and anything to do with workflows and architecture. For example, when something new comes up, I turn to the platform to help with brainstorming and ideation, and it has helped to a great extent.

We use it as a mind map tool, for decision-making workflows, and technical workflows. There are multiple reasons that we utilize it, depending on the use case.

I have been using Lucidchart for process flows and diagrams of our business processes for a system that we've implemented called Workday. We have been building out our process flows to communicate them to our end users in a more digestible format.

It is used on the technology side of the business in several departments, including the help desk, service center, and others.

I create visuals for executive management, and I use it for business process flows. I have also started integrating it with Google Sheets so that I can pull different records from Google Sheet into a whiteboarding session. I am taking table data and making it prettier by having it integrated into a Lucidchart that reads those records. I've also used it for planners.

It is a cloud solution, so we are using its latest version.

I use Lucidchart for creating journey maps and educating customer success managers on best practices when it comes to managing customers, relationships, and difficult conversations. 

People are visual, so I typically try to visualize what I'm trying to say and Lucidchart makes it easy.

As a Mac user, and with most people in the area using a Mac, it is important to me that Lucidchart accommodates both platforms.

I was previously using whatever was on the web, but we have a plugin for our Atlassian tools, like Confluence, where we can integrate Lucidchart diagrams into our Atlassian tools as well. 

Previously, I was using my own personal cloud subscription, but then I stopped doing that. Once we had integrated it into our Atlassian suite, there was a plugin for Lucidchart and we had licensed the plugin. And so we would use the plugin that when we would add that type of graph, it would take us to the external website for configuring our diagrams, and then we could exit back and it would render the diagram in our Atlassian solution.

Lucidchart subset their older components or something like that had happened. I don't entirely know the totality of it, but we were forced to upgrade to a different integration with Lucid than what we had. I've had a lot of frustrations with that because I've lost a lot of diagrams. I can't get them back and I'm getting pop-ups that are showing me that our data will be loading and I can't run four or five years of my engineering diagrams. I'm extremely angry about that. I can say that all the time I've had this thing is making me leery to using the plugin, let alone rather just use the tool independently and copy-paste pictures because when the plugin fails to work and you don't have an image to fall back on, you could lose years of work.

I have that as a real big sore point and I can't figure out what, why, or how, and there's not really a good clear point of context to figure out how I address recovering all the lost work I have or how to migrate it.

I had massive engineering, ERD diagrams, database diagrams, architectural diagrams, you name it for years. And a lot of the documentation I had in Confluence, including system architecture documents for our products. I can't get those assets back.

My primary use case was for data entity-relationship diagrams for UML. It shows the engineering, architecture documents, using UML and the general flowcharts, and swim lanes for process swim lanes. I do tons of processes and swim lanes. I'd say those are really the four things I usually do with it.

There are a few different things. The main one, obviously, is creating business workflows. 

I've been using its web-based version.

I do a lot of strategy stuff with it:

1. Mapping things out that way. 
2. Laying out product plans and roadmaps.
3. Visually showing people some of that information.

I use it for general mapping, more like a canvas. I'm a single user who uses it for our company for a very specific need.

We are using Lucidchart through the web.

I was using Lucidchart to design charts and diagrams. One of my tasks was to design an organizational flow chart.

I worked as a business analyst before, and now, I am a consultant. I am mostly using it for data flow diagrams and process flow diagrams. I don't constrain myself to just CAD diagrams. I also create ad-hoc charts and diagrams for Apex user stories and things like that.

I am using the web-based application of Lucidchart.

I have used Lucidchart for many things, but the biggest piece that ended up generating the most work was process mapping. 

I have done Kanban charts. I've used it for organizational charts. I've even used it for describing business entities to describe relationship management, which isn't necessarily a process. 

I used Lucidchart because I had to create an accountability chart. We use an operating system called EOS, which is Entrepreneurial Operating System and I was tasked with assigning a seat for every role that's necessary to run an organization properly. Starting at the very top with what's called our visionary, which is really the CEO, and then my seat, which is the COO and I'm the integrator. From there, I had to divide it into departments and department heads and then the different roles each person plays within each department.

We use Lucidchart for our sales team. It displays what our sales flow should look like from start to finish once we contact the customer, all the way through closing out a sale. It displays the whole process.

I use it to filter data and create data models for applications.

We are in the starting phase. We are going step-by-step. We have just created our data diagram, and there is not much collaboration on this part. When we go to our architecture diagram, we will be having more collaboration.

I have used it for technical purposes and support.

I am still exploring the tool.

We use it for making flowcharts. We are using the iOS and PC views to make mock-ups and wireframes.

I've used Lucidchart much more on a personal project than at work, just by coincidence. Mainly at work, we've used it to create a very simple diagram chart, some squares, some circles, and arrows connecting them. It's for HR purposes. I work in human resources. We basically map out the process that a candidate goes through when they're hired in the company. We made some squares saying all the steps that need to be done to onboard someone and we connected them with some arrows and made a flow chart.

On the other hand, I've actually used it very extensively for a personal project of mine, which is a video game. Since I'm developing a video game, I'm using Lucidcharts to organize all the different pieces of the game, including the levels, the maps, and how they all interact with each other. That's also basically a giant flow chart and diagram with loads of connecting pieces.

I'm using their web-based application. I've just come off the free trial, so I'm a very new user.

We use it for the organizational charts and for documenting new teams. We'll probably use it for processing systems at some point.

I would rate Lucidchart a seven out of ten for documenting things like new teams. I'd give it this rating purely because I don't know all the features yet.

Primarily, since I'm a solution engineer, I use it to create mock-ups of ideas for building out demo instances; what they should look like based on what we currently have in inventory. I take screenshots, throw them in there, and do all the diagramming. That is not my core responsibility, but it's one of things I am responsible for. I use Lucidchart to build out those mock-ups and to collaborate with the team so that they can have input on the layout, how things should look, and on behind-the-scenes processes.

We use Lucidchart for building business presentations and business flows and explaining processes to stakeholders.

I am using its web-based version.

I've been using Lucidchart to create process flow charts. I've been using the shapes, swimlanes, and arrows. I haven't really been doing anything too formal, but it definitely has a lot of value for our team.

I only use the diagrams. I don't really use all of the features.

I mostly use Lucidchart to describe projects, processes, process descriptions, and project flows. I also use it for mind mapping a little bit. I cannot imagine working on a presentation for my manager without using Lucidchart. It's handy. It enables me to clear my mind in terms of how the process should look, what the necessary steps are, what the flow should be, how the flow should look, and all the beautiful stuff.

My company is a solution provider and I primarily use Lucidchart to create workflows for my clients, to show them how a product is going to work. It helps us to create a pre-sales demo of what our solution for them is supposed to look like.

I use Lucidchart to document things such as business requirements, as well as entity-relationship diagrams to see exactly what the schema of their solution is supposed to look like.

Essentially, everything I do with Lucidchart is part of the requirements for making a presentation to the client.

In this company, we are using Lucidchart as a mechanism for whiteboarding and creating flow diagrams, charts, and any other things that are required for my day-to-day work. I use Lucidchart in my company and I used it in my previous job, as well.

I work mostly as a business analyst, in a product owner role. I have to build up the requirements, convert them into charts, and explain everything to the business owners.

The Lucidchart platform is where I use graphics to create pictorial descriptions, which is better than using simple words. It is a very effective tool for documenting processes and using it has improved our efficiency significantly.

Primarily, we have been using it for collaborating with other team members and documenting the work that we are doing as a team and organization. Its two main functions are to document and collaborate. 

We are mainly using it for flow charts, organization charts, and process flows. In terms of deployment, we have a subscription for it. It has a login and a password, and we have to log in.

I've been using Lucidchart for process mapping and creating organograms. Primarily surface researchers use it. We're setting up a new service and that's what we're using it for.

We primarily use it for process improvement in a factory setting. What I am primarily using it for is making process flow diagrams—with the rectangles, circles, diamonds, arrows, and whatever else you would build into a process flow. 

We've had discussions about using it to build engineering-type stuff, as well. For example, "Here's the room, here are the dimensions. Here's what it would look like if we moved this piece of equipment, what space it would open up. Here are other constraints or barriers that it might create." We've had discussions on that, but we haven't really delved into that yet. 

I have the web-based for my laptop, and I have the app downloaded on my iPad Air. I've been using it on both of them.

Our primary use case is to document processes in the business organization.

I use it for the WBS tree diagram, the work breakdown structure, and for divisional workflow mapping. I also use it for whiteboarding sessions with my team. And I have used it for an operational requirements matrix. Our company has used it for making a company organizational chart.

I am an engineering student at college and I was using Lucidchart for a research project. I was using it to create flow diagrams.

We use Lucidchart for the lateral flow charts.

We use the data models. We create technical architecture and system architecture, usually for technical diagrams that we need processed.

We use it for primarily for two things:

1. Website architecture design.
2. Process flow diagrams.

Most of our company's designers and I are on Macs along with a few other Mac users, then everybody else is on Windows machines. I also have a Windows machine, so it has to work on both.

Professionally, I am involved in marketing and I use Lucidchart to create campaign flowcharts. One of the specific things I do is create process workflows.

I am primarily using it to draw org charts but I also use it to create flow charts.

My goal is to make sure that my org charts are presentable, and that they look great.

A lot of people in my company are using it for mapping processes.

We use it for mapping sales processes and product management processes. We look at a product and map it, including how we interface it through the product life cycle. Personally, I use it a couple of hours a day for project process mapping work.

I am using Lucidchart to help me with learning about flowcharting and workflows. Essentially, I was creating flowcharts.

My primary use case is for drawing technical diagrams.

I'm an engineer so I create process diagrams. 

It is mainly for sales and business development. We use it for account mapping. If we have a target account, we want to know who the key players are. They include the decision-makers, individual contributors, etc. We map this information out on Lucidchart.

We are probably using the latest version. They're pretty good about that. In terms of deployment, it might be SaaS.

As a product manager, I often use these infinite canvases for coming up with ideas and  for brainstorming. I also use it for defining workflows of new products or features that we are brainstorming on.

Now that remote working has become so prominent, these types of tools come in handy when you are collaborating with a lot of folks and you need their input quickly, in a manner that is manageable. That is where I have used Lucidchart.

It's a SaaS-based service, through the browser. Things are automatically saved over the cloud.

I started using it for projects that I have to deliver at university. I see it more as a collaboration tool where you can create things, present them, and you can do idea maps. For me, it's mostly a graphics tool. If I had to present something that represents a hierarchy or a process, I could use it as well.

I am using it for a wide range of diagrams for network configuration, process flow, etc. I am using its web version.

I used Lucidchart to build-out items such as business org charts, business processes/workflows, and product diagrams.

Lucidchart is much better than competitors that I have used, such as Visio. I am able to easily save off charts I have created in a PDF document, which is primarily what I do.

The flexibility of Lucidchart is great. It is easy to create swim lane process documents with as many rows as you would like. It is also very easy to include columns into the swim lane that allows you to show where one process ends and another picks up. This feature has allowed me to generate very detailed process documents that my employers have loved. 

I am using it to create a process document showing a process flow with a timeline.

I'm using the web version.

I make the domain-driven designs (DDDs) for my teammates as well as ER diagrams (ERDs).

I usually use Lucidchart with my work for some idea improvements or brainstorming.

I have two main use cases. I am an IT architect, so I'm drawing IT architecture with Lucidchart. The second use case is that I'm using it to build some business models to describe my customers in a single slide.

It's a SaaS solution.

I'm a software engineer and one of my tasks is to design a system for how data will flow and how things will be organized. That's what made me start using the solution. If I go one step deeper into this project, I will need to make database-specific diagrams, including class entity and relationships diagrams.

I use it whenever I have to start any new project, any new REST API, any new system design, or microservices. That's when Lucidchart is the primary tool to work with.

Lucidchart is a SaaS-based solution.

Our primary use case of this solution is to create some process flows, namely how the user will use the product, how they will walk through the product, etc. We don't use the program very often - only once every week or so.

I used Lucidchart to design flowcharts for my APIs. 

I primarily use Lucidchart for mobile app development.

Our use cases have been mostly for software development. We use it to integrate software and for processes, like representing different business processes.