// how to
How to Make a Flowchart or Diagram with Claude
Describe the process step by step in plain English, including the decisions (yes/no points) and who does each step, and ask Claude to draw it as a flowchart. Anthropic lists diagrams and flowcharts among the things Artifacts can be. Then ask Claude to find missing steps and dead ends.
The short version
Drawing a process is the fastest way to find out where it breaks. Describe how something works today, let Claude draw it, then ask it where a customer could get stuck or a task could fall through the cracks.
Step by step
- Pick one process with a clear start and end: “a customer orders a cake”, “a new hire’s first week”.
- Describe the steps in order, as you would to a new employee, including who does each one.
- Name the decisions: “If the cake is custom, the baker approves the design first.”
- Ask Claude to draw it as a flowchart Artifact.
- Ask for problems: missing steps, decisions with no “no” branch, steps with no owner.
- Fix and redraw until it matches reality.
Prompts to copy
Draw it:
Draw a flowchart of this process. Use boxes for steps, diamonds for decisions, and label who does each step.
<process>
A customer orders a custom cake by phone or website. If it's a custom design, the baker approves it
within a day; if not approved, we call the customer. Customer pays a 50% deposit. Baker bakes the day before.
Customer picks up and pays the rest.
</process>
Find the gaps:
What's missing from this process? List decisions without both branches, steps without an owner,
and places a customer could wait without hearing from us.
Get editable code:
Give me this flowchart as Mermaid code too, so I can edit it in other tools.
Example
The cake process above, once drawn, shows a gap: if the customer misses pickup, nothing happens. That’s a real problem (a wasted cake and a lost deposit dispute) found in two minutes.
Mistakes to avoid
- Describing the ideal process instead of the real one. Draw what actually happens.
- Too much in one chart. Split big processes into a few smaller ones.
- No owners. Every step should say who does it.
When to go further
A clear flowchart is also the best brief for software: if you want online ordering or booking built around your process, it shows a developer exactly what to build. See our project playbook for how we use these diagrams.
Related: use Claude Artifacts.
Frequently asked questions
Can I edit the flowchart after Claude makes it?
Yes: ask for changes in the chat ('add a step after payment', 'make refunds a separate branch'). You can also ask for the diagram as Mermaid code, which many tools can open and edit.
What's a flowchart good for in a small business?
Training new staff, spotting where things go wrong, and explaining a process to a developer or a partner. Drawing it often shows steps nobody owns.
Free download
Get the AI Coding Starter Kit
A PDF you can use with any AI coding assistant: a project-rules template, 25 tested prompt patterns, a team adoption checklist and an assistant comparison sheet. The editable Markdown sources are included.
- Works with Copilot, Claude Code, Codex, Cursor and more
- Double opt-in, one-click unsubscribe
- No trackers, never shared