I Stopped Drawing Flowcharts by Hand, Here’s the AI Tool I Use Instead

Last year I burned most of a Tuesday afternoon dragging boxes around inside a diagram app. The job sounded simple: write down how our team handles refund requests so a new hire could follow it without pestering three different people.

Four hours later I had something that looked decent, and then my manager pointed out I’d skipped the part where finance signs off on anything over a certain amount. Back in I went, nudging arrows, resizing shapes, watching the whole layout collapse every time I squeezed in a new step.

That was the afternoon I started hunting for a better way to do this. What I found genuinely changed how I document anything at work, so I figured it was worth writing up.

Why flowcharts are more annoying than they look

If you’ve never had to draw a proper process diagram, you might assume it’s a ten-minute job. Boxes, arrows, done. The problem isn’t the drawing. The problem is that real processes are messy.

Take that refund example. It’s not a straight line from “customer asks” to “money returned.” There’s a check on whether the order is inside the return window. There’s a branch for damaged goods versus buyer’s remorse. There’s an escalation path when the customer has already complained twice. Every one of those forks means another decision shape, another set of arrows, and another chance to accidentally leave a dead end that goes nowhere.

Then there’s the standards problem. Most people draw whatever shapes feel right, which is fine until someone from another department opens your file and has no clue whether a rounded rectangle means a task, a system action, or a waiting period.

There’s an actual standard for this, called BPMN, short for Business Process Model and Notation. It defines what each symbol means so anyone who knows the notation can read your diagram without a legend. Circles are events, rectangles are activities, diamonds are decision gateways. It’s not complicated once you’ve seen it a few times, but placing all of it correctly by hand is tedious work.

The thing that actually fixed it for me

The shift for me was realising I didn’t need to draw anything. I needed to describe it.

I started using BPMN AI, which lets you type out a process in ordinary English and spits back a proper diagram. So instead of dragging shapes for four hours, I wrote something like: “Customer submits a refund request. System checks if the order is within thirty days. If yes, support reviews the reason. If the amount is over five hundred dollars, finance approves before the refund is issued. If the order is outside thirty days, the request is declined and the customer is notified.”

That’s it. That’s the input. What came back was a laid-out diagram with the branches in the right places and the symbols matching the standard. Was it perfect? No. I’ll get to that. But it took maybe ninety seconds to get to a draft that would have taken me half a day, and more importantly, it caught two branches I would have forgotten because I was too busy thinking about arrow placement to think about logic.

What it got right

The biggest win is the layout. Anyone who’s used a diagram tool knows the special misery of inserting a step in the middle and watching every connector below it turn into spaghetti. The AI handles positioning automatically, and when I edited my description and regenerated, it re-laid everything out cleanly instead of making me fix it manually.

The second win is that it uses the proper notation without me having to memorise it. I know roughly what a gateway is, but I couldn’t have told you off the top of my head when to use an exclusive gateway versus a parallel one. The tool made those calls, and reading its output taught me the difference faster than any tutorial had.

Third, and this surprised me, it made the diagrams collaborative in a way mine never were. When I shared my hand-drawn version, colleagues would say “looks good” and move on, because editing it meant learning the tool. When I shared the description alongside the diagram, people started sending me corrected paragraphs. “Actually finance only reviews it if the customer is on an enterprise plan.” That’s a one-line edit and a regenerate, not another hour of dragging.

Where you still need a brain

I don’t want to oversell this. A few honest caveats.

It only knows what you tell it. If your description is vague, the diagram will be vague. I got much better results once I started writing in short, explicit sentences with clear conditions rather than rambling paragraphs. Think of it like giving directions to someone who’s never been to your city.

It also can’t tell you whether your process is any good. It’ll happily draw a workflow with six pointless approval steps, because that’s what you described. Spotting that step three and step five are redundant is still on you. The tool removes the busywork, not the thinking.

And for very large processes, I’d still break things into chunks. Trying to describe an entire department’s operations in one go produces something technically correct but too dense to read. Two or three smaller linked diagrams beat one wall of boxes every time.

Who should actually bother with this

If you’ve ever been asked to “just write down how you do that,” this is for you. That includes team leads writing onboarding docs, freelancers explaining their client workflow, small business owners trying to hand a task off to a new employee, and anyone in operations or support who’s tired of the same questions landing in their inbox.

You don’t need to be a business analyst. You don’t need to learn a modelling tool. If you can explain your job to a friend over coffee, you can produce a clean diagram of it in a couple of minutes.

A few things I’d do differently starting out

Write your description as a sequence of short sentences, one action per sentence. Name who does each step, because “the request is reviewed” is less useful than “support reviews the request.” Spell out your conditions explicitly, using plain if/then language. And once you have a draft, show it to whoever actually does the work every day, since they’ll spot the missing exception within about ten seconds.

Worth it?

For me, easily. I’ve documented five or six processes since, and none took longer than twenty minutes including the back-and-forth with colleagues. More than the time saved, though, I stopped avoiding the task. Documentation used to sit at the bottom of my to-do list because I dreaded the diagram tool. Now it’s a quick job I actually knock out, which means our team’s docs are current instead of eighteen months stale.

If flowcharts have been quietly ruining your week too, this is one of the more genuinely useful things AI has done for my workflow.