Lucidchart Reviews

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.

With respect to documenting processes, Lucidchart has been very helpful, especially for our team in a remote setting. We've tried other platforms and by far, Lucidchart has been the most beneficial to us, especially since it's been integrated into our organization. We're able to work cross-functionally on various projects, even outside of our team.

My impressions of Lucidchart's capabilities for visualizing and understanding process flows have been really good. It's pretty straightforward and Lucidchart does a really good job at simplifying the process flows for the end-user in a very digestible format. You don't need to have a project management background to understand the flows. It comes down to ease of use, and the fact that it can present things in a very digestible format has been very beneficial.

It is important to our organization that Lucidchart accommodates both Mac and PC Users because we have hybrid users who might prefer to use one over the other, or both. Due to the nature of our organization, we definitely have Mac users but for the most part, we use PCs. That said, having Mac users adds a little more credibility.

In our collaborative efforts, people simultaneously access and work on the same version of a document. In addition, we have other team members that are working on various process flows. The real-time updating allows us to drill into documents in real-time, and pick up where people leave off. The related security feature is also very beneficial, as you can prevent users from editing the document if you don't want them to, while at the same time, giving them visibility.

This ability has enhanced our project development process because it allows us to meet and work on the same document in real-time if needed. If there are any takeaways or any additional work that needs to be done on a particular document, the ease of use allows us to do that.

The real-time collaboration capability definitely saves us time. I would estimate that we save at least 15% of the time that it would take otherwise.

The ability for people to look at a diagram, rather than reading through written documents, is another way that we have saved time. It is difficult to estimate how much money this may have saved but we do work at a very visual organization where people prefer diagrams and visuals, rather than written or documented processes. As such, it's definitely saved us time, especially when it comes to explaining what the process is. The visuals definitely help.

Lucidchart helps us to realize efficiencies in the projects that we use it for. We're working on a Workday implementation, and one of the key reasons for using Lucidchart is to make the information that we're passing along to our end-users a little more digestible. By using Lucidchart, we can explain our process flows visually, and this has definitely saved us time.

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 also use LucidSpark, which is another tool that helps with brainstorming. Particularly in my role as an infrastructure manager for the region, I need to work on strategies. There are always a number of challenges, particularly during the transformation stage. I'm required to bring in the right products and the right skills. When I am stuck and face a blank, LucidSpark helps me to move forward.

The functionality for documenting things like processes is excellent. The templates are already available and all you need to do is bring one in and use it. This saves a lot of time and effort in terms of documentation, and you can export it to any format you need. It allows us to give our reports a professional touch.

I have used LucidChart to create a database schema for one of my colleagues. It supports the notations that we use, such as one-to-many, many-to-many, and others. There is support for components such as private keys, foreign keys, and other such definitions. It is something that is easy to do.

In terms of integrations, we use Microsoft teams as our platform for communication and I was able to successfully integrate it with LucidChart. The one limitation with teams is that people have to be comfortable with viewing things on a web browser.

Using this product brings up the wow factor when I present my ideas. I don't have to rely on PowerPoint presentations, which is another skill. The graphical representation also makes it more open to peer contribution and focusing on a problem.

This product has improved our collaboration and we now do it in a much better way. However, we do not yet have several people collaborating on the same version of a document at the same time. For example, earlier today I was working on a project with infrastructure managers from several regions. We were all on a call and I presented my thought process and ideas. I was the only contributor and I shared my screen. Although I was getting opinions from people, I was doing all of the work on the board. Ideally, people would treat it like a working session and do things like putting sticky notes on the board. In the future, having this type of collaboration would be great.

The plan is to let people know that the option for this type of collaboration is available, and have people come forward to contribute. This way, we start thinking and doing transformation on a different scale.

I can see that using LucidChart is going to save us time in project development, collaboration, and brainstorming. I can't estimate exactly how much it will save us without first having a baseline, although I can say that without the tool, ideation would take me approximately five times longer. The time it takes to complete a project has been drastically reduced.

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'm a consultant and a lot of the work that I do is around building the flows. Lucidchart provides the ease of use for building the flows, and then I am able to showcase them in other environments such as Google Slides.

The ability to produce a cool diagram that looks very pretty in a short period of time is the number one asset. I have built process flows. I have created a couple of diagrams for senior executives, and they have been received pretty well. Obviously, they are not very rich because I only started using it a few weeks ago.

It accommodates both Mac and PC users, but because I'm using it in Chrome, to me, it is seamless whether I'm on a Mac or a PC. It supports all the different shortcuts that I would normally expect.

The ability for people to look at a diagram rather than reading through written documents has saved time, and as a result, money, but it is hard to quantify. A picture tells a thousand words, and a lot of my success so far in promoting this is because I've been able to take very wordy slides and transform them into something that is visual. I am able to tell a better story to senior management with visuals rather than just a bunch of text. It helps to turn information that is very textual into a visual component. People are getting the information in a way that they can understand. The fact that you're able to tell a better story and people like it has immeasurable gains.

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

I've been using its web-based version.

It is excellent for documenting things such as processes, systems, etc. We have a guy who is a salaried commission salesperson who was doing very dry due diligence work on real estate deals. I took what he was doing and mapped it out so that a $12 an hour temp person can do it. It is very good for that. It is also good for mapping out things like marketing campaigns to explain to clients. I also run an agency on the side, so having here's what we're going to do and let me visualize it for you has been extremely useful as well.

It is important for us that Lucidchart accommodates both MAC and PC users. We have a mix at our current company, and I have guys who work from an iPad. We're currently in the process of transitioning everyone to MAC. It has been a headache because some of the software products that we can get on a Windows computer are not available for MAC. We're a construction company first and foremost, and a lot of construction software is designed around Windows. Lucid is a huge part of my day-to-day work. I use it almost every day. It is very helpful that it is web-based, and it accommodates both MAC and PC users. 

The ability for people to look at the diagram rather than reading through written documents has absolutely saved so much time, and as a result, money. For our due diligence process, I can't give a written manual to the kind of employee I have for this work and expect that employee to follow it. There's no way. Without Lucidchart, the whole project of having that employee do due diligence kind of dies because I don't have a way to show them that this is how to follow this workflow. If I'm paying somebody $12 an hour, I'm not going to expect them to be proficient at reading a technical manual. That would be a huge learning curve, but almost anyone can read a flow chart. I worked at fast food when I was 16, and I had flow charts on how to do stuff. You can give that to somebody who's very low-skilled and have them working above their skill level. It is a tool for employee growth in a way because you're able to give somebody a task that might be out of their pay grade and grow them into that role because you're able to explain it more simply.

It has definitely helped us in realizing efficiencies in our projects. Just yesterday, I was working on this due diligence project. We buy land, and when we get any land under contract, we have a period of time where we have to go and assess the land and decide if we want to buy it. It seems like you have to be an expert to do it, but it's really following a mental checklist. I got with my guy who does that, and I said, "I need you to tell me every question that you need to be answered in order to tell me if we can buy this land." He was like, "Well, this one, no." I was like, "No, you need to tell me every single question, and we'll get it on the chart." Doing that, I realized that sometimes, he's sending people out to look at stuff that he knows we can't build on. I was like, "They shouldn't be going out to look at that if you know that we can't build on it." That's an employee who is more highly paid than the person is who is going out to look at the land. That person is wasting two to three hours of their time to drive out and look at a lot that may not be buildable. That was just yesterday, and that's going to save us thousands of dollars. That's a huge time saving, which is time and money.

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.

Lucidchart is really useful for mapping out processes, even if you're just trying to think about how to write them out or relay an idea to other people. Being able to draw it out is very helpful.

The organizational charts for visualizing and understanding hierarchies and relationships are very simple to draw out, then share and quickly make edits, according to feedback.

Lucid's capabilities for visualizing and understanding process flows are good, as you can use layering on top of your ideas. There are also so many templates that I can start with, I don't have to start from scratch when trying to visualize the concept. It's very easy and clean to use.

I collaborate with other team members for assessments of clients' customer success teams, playbooks, and education. The ability to do this absolutely makes our process faster, mainly because you can visualize what you're trying to say, so people understand it faster.

I'd say that it cuts the amount of time we spend in half because you don't have to write emails back and forth. You can see what they've changed, even in real-time.

Using this platform has helped me to realize efficiencies because I can visualize what I'm trying to tell the person. Instead of writing it out or taking a long time trying to figure out how to do it in PowerPoint, I can just drag and drop so many different images to convey what I want to say into one page, as opposed to taking multiple pages or wasting time trying to figure out which icon or how to draw something out when they already have templates in there.

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.

Lucidchart's capabilities for understanding workflows is high. I use a couple of different programs, like MindManager, and what I like about using Lucidchart is that it is all web-based. So, I can quickly go into a web browser, drag and drop a bunch of files, pictures, or notes, draw some flow lines, and rapidly be able to create a visual representation of what I am trying to do. As a product manager, I can quickly organize thoughts that way and show people what we are working on.

I do more show and tell with it. We don't really collaborate too much. We are mostly just sending, "Here is where we are right now with this." We don't really collaborate on the same document, which I know could be a really powerful function. We just don't use it that way yet. 

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.

It's filling a gap where we can better visualize our engineering processes and architectures within our Atlassian tools.

It provides real-time collaboration among users so that everyone is accessing and working on the same version of a document. Although we rarely use it in that way. Unlike sharing a spreadsheet that is being filled in by multiple people or something like that, usually editing diagrams isn't something we're doing at the same time.

It hasn't affected our project development process. For other tools, having simultaneous collaborative access is great, but for diagramming, it wasn't really a necessity for us. And I think that is mostly because we access Lucidcharts through a plugin, through Confluence, as opposed to logging into Lucid and then using that as a primary tool.

The ability for people to look at a diagram rather than reading through documents has saved time. They can look at a diagram to better understand something as opposed to reading words. That's kind of an abstract idea. I can't put up a price tag on it. There are probably tens of hours saved on managing the ERD diagrams and specifics since the automation is there for that.

It helped us to realize efficiencies in our projects.

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

I'm able to create a mock-up and then share that with a person on the other side of the world for his or her review and commentary. We're then able to easily understand how the mock-up or flow should work, based on sharing and using Lucidchart and the commenting back and forth between people.

The real-time collaboration among users, so that everyone is accessing and working on the same version of a document, has made it more efficient for multiple users within our organization to review the same mock-up or wireframes simultaneously, and comment on them to enhance or improve them. The real-time collaboration has saved us hours of time per week.

We also use the solution’s ability to compare versions of documents. It's important to understand who, on the team, is responsible or has version control. In sharing wireframes or mock-ups, referring back to previous versions or iterations has been helpful to understand how things have progressed to the current state. This feature is important to understand how a document or flowchart has continued to improve.

The ability for people to look at a diagram, rather than reading through written documents, has saved time and money, but at this point it's hard to put a dollar figure on it. 

An example of the kind of efficiencies it provides in projects is that it has saved us time in reviewing a mock-up for a mobile app. Being able to share those mock-ups back and forth between our product and development teams ensured that the mock-up was meeting the desired end-state. It probably saved us a day, eight hour's worth of time, over the course of the last two or three months.