What is our primary use case?
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.
How has it helped my organization?
We're primarily using it for process mapping and it's much quicker than trying to do it in Excel.
Doing things digitally means that if I'm on a Teams or a Zoom meeting, I can get input from people and they can see it as we go. I'm a pretty big user of whiteboards. I have two in my office and those are great. But what I hate sometimes is when it comes to, "All right, let's take this away. Let's run with it," I have to take a picture and send it out. Then, at nine o'clock at night, someone on the team will say, "Oh, I just thought of this step that we completely overlooked..." I can't do anything about it because it's on my whiteboard. But using Lucidchart, I've been able to say, "Okay, I've got my iPad, let me add that in really quickly." I like the convenience and the user interface.
It is so great for understanding process flows or workflows. With the prior training that I had, doing things on whiteboards and in Excel or Word to manually build stuff was clunky. Because it was clunky, it was slow. When it's slow and you have a meeting, you lose people's attention. Because this is fast and not clunky, people are able to say, "Oh, okay. This is the next step and the next step." I get better engagement and I get through mapping the processes quicker. Because it has the different shapes and the explanations of what things mean, I'm able to get more out of it. Visually it is the best application that I've used.
I'm also getting productive engagement and productive challenge from my teams. Someone will say, "Well, that step shouldn't really be represented by a diamond. It's more a case that somebody has to go and get things and that causes a delay, but it's not necessarily a decision because it's built into the process."
Per week, I probably do two of these exercises, and each one would take three-plus hours to get through when dealing with some of our more complicated processes. Now, we can get them done in about an hour. That's a huge improvement because of the software itself, but it has also helped us to see, "Wow, we have a lot of excess steps and waste in our process." For example, we were working on it with a team over the last two days and we got two new maps up in the span of an hour and a half or two hours. We're getting much quicker at process mapping and understanding what we need to address.
Lucidchart has also helped with training and developing standard operating procedures. Before, we would just use a piece of paper, and maybe it would have a picture of what is going on. And on that piece of paper would be a list of sequential steps. We still have to do that for FDA regulations of having and maintaining SOPs. But having printed out flowcharts benefits us because you can just flip over the piece of paper and see, "All right, here are the four or five little steps I take before I get to a decision, and here are the two branches from that decision." That extra context helps us in building a development tool. And we can post the process flow map for, say, operating a hopper, right on the equipment. That way, people can see things. And if they need more context or deeper instruction, they can bring up the actual SOP with all the words. But a quick little chart that shows the flow: "This is what I do. This is what I do if this fails, et cetera," is something that we're getting a lot of immediate benefit from.
What is most valuable?
It is important that Lucidchart accommodates both Mac and PC users because if you support Mac, that means you also support the mobile applications on the iPad. Because of the kind of factory setting we're in, all of the office personnel and management have laptops, but they also have iPads. Some of the other employees have access to an iPad, but not all of them do. When we're trying to talk through a process with them on-the-fly, or at the point of occurrence, it's so much nicer if we can both have it up on the iPad. That's why I would say the Mac support is essential.
It's easy to click and drag and automatically insert shapes. And once you have selected an arrow to move to a new location, it auto-associates the shape with it and you can right-click and change. There's no copy, paste, make next steps, start typing. It's all seamlessly integrated.
What needs improvement?
Integrations with third-party software are pretty important. I do a lot of work out of Tableau for data analysis. One of the things that I find frustrating is that all of our Tableau information is on a server, so when I send that out people can't open it and use it. I then have to go back and do extra work to convert everything into an Excel format that everybody can use. It would be really important to me, if I send something out to somebody who doesn't have a Lucid account, that they can just click and see it, instead of having to log in and create an account. I can understand if they can't edit it; that makes sense, to restrict that behind the paywall. But in terms of actually being able to open up the data, it would help. With Tableau, for our data management systems, it's a big constraint. The user interface across other software is very important to me.
Something that would also be nice—and maybe it's just a feature I haven't explored yet—would be to be able to link the data from other sources, whether Tableau, Microsoft Power BI, or even straight from Excel. That way, if we build processes we could immediately assign data, whether its defective units, operational uptime or operational downtime, changeover time, et cetera. It would help to be able to put it in there so that we can have the data collected and then somehow integrate it to each step of the process. For example, if this step of the process fails, it causes X minutes of operational downtime and Y number of defective units coming out of the machine. I understand that it might be a little advanced, but right now I'm taking the charts and correlating them to existing data from Tableau and from Excel. If there were a way to make it seamless, so I could click on my flow chart and show, "This decision point, this diamond, is potentially responsible for X number of minutes operational downtime, and Y number of defective bottles," that would be the continuous improvement dream.
For how long have I used the solution?
I have been using Lucidchart for close to a year.
What do I think about the stability of the solution?
I've only had one or two issues where the performance of it was delayed. I don't know if the cause was the internet connection or if it was because I was trying to fill out the charts on the iPad. But using the Apple Pencil, there were time delays between drawing lines between different process steps and getting things entered in. It was a little awkward on the timing. When you build something on the iPad, its performance might just not be as effective as building it on the computer.
Other than that, every time I build something there's no buffering or issues with it deleting my work or not saving things. It seems to be doing all the things that it needs to be doing. The iPad issue is the only little snafu I've had.
What do I think about the scalability of the solution?
I can't speak too much abou its scalability. We could probably expand it and get multiple supervisors at my plant using it. But in terms of getting the information made and sharing it out, it's pretty quick and pretty easy. If we were to add a company server for it and 18 people working on it at the plant, I don't know if there would be scaling or server issues.
I hope we have plans to increase usage of Lucidchart. Our business is split up into four plants across the country. In the Continuous Improvement department there are four of us. We each have a license. There are plans to bring one more person onto the team. I'm hopeful that we would then be looking at getting it at least for our operations and production managers, which would potentially be an additional two licenses per site.
How are customer service and technical support?
I have not needed to use the technical support yet. I've not had any major issues.
Which solution did I use previously and why did I switch?
Before Lucidchart, we were building process diagrams in Excel.
How was the initial setup?
The initial setup of Lucidchart is a pretty straightforward process. There is still stuff I'm learning as I go, when it comes to knowing what to look for with different templates. But if the most basic function you need is to make process maps, and to do it quickly, and then figure out what you've got to improve, it's very effective at that.
What was our ROI?
While it's not directly saving money, because it is a paid-for service, it saves us money in the sense that we have a better understanding of our processes, what can be changed, and what we need to attack. We then go out and attack it, do it, update the maps, and then we get the return on the investment.
Which other solutions did I evaluate?
I used Visio here and there when I worked for another company, but I was not the main user of that application. Still, between it and Lucidchart, I prefer Lucidchart. It is a lot simpler and a lot more accessible.
In my current company, we have not evaluated any other solutions. I think our engineers do have CAD for facility layout, but in terms of competitors to this, we have not looked at any directly.
What other advice do I have?
Watch some of the tutorials, check the reviews, and definitely talk to folks who are using it. Figure out what they like, what they don't like, and what they would want changed. There's a lot that I like about it. I find it to be a pretty good service. Get involved and play around with it, especially if you're working on facility layouts. I have printouts for some of the areas where we're implementing 5S and changing processes in. It's nice having something that the engineers have printed out, like a schematic or a blueprint for us.
Also, if you're going to try it out, try to make a simple process that you already know all the steps for; one you've already done it in Excel or in something else. See how much faster you can do it on this. That would be the big selling point. Trying to make some of these process maps in Excel, because it's so clunky and so slow, could take me 35 minutes just to get a 15-step process properly built, connected with the decision points in the lines, and for us to really understand where the pain points are. Taking something as simple as a 15-step process, timing out how long it takes to build it in Excel or PowerPoint, and then comparing it to this may show you, "Wow, with Lucidchart it took, maybe, five minutes."
I've been discussing getting this implemented in other departments at my facility.
In terms of its integrations, we've used it with some of the Microsoft suite for sending things out. I haven't used it for Slack yet, although I do use Slack for a nonprofit that I'm in. That actually might be a good opportunity because then I could just make some process maps for some of the nonprofit stuff that I do. And could then just send it out that way.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.