Lucidchart Reviews

We use Lucidchart for the lateral flow charts.

I've used Lucidchart for a status report. I gave it a particular format and was able to set it up in minutes.

It's fairly intuitive. It has a fairly low learning curve. The only tricky part, and it's only because I have not spent time on it, is some of the formatting. They should enhance the help section on the formatting.

When it comes to documenting things like processes, systems, and new teams, I'd give it an eight or nine out of ten. It's very high because it's fairly intuitive, there's a low learning curve, and it's easy to get immediate output. You can get results very quickly without a lot of direct effort. You don't usually take a week-long series of training. You don't need to go through a lot of hoops to make it work.

I would also rate Lucidchart's capabilities for visualizing and understanding process flows or workflows a nine or ten out of ten. It's much easier to use than Visio.

I plan to use Lucidchart to create database schemas or modify existing data structures. That's the next step, but I'm still at the beginner's level.

We have used Lucidchart in real-time collaboration among users. The solid collaboration has saved us time.

I have received good feedback about its ability for people to look at the diagram rather than reading through written documents.

Lucidchart has helped us realize efficiencies in the projects we use it for. I did use it for a status report. It saved emails, but I can't quantify how many emails we would have sent.

The main improvement I would like to see is for them to improve the help section on the flow charts or on the formatting.

I've only been using Lucidchart for a few months. I use the web-based application.

It's highly available. Once you have all the users on the same licenses, it's very available.

All of us are in the project. There are multiple users.

I have not actually had to call up support yet, which is a good sign. I haven't really had any calls with them.

We used PowerPoint, Word, and templates. It seems like Lucidchart is the most intuitive out of the entire set. 

The intuitiveness is the main difference. The ability to get to see it very quickly seems to be the big advantage for Lucidchart.

The initial setup was very straightforward, except for the formatting. It took a little bit more to try to add bullets or anything to touch it up.

My advice would be to give it at least a good hour to try it before you make any decisions. It shouldn't take that long, but if you put in effort for an hour, I think that you will get immediate results to see the benefits.

A nice thing is that this platform's very forgiving, so I would say to learn to experiment.

Overall, I like it. I just need to find some dedicated time to learn some of the nuances of using the tool. 

I would rate Lucidchart an eight out of ten. 

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.

The process mapping has improved my organization. It would have looked very messy to do it on Google Docs. We wouldn't have been able to cover such a range of things in our process mapping. We've managed to get in rows for different organizations and how they fit into the process mapping. We just wouldn't have been able to have space for that using Google Docs and it would have taken so long with the formatting.

It saves us about two hours. It only took us about an hour doing it on Lucidchart, so it probably would have taken about two and a half hours on Google Docs.

We use it to collaborate among users in real-time so that everyone is accessing and working on the same version of a document. It has been great for our project development process. In a way that's similar to Google. It's not that new for us, because we use G Suite throughout our whole organization. So we expect things to be able to do that because we do that a lot where we're all working on the same document at once. But in the same way that it does G Suite, it's really useful. It would be a real big drawback if we couldn't do that because you have to get the Word document, then you save your changes, then you send it back. It saves a lot of time being able to do it at the same time as someone else.

It's not necessarily saving time, but more saving the admin from sending it back and forth and trying to make sure that we're working on it at separate times. It probably would have taken us the same amount of time. It's more the ease of doing it.

It's hard to say whether it's saved money. It's definitely saved time. If you tried to put a process map in writing, I don't think anyone would read it. I don't know if it would save time and money, because no one would even look at it.

I've been using Lucidchart for quite simple things, but it's definitely much easier making process maps using Lucidchart than it is using Google Docs for basically everything. It's much simpler in terms of how easy it is to use Lucidchart. The way that you can get the arrows on the flow charts, based on the process mapping, you can drag the arrows from one box to another and it automatically shows you where you can put it. It makes decisions for you in terms of if you have a decision diamond, then the line is automatically a yes or no. This just makes it so much easier.

I use Lucidchart to document process workflows. We're setting up a new service. So we needed to map how the old service worked, as the exact processes of the old service, and then map how we want the new service to look.

Its capabilities for visualizing and understanding these types of workflows are really good. It's been really easy in the way that when you do a Google Doc, it's all about if it will fit on the page if you're doing a process map or something like that. Whereas Lucidchart, you can make it as big as you want, but then still when you convert it to a PDF, it will all be on one page and then you can send that PDF to people. I found that really useful.

We integrate it with G Suite. Its ability to do so is definitely important. At the moment, that's been fine, because we link it when we're doing a Google Doc, for example, and we have it find the process map and then we would just link into the Lucidchart there. As long as we can do that, I don't think that would be a problem for us. But we'd want it so that when people open Lucidchart if we were sending a paper saying, "This is how our service is going to look. Please see here," and we've linked in the Lucidchart, we would want it so that when they open the Lucidchart, it's a final copy and it doesn't come up with where it says shapes and it has all the editing toolbars. We would want it to just link to a copy of the actual process map.

It's important to us that Lucidchart accommodates both Mac and PC because in our organization, since COVID, most people are using different types of computers. Our whole organization uses Chromebooks, but some people prefer to use their personal laptops for work. For example, my personal laptop now is a Macbook, so I would need to be able to access it when I'm at work, which is on a Chromebook, and also when I'm at home using my personal laptop for work.

Lucidchart has been pretty good. I've never used it before. I didn't read any instructions on how to use it, but I still just managed to pick it up. Anyone who's generally computer savvy would be able to just pick up to use it very quickly. Maybe it would be useful for people who don't process maps not that much to where it says containers and shapes. There is diamond, round and rectangle, maybe it could be explained in brackets that that's used for in-process mapping and flow charts.

One of the issues has been that, as far as I understand, even to view it, the other person needs a Lucidchart account unless you send them a PDF. That's been a bit of an issue because some people in our organization don't have Lucidchart accounts, only certain people have logins. If we just want to collect comments from people, that's been a bit complicated.

You can't put comments into a PDF that easily. We'd want them to be able to open it on Lucidchart without having to have an account themselves and then put comments for us and be able to tag us in comments and things.

That's not possible to do now, at least in a simple way that we've been able to tell. We've had people emailing back saying, "I need my Lucidchart login. I don't know what this is."

I have been using Lucidchart for around two months. 

Web-based is much better because I'm using my personal laptop for work and loads of people are during COVID. I would never want to be downloading lots of applications onto my laptop. The fact that I can just open it in Google Chrome makes it much more accessible to me.

The initial setup was really straightforward. I've never used it before and I didn't read any of the instructions. Someone just said, "We use Lucidchart for process mapping." So I clicked on it, made my account, and then it was just intuitive. I didn't need to do anything. I didn't need to learn or anything.

I can only comment on process mapping and organograms because that's the only thing I've used it for. But I would definitely recommend using Lucidchart for this.

I would rate it a nine out of ten. 

My primary use case is for drawing technical diagrams.

I'm an engineer so I create process diagrams. 

Before we had people on Visio and Lucidchart. Now we still have some people on Visio and we can seamlessly trade Visios between machines. I anticipate that we're all going to Lucidchart.

Lucidchart provides real-time collaboration among users so that everyone is accessing and working on the same version of a document. Most of what we do is document our platform and then change it to show what it would look like in the customer's world. We're a cloud company, and our customers want to know how they connect to our cloud. We changed those diagrams to show how things would fit into the customer environment, to go from access from the customer environment to ours, and we collaborate on that. We may have a voice architect, a data architect, and an end-user architect all on the same call, and we're chatting and changing things as we go, and sharing it through Zoom or doing it through version control. It really depends on what we're going to do.

The real-time collaboration has saved us time. I have collaborated on two diagrams so far and it made it easier.

The ability for people to look at a diagram, rather than reading through written documents saved time and as a result money. Nobody reads. People look at pictures. Imagine trying to read through a diagram that's typed out as an explanation versus looking at a picture. If you look at a picture you can just get it, but with a diagram, you just understand it right away because you can see where things connect. Trying to read that, the human brain doesn't work like that. We work looking at pictures and Lucidchart is a really effective tool to help illustrate those pictures, to explain very complex technical ideas to other technical people. We can do immediate sync and realize, "Oh, it connects like that. Okay. We're done. Next."

We're a cloud company, so we have to overcome technical objections to advance the opportunity and help the customer. If we make it right for the customer and we help them, the money comes. We don't need to focus on selling. We just explain, share, and solve, and then eventually money will come.

I was using Visio before because the benefits of graphic representation of data are obvious. The ability to import Visio diagrams is really helpful because a lot of customers that are on Windows are still on Visio. It's such a pain to install Visio on a machine. If it's a Mac there are requirements and it takes a lot of RAM and it bogs down a machine. This doesn't bog down anybody's machine. It's just to have this web.

Lucidchart helped us to realize efficiencies in the projects we use it for. I can show people pictures, and I can change things in a meeting and then email it by the end of the meeting. Because most places we go, especially now with everybody in-home office, I'm going to have great internet access, and that just makes it easier to be able to change things quickly while we're in a meeting and go, "Oh, you changed this. Oh, okay.", and then send it to them as a proof and send it as a PDF or send them a link. That works great. That saves time and accelerates a sale.

The most valuable features are: 

• The network
• Great network icons
• It's easy to use.
• It's simple.
• It's easier than Visio.

Documenting things like systems and new teams is fantastic. It's even easier when you're doing process stuff. You just drag it out and use it.

Its capabilities for visualizing and understanding process flows ad workflows are very good. It's every bit the equal of Visio and that's a compliment because Visio has been developed for 20 years and Lucidchart is relatively new compared to Visio. It's every bit the equal of Visio. I haven't found any feature that I haven't needed yet.

I do not use it for integrations with Atlassian, Salesforce, Microsoft, or G Suite but I think that would be super handy. 

It's important that Lucidspark accommodates both Mac and PC users. We're a diverse company. I'm on Mac, other people on my team are on PCs and we just use whatever we're most comfortable with.

As far as I know, LucidChart can’t be automated with Visual Basic .Net like Visio.

I have been using Lucidchart for years. 

The stability is flawless. I haven't heard of any stability problems from anybody. And we're a cloud company, so we're uniquely sensitive to that. It has to work all the time.

There is no downtime.

I haven't encountered any slowdowns at all. It's a modern web solution. It's going to scale. It uses the same technology like Google and Amazon and every other cloud provider. It's going to be fine. Scalability shouldn't be a problem.

There are at least 150 people like me using it. We don't require any staff for maintenance. It's a browser app, we don't have to do anything but grant access. It's access management, that's it. Zero. There's no install. It opens in a browser.

I'm sure we will increase usage. As we grow, there'll be more licenses added. I can't imagine why we wouldn't add licenses as we gain employees.

We haven't had to contact their technical support. 

I switched from Visio. I use a Mac and the migration was simple. I just imported old Visio into Lucidchart. It's simple and effortless. The ability to import all these files is important to us. 

They're both good products but I use Lucidchart because I'm on a Mac and it's easier to use.

The initial setup was the simplest ever. A child could do it.

It's a web browser. If you can't do that, you don't need to do anything. If you can start a web browser, you can use this thing. The online help is really good.

The implementation consisted of me opening a web browser. Got it added to my Okta tile. That's about it.

We see ROI because it's cheaper than adding something to the Microsoft suite. Instead of getting Visio, we have Lucidchart. We're not buying Visio anymore.

I didn't evaluate other solutions. I went straight to Lucidchart because it came so highly recommended.

My advice would be to just buy it. You don't need to look at anything else. I wish we'd done it a long time ago.

I would rate Lucidchart a ten out of ten. 

I used Lucidchart to design flowcharts for my APIs. 

Lucidchart was able to help me design the flow of my APIs. They are quite complicated with many conditional flows and many multiple-table interactions. It would have been difficult for me to jump to the code directly, without having the clarity given me by using Lucidchart.

The problem is that it can be difficult to think about exactly what needs to be done, which is why I started using Lucidchart. I thought that it would be better if I have a pictorial representation of the flow that I wanted to implement in my system. After I had this visual, I went on to start coding it.

I have definitely realized efficiencies in the projects that I have used Lucidchart for, and it has had a major impact. As I am designing the flow of data through an API, I sometimes forget to handle some of the base cases or some of the edge cases. More importantly, there could remain some endpoints that are unfinished, or there could be some endpoints that are broken. However, if I am using a pictorial representation, such as with Lucidchart, I always know that at each particular point, I have not missed an aspect of the design that would explain what happens when a particular condition occurs.

Lucidchart's ability to create a visualization that people prefer to look at, over reading written documents, has definitely saved me a lot of time. Moreover, it has helped to make my code bug-free because I no longer have broken endpoints. For example, the system that I am working on now is pseudo-transactional, which is the model for the flows. This means that I should have a rollback mechanism if some particular condition doesn't succeed.

It is easy to check for a particular condition using a standard If and Else combination in code, but there are some scenarios in which there are nested conditions. Solutions need to implement these as well, which is more difficult. However, this is where Lucidchart helps a lot. On every particular flow, it asks me to design a new system that includes an endpoint.

I have experienced a 40% reduction in development time because I don't have to search for the use cases during the coding phase. Specifically, I don't have to search for the edge cases or the base cases because they are designed in a pictorial representation that is easy to follow. I just have to look at the diagram and write the code.

I may write a best-case scenario when I get the data, but the nested decisions or the conditional statements remain unhandled sometimes. There is always a question of what will happen to the flow if something specific occurs, or in some cases, does not occur. For example, if something is missing from the database or one of the tables, it can be difficult to forecast what the consequence will be. In cases such as this, how you react is something that needs to be defined. You should know what will happen, even when conditions result in the worst case. This is why it is best to have a pictorial representation. It will allow you to easily design fallbacks for the system.

It is important to me that Lucidchart accommodates both Mac and PC users because sometimes when you switch companies, they use a different operating system. At this point, I'm using Linux and Lucidchart is compatible. At some point in time, I may change to another organization or even just change laptops, so I need the functionality to work properly on the other operating system.

The most valuable feature is the charting, which allows me to visualize the workflows that I will be coding.

The flowcharting feature would be improved if it had some kind of prediction capability that helped to create the diagrams, such as the ability to automatically join components with my database. Another example would be having it smartly or automatically add or join conditionals.

I only used Lucidchart for two or three days before my trial subscription expired.

I did not experience any issues with stability or performance.

This product is highly scalable. I didn't have the opportunity to use the presentation feature or collaborate on designing a flowchart or UML diagram or database schema, otherwise, I could have compared it and looked at the behavior.

I have not been in contact with technical support.

Prior to Lucidchart, I did not use a similar product for this task.

The initial setup is not complex. I just used the website.

This is not a time-consuming process and I was able to start using it in just a few minutes.

I have only used the trial version and have not yet paid for it, or explored the pricing options.

After performing a simple Google search of some flow design tools, Lucidchart was the first result. I tried it and found that it was easy to work with. I've yet to explore the pricing and have not looked at other products.

My advice for anybody who is considering this product is that if you have business-related documents that you use to implement a solution, it generally takes a lot of time to build. But, if you're using Lucidchart and you have already designed the flow, including a diagrammatic or pictorial representation of what the flow would be like, then it will reduce the time required to build it. Also, the system will be better.

I would rate Lucidchart an eight out of ten.

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.

Lucidchart has features for documenting things such as processes and the product is very nice in terms of creating the flowchart, but it appears to lack the ability to process handwritten or textual documentation. I'm not sure if this is possible, so I would rate the capabilities a seven out of ten.

This product has very good capabilities for visualizing and understanding process flows and workflows. I would rate it an eight out of ten in this regard because we can create very good process flowcharts.

Having people look at a diagram rather than read through written documents has absolutely saved us time and money. I estimate that it saves us two hours per week.

The most valuable feature is the ease of use. The usability is very nice in terms of flowchart components that are available.

I would like to see more flexibility in terms of the components that are available. For example, I was not able to create a freeflow shape and I did not have the option to create a straight line without an arrowhead on at least one side. I only had the option of having an arrow on one side or the other, rather than a simple line. Adding these few things would make sense but overall, it is fine.

It would be really helpful if we could create a process flow based on a Word Document or a PPT file.

Having integration with a CRM would certainly help. For example, it would be better if we could extract the fields from our CRM when we are creating a process. 

I have been using Lucidchart for approximately four months.

The availability of the application is 98%. 

At this point, I am not sure of how scalable the product is.

Prior to Lucidchart, I used Microsoft Word and Microsoft PowerPoint to prepare flowcharts. I switched because it is easier to build flowchart diagrams.

The initial setup is straightforward. It is a web-based application that is easy to set up and easy to use. Getting started with inserting diagrams and workflows is not something that I found difficult.

It will take another two or three months to see ROI but as of now, we are happy with the investment.

The price of this product is a little bit high. It is probably 20% higher than what I expected to pay for such a solution.

I have not yet integrated Lucidchart with other products but this is something that I plan to do in the future. I would like to integrate it with Microsoft Teams.

My advice for anybody who is considering Lucidchart is that it's a very good tool for creating processes and documenting flows. It is plug-and-play and very easy to use.

I would rate this solution an eight out of ten.

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.

Lucidchart enables me to put down on paper what I was visualizing in my head. It makes it more shareable than only using words.

The ease of use is the most valuable feature. It's simple to learn pretty quickly.

I have used the organizational charts for visualizing and understanding team hierarchies and relationships. It's been very good so far. It's easy to use, it's easy to manipulate and change quickly if I need to change something. It's a good product.

A couple of times when I tried to move a line, connecting two shapes on an organizational chart, occasionally the line doesn't move as intuitively as I think it should. I have to fiddle around with it a few times to get it to do what I want it to do. That's probably because I'm a new user and I'm not experienced enough, rather than it being an issue with the software itself.

I have been using Lucidchart for around three weeks. 

It seems very available and very stable so far. The follow-ups have been good.

Nobody else is using it yet, but my business partner and our general manager will probably be using it. So there will be at least three of us.

I know I can add other users and stuff like that. So, that's good.

I tried to do charts in Word before.

Lucidchart is definitely more comprehensive, more professional-looking, and more flexible.

The initial setup was of medium-level complexity. 

It didn't take very long to set up. There wasn't anything really difficult about it. I'm just not the most computer savvy person on the planet.

I hope to see ROI soon. 

The price was low enough to make me think that it was fine, I'll go for it. I think it's $80 or so. It's not too expensive. Even if I don't end up using it that much, I feel that it's still a good deal.

I didn't evaluate other solutions.  I had a quick look at Lucidchart when a co-worker of mine used it about a month ago.

I haven't integrated it with third-party solutions. I've only shared it through its share function, like with email and Outlook.

I liked the fact that I could extend my free trial for seven days. That was good because I wasn't ready to make a decision to buy it in the first seven days. I haven't had a chance to really use it properly. I have a pretty busy life and giving me that extra seven days was very useful.

I would rate Lucidchart an eight out of ten. I only give it this rating because I haven't had a chance to really explore all its functionality yet.

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

It is good for documenting things such as processes, systems, etc. Typically, for each project, I'll start with a new file, and for each and every step, I create more sheets under the same file. It is similar to Excel where you have multiple sheets in the same file. It is an effective way for me. It is very convenient and easy to use.

It provides real-time collaboration among users so that everyone is accessing and working on the same version of a document. We typically organize a Zoom meeting at certain times, and I do screen sharing, and a few other people join in. We work together by using collaborative editing options. Not every person who has access to the collaborative option is very technical. Sometimes, they might unknowingly delete something. When more people are collaborating, they can mix things together. Such human errors will come up, but they happen because of the people who are collaborating and not because of the tool. 

The ability for people to look at a diagram rather than reading through written documents saves time. The clients get the reality of what we are doing, which we consider as important. We can show what we are really working on, and they understand. 

I do a lot of process flows and diagrams. It is very important for me, not only for process flows but also for network designing and other such things. It has been helpful for understanding process flows or workflows, and that's the main purpose for which I use it. I have to forward the software process or application process flow to my development team. For non-technical people, such as a client who doesn't know the technical terms, Lucidchart helps in more visualization. When I present it and explain the process, people can easily understand it. That's the main advantage of using this one. For technical people, I spent a few hours defining the process flow, and they can understand it in five minutes.

Lucidchart saved us around 90% time as compared to the other solution. When you use presentation slides, it takes so much time to create a proper design. You have to insert each and every shape, and you have to connect things properly. Moreover, the slide sizes are fixed, and you can't extend the slides, which makes the work harder, whereas, in Lucidchart, you can extend a particular sheet to whatever size you want. You can also put everything together, and it still works fine. I own a development app in which we have more than 10 modules. For all 10 modules, I'm just using a single sheet. I just extend its height, and I am able to use a single sheet for the overall process flow. So, I don't need to go slide by slide to explain what is happening. Previously, to share my slides with other people, I had to put the file in one place and then send the link. If they didn't know much about designing slides, they used to mess up everything. With Lucidchart, this doesn't happen.

I really like the drag and drop feature because it makes the work easier. It is very easy to use. All the pieces are very good. All the icons and all the fields are available in the left panel. So, I just click, drag, and then edit a piece. When I showed it to my managing director, he was very inspired, and he also got a premium account for himself. 

I deal with technical sites. So, I typically use this for roster plans such as who will be on a particular project, and it has been very useful. 

When it comes to network diagrams, it gives us the flexibility to design a network on the go. This flexibility matters to us, and it makes us more productive.

It makes everything easy. It is very convenient as compared to other typical solutions. It makes my work easier. I don't need so much technical knowledge or experience of a particular software. I can just click and drag.

Wireframing can be improved. For mock-ups and wireframing, only 10% of what is required is there. If they can develop this feature, it would be much better because it will then provide everything. Currently, we can design network diagrams, processes, etc., but we should also be able to do wireframing. 

I design the process flow, and after the developer starts the process, I also have to design the UI. At present, I'm using another solution for wireframing or UI, but even in that, most of the icons are missing, so I have to get the icons from the internet. If Lucidchart can have the wireframing options into it, it will be a major success and helpful for us. Lucidchart already has the concept, but it does not have many options. You can select only limited options even if you have a premium subscription.

I used Lucidchart as a student for two years. As a professional, I have been using it for the last one month after joining this organization.

It is totally fine in terms of stability.

It is pretty okay. We haven't encountered any compatibility or accessibility issues so far. 

Currently, we have about three employees who are maintaining the Lucidchart pack. They dedicate roughly one or two hours per day. Each one has a different role. One is handling development, one is handling the testing, and another one is handling the database and backend stuff. Their roles are IT manager, system engineer, and assistant system engineer. 

It is one common license. We just share the permissions. So, we have one account, and I am the one maintaining the account. I have three other people who have fewer privileges. I share the documents with them, but they can't do much editing. They can only do limited operations.

Currently, we don't have any plans to extend its usage. After three or six months, when our initial project is rolled out, we might expand it and purchase more licenses.

I have never contacted their technical support. There was no need to contact them because it is very straightforward and easy to use.

In my organization, they were creating presentations for any kind of process flows, but they didn't have a professional look. They had to spend more time on the explanation part to help clients visualize the process. With Lucidchart, everything is in a single place, and everything is properly designed and organized. When I explain something to clients, it is easy for them to visualize and understand it.

Its initial setup was straightforward. You just create an account and make the payment. It doesn't require any implementation strategy.

The ROI is not in terms of money, but it is in terms of productivity. Previously, to explain the process flow to developers, we had to spend hours creating the presentations. The guy who held my position previously spent almost a week designing five slides that explained the process flow. He had to spend another three to four hours explaining it to our developers, so the duration was very long. With Lucidchart, I can create the whole process flow within a day, and when I show it to the developers, they can understand within five minutes. So, I can witness its effectiveness. It is also useful when there is an occasional change in the process, which sometimes can happen once in a month.

Its pricing is very affordable and reasonable for the features that it provides. I am using its basic plan, and for my usage, it is perfectly reasonable. It suits perfectly.

As a student, when I was searching for such solutions, I came across Lucidchart in Google search. I just created a trial account, and it was pretty okay. I then came to know that my university also provides premium access to Lucidchart. 

In my current organization, I didn't evaluate any other products before recommending Lucidchart to my manager. I know Lucidchart for the last two years, and I thought this would be a perfect fit for us. I recommended it to my manager and showed him how it works, and that's it. He approved to go with it.

It is very flexible and easy to use. These are the two main things about Lucidchart. Moreover, it doesn't take so much technical support. It is just click-and-drag. With some of the other solutions, you need some technical knowledge to understand how it works, whereas Lucidchart doesn't require any technical knowledge. If you have experience working with Word, PowerPoint, or Excel, you can use it easily.

I have very occasionally used Lucidchart to create database schemas or modify existing data structures. I have not used Lucidchart's ability to compare different versions of documents. I might try it in the future.

I haven't tested it with Mac. I have a Lenovo PC and an HP workstation. It works fine with both. I have also tested it with Ubuntu, and it works totally fine with that. In our organization, everyone uses Microsoft.

I would rate Lucidchart a nine out of 10. It just needs more wireframing features.

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.

In general, this product has improved our organization because it makes accessing up-to-date processes and planning a lot easier.

In terms of documenting things such as processes, systems, and new teams, it's easy to go in and share it with people as you're putting the process down. They can interact with it as well, and make changes at a later date. It stores all of these pages together under one folder and allows others to make changes, and it is also documented.

Lucidchart's capabilities for visualizing and understanding process flows and workflows are very good. There are lots of different shapes to use, they are easy to connect, easy to drag and drop, and the user interface is good. Changes and updates are also very good.

Overall, it's a very simple and very easy application to learn and also to use.

Lucidchart is integrated with Atlassian and it works fairly seamlessly. It's fairly important to our operation and the way it has been set up, I don't notice the integration.

The most valuable feature is the user interface. We use it live, so as we're having a conversation and deciding on the process that we're working on, it's easy to map it down, drag and drop components, move the different boxes around, and then add labels and things.

This solution allows for real-time collaboration among users so that everybody is working on the same version of a document, and this has definitely improved our development process. It has saved us time because of the time difference between myself and my colleagues. For example, I work in the UK and I have colleagues that work in Calgary, Canada. There are several hours of difference between us. Whenever we have a meeting in the afternoon, we can sit down and see the same document that we're all working on. We can edit and create processes in the live format, which means that we can maximize the amount of work we can do in this limited window of opportunity.

The ability for people to look at a diagram, rather than reading through written documents, has saved us time. I estimate that it saves us perhaps five hours per week. The savings comes from the fact that it's all there in front of us and we can refer back to it when we're referencing something else.

It would be helpful if there were different options available for organizing the folders, such as having a high-level display with pictures.

I have been using Lucidchart for between two and three weeks. The company has been using it for quite a long time.

This product is very robust, as far as I can tell.

Scalability is very good. You can map a whole product development cycle through sales and interacting with the customer, and probably roadmaps going forward.

It is being used company-wide and I think that most people are probably using it. We have approximately 30 in the UK and in Canada, it is probably 150 more. It seems to be the de facto system and I suppose that as the company expands, the usage will increase.

The initial setup was straightforward. It took a while to get my password for the license, although that may have been an internal issue rather than an external one. I expected it to be pretty quick but it took a couple of weeks, through our IT people.

Once I had my password, all that was required was for me to log onto it. I've also been given links that were shared by a couple of colleagues that I was working on things with.

I probably use 20% of the features available in the product. I'm sure there is a lot more than I could be using it for and over time, I'll figure out more of it.

My advice for anybody who is looking into implementing Lucidchart is that if it fits what you want to do, I recommend it.

I would rate this solution an eight out of ten.

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.

When we have target accounts, we really need to see and get a really clear overview of who's who, who does what, and who the champions are. Lucidchart has been in charge of that.

I have used Lucidchart's abilities to modify existing data structures. When I joined the company, they had existing account maps, and I was able to duplicate them and then tweak them to my needs. Lucidchart supports such processes very well. It is very user-friendly. It was easy for multiple users to collaborate on a single chart. Anyone can jump in and start adding and changing to an existing chart. All that activity is also trackable, which is helpful.

We have integrated it with Salesforce and G Suite. These integrations are important because when you make tweaks on Lucidchart, you want to make sure that those tweaks are also reflected on Salesforce and other solutions. You can update on one, and it gets updated automatically on the other and vice versa. These integrations are critical to what we do.

There is also integration with Slack, which is our main communication channel. It is definitely something we use more than email. Having this integration between Lucidchart and Slack really allows us to share documents for feedback. For example, I can share a Lucidchart via Slack with my boss, and then he would take a look at it and give me immediate feedback over Slack, which works in conjunction with the comments in Lucidchart. Basically, when I'm speaking with my manager, we communicate via Slack about the Lucidchart file, but when I'm speaking with my counterpart, who's working with me on the same account, then we would make the tweaks directly in Lucidchart. Slack just complements the collaboration that's within Lucidchart. It adds another layer for sharing with the wider organization.

Lucidchart provides real-time collaboration among users so that everyone is accessing and working on the same version of the document. This real-time collaboration is key because I would be on Zoom with one of my colleagues, and then we would jump into a Lucidchart file and start tweaking it as we go together.

It has definitely saved time. More efficiency gains are definitely there. It has cut our time. Previously, we used to create something in a PowerPoint or Keynote file, but they were just not as collaborative, dynamic, and adaptable as Lucidchart. In terms of numbers, it has saved us at least 20% of the time that would have been spent on other programs.

It has definitely helped us in realizing the efficiencies in the projects. It has made us more efficient as a team. The collaborative nature of it is something that's key to time-saving and being efficient in our workflows. Each of us manages multiple accounts, and it is just easier to keep track of things with Lucidchart.

The ability for people to look at a diagram rather than reading through written documents has saved time and, as a result, money, but I don't have specific metrics to show for that.

I really like the drag and drop feature. It makes it really easy. I also like the comment feature that enables various users to comment on the chart in real-time.

I like how all the contacts in my chart are linked to LinkedIn. That's what makes it really easy for outreach and for making sure we have all the contacts right there in front of us when we need to.

It is very user-friendly for documenting things such as processes, systems, new teams, etc.

Lucidchart's organizational charts are very good for visualizing and understanding team hierarchies and relationships. That's the reason we use it. It gives you a very clear overview of who does what within the company. I also like how adaptable it is. It is very easy to tweak if someone leaves the company or someone joins, or as we find out more information about the company that we're working with in terms of who the players are. It is almost like playing chess. We can just move the pieces around the board.

It is very good for visualizing and understanding process flows or workflows. When I first started using it, I didn't feel the need to read the whole manual. It is very intuitive in terms of what the steps are. It is integrated with Salesforce as well, which makes it very easy to import leads from Salesforce into Lucidchart to create those maps. The workflows and processes are very seamless.

It would be nice to be able to import not just contacts from Salesforce but also leads. In the beginning, when I was still learning the ropes and my way around it, I couldn't find such an option. There might be an option, but I just don't know about it.

I have been using it for only about a month, but my company has been using it longer.

It is really stable. I honestly haven't incurred any issues related to stability.

It is scalable. As our team grows and we hire more people, it can definitely accommodate all the users that we need. I do not have the numbers, but I just know we're hiring a lot of new people, myself included, recently.

We have more than 100 licenses, and its users include the Business Development people and Sales Account Executives. I'm on the Business Development team. There are also some Customer Success Managers who get involved once a deal is closed. They need to know who the players are at various accounts. We also have a team of Sales Engineers. They definitely get involved in it as well. So, Business Development, Sales Account Executives, Customer Success, and Sales Engineers are the four groups that are the main players.

I have never interacted with their technical support.

I was not there for that. There is a whole team that does that. They know how to handle Lucidchart. They handle other tools too.

For its maintenance, maybe one or two people are required on a regular basis. They just need to send out very quick and short surveys to see our experiences with the software. It is usually done when we are getting close to renewal, and then they see if it's worth extending the licenses.

I would definitely recommend it. It is a tool that I wish I had in my previous jobs and companies. I would advise others to start with an existing template from the company and then reverse engineer that. It is very easy and very intuitive to use, so I would say go for it.

Lucidchart really has a clear overview. Once you have your players charted out, it is bound to change at some point, and it is not going to be static. It is dynamic, and Lucidchart can definitely accommodate. It is adaptable enough to accommodate all those changes.

Our company only uses Mac. So, it's not important for us to be able to access it on PC. I have not used Lucidchart's ability to compare versions of documents.

I would rate Lucidchart a nine out of 10.

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 joined my new company at the beginning of May. I'm in HR, and it is called the People Performance and Culture (PPC) team. One of the things I was told to do was figure out the process flow for onboarding. Because it is APAC and we have some people in India, Japan, China, and Singapore, it was confusing to understand who comes under which part during onboarding. My manager wanted to make a process flow, so I decided to make a flow chart. I literally just searched for flow chart software or easy-to-use tools on the web, and I came across Lucidchart. I really enjoyed using it. I was quite quickly able to understand how to use it and get on with my process flow. This process flow has really helped all the regions in understanding how onboarding works across all the regions. In the future, we can easily see how the process works rather than thinking it is too complicated, and we don't want to get into it. It just makes things simpler. Now, more people use it, and obviously, I can add more features to it if I want to. I think we have used it for our org chart as well. We've just rolled out a new org chart. I wasn't part of that, but I can see that they've used Lucidchart for that.

It is very useful for documenting things such as processes, systems, new teams, etc. because it has everything. It is very easy to document, and it is very easy to see the date you created or gave access to something.

It provides real-time collaboration among users so that everyone is accessing and working on the same version of a document. This real-time collaboration has affected our project development process. I was able to get someone to look at the org chart while I was working on it. As opposed to making changes at the end, I could make changes as I was working on a document. Its real-time collaboration has saved us time. It has approximately saved an hour worth of work.

The ability for people to look at a diagram rather than reading through written documents has also saved time, and as a result, money. It has saved about an hour.

It has definitely helped us in realizing efficiencies in our projects. It has made everything more visual. Once things are more visual, it becomes easier for me to see whether there are glitches in the process, whether there is a better way of doing things, and whether we have too many steps for one thing. The visual aid has definitely helped us look at the processes in a different light.

We use Microsoft Teams in our company, and one of the reasons for using Lucidchart is that you can integrate it with Microsoft Teams. If I need to send somebody a document through Microsoft Teams, it is very easy. This integration is highly important for our operations because otherwise, we will have to use another solution or way to do the same thing. We are already using Microsoft Teams, so it is much easier to tag it on to Microsoft Teams.

The flow chart is most valuable. It is a very user-friendly and simple-to-use product. Quite quickly, I was able to understand how to use it and just get on with my process flow. 

Its organizational charts are pretty good for visualizing and understanding team hierarchies and relationships. These organizational charts are very visual. The colors also help. It is also easy to create an organizational chart.

I use it for visualizing and understanding process flows or workflows, and I would rate it really high from this aspect because I found it very easy to use. It has some suggested themes, so I can make them look pretty. There was access to videos or tutorials if I got stuck. That was really good as well.

It can have more colors or graphics. Currently, it is a little boring. It can have a little bit more fun factor.

I have started to use it very recently. 

It is quite stable and reliable.

It is quite scalable. We are a small department. Currently, two departments have access to it. We have only about 30 people, and out of them, only four are using it.

I am pretty new here, and we're just figuring out APAC processes and hiring new people. I will be using Lucidchart a lot more in the coming months because we're trying to figure out all the processes and the process flows amongst all the regions.

It is pretty good. They were videos available for any questions that I had while I was using the solution. I'm more of a visual person, so the videos really helped.

It was straightforward. It took just a few minutes.

I did it on my own. I was using the free account because you can use a free account. It turned out that we had a company account with Lucidchart. My manager gave me access to that, and then basically, I uploaded the flow chart that I had created over there.

For its deployment and maintenance, probably only one or two people are required.

I did come across Visio, but I looked at Lucidchart first. Visio wasn't as user-friendly.

I have definitely told people to use it. It really makes things easier. The visualization is really good, simple, and neat. For me, visuals work much better, and it is easier to spot mistakes when you can see it all in one go rather than in different steps. I would definitely advise people to integrate it and use it as much.

In my organization, we currently only use PCs, but it is good that it is compatible with Mac and PC. I have not used its ability to compare versions of documents. I have also not used any other product from their suite.

I would rate Lucidchart a nine out of 10. It just needs a little bit more fun factor.