Dr Lead Flow← All free guides
Systems · Diagrams

Draw the System

If you can't draw your process, you don't have a process. You have a habit living in your head. The skill that turns any messy system into a clean, dummy-proof diagram.

Most clinics I work with have never once drawn their own client journey or their own marketing engine from end to end. It's not written down anywhere. It just lives in the owner's head, which means it dies the day they're too busy to do it themselves.

I map every system I build this way. Not a wall of boxes and crossed arrows, an actual clean diagram, real numbers, real examples, that a new hire or a client can look at once and understand.

This skill is the layout discipline that makes that possible. Most AI-generated diagrams are unreadable because nobody sized the boxes to the text or lined up the columns. This one does both, and it turns a messy process into something you can hand off.

The three levels

Level 1 · Manual

Keep it in your head and re-explain it to every new hire, every time, slightly differently.

Level 2 · AI + connectors

Describe the process to the skill, get a clean diagram back with real examples plugged in, not placeholder text.

Level 3 · Agents on schedule

Every new client's system gets diagrammed on day one and becomes the reusable template for the next one in that vertical. That's how I scale this.

Connectors for this guide: No connectors required — works from a description of your process, ideally with one real worked example.

The free skill

It picks the right shape for your content, sizes every box to its actual text so nothing overlaps, zones related sections with labeled backgrounds, and marks which parts are the reusable template versus the one-off example.

How to use it: copy the whole thing, paste it into Claude (or save it as a skill file if you use Claude Code), and say “map this out”. It walks you through the rest. Works with any AI that can read your data.
draw-the-system.md
---
name: draw-the-system
description: Turns a messy process living only in your head into a clean, dummy-proof diagram — the layout discipline that makes a diagram actually readable, not just a box-and-arrow mess — so you can hand your system to a new hire, a client, or an agent and they get it in one glance. Trigger on "map this out", "make this dummy-proof", "turn this process into a diagram", "draw my system".
---

# Draw the System

If you can't draw your process, you don't have a process. You have a habit that lives
in your head, which means it dies the day you're too busy to do it yourself. Most
businesses, clinics especially, have never once drawn their own client journey or
their own marketing engine end to end. That gap is why the same mistakes repeat.

This skill produces a diagram that's actually readable — not a wall of boxes and
crossed arrows, which is what most AI-generated diagrams turn into.

## Before you start

You need the process described out loud or in notes — every step, in order, plus
anything that branches (if X, then Y instead of Z). If a real example already exists
— a client, a campaign, a specific case — pull that in too. Real examples beat
abstract steps every time; "here's the actual ad and the actual result" teaches
faster than "run ads, measure results."

## Step 1: Pick the shape before you place a single box

The most common mistake is defaulting to boxes-and-arrows for content that isn't
actually a flow. Decide first:
- A sequence of steps in order → a left-to-right or top-to-bottom flow.
- Several parallel tracks that don't depend on each other → zones side by side, not
  one long chain.
- A decision point with different paths → a branch, clearly forked, each path labeled
  with the condition that sends someone down it.
- A reference sheet (a matrix, a checklist, a menu of options) → a grid, not a flow at
  all. Forcing a checklist into arrows makes it harder to read, not easier.

## Step 2: Write the content before you draw anything

For each box: a short title, and the real content — real numbers, real examples, real
names where possible, not "insert your data here." A diagram used as a template later
should mark exactly which fields are meant to be swapped (a consistent color works
well) so it's obvious what stays and what changes per use.

## Step 3: The layout rules that separate readable from amateur

- **Size every box to its actual text.** Never guess a box size and hope the words
  fit — measure the longest line and size around it. This single rule fixes most
  overlap problems before they happen.
- **Line up variable-length elements on a fixed column**, never right after each
  other. If one item's label depends on its own length, a long one collides with the
  next row.
- **Give asides their own clearly separated space.** A warning, a footnote, or a
  callout crammed between two flow steps reads as clutter, not as a note.
- **Keep everything in a row the same size.** Three cards side by side should share
  identical width and spacing — pad the shorter ones rather than shrinking the layout
  to fit the longest.
- **Zone related content with a labeled background**, so someone scanning fast can
  tell "this whole section is the ads engine" without reading every box.

## Step 4: Build it as a script, not by hand

Hand-placing dozens of boxes with guessed coordinates is how diagrams end up
overlapping. Generate the layout programmatically — compute each box's size and
position from its content — so it can be regenerated cleanly the moment something
changes, rather than manually nudged forever.

## Step 5: Make it a template, not a one-off

The most useful version of this isn't a single diagram — it's a template you can spin
up for the next client or the next vertical by swapping the marked fields. Mark
clearly which parts are the reusable skeleton (the process itself) and which parts are
specific to this one example (the real numbers, the real names) so future-you can
clone it in minutes instead of starting over.

## Rules

- If a diagram looks messy or crowded, that's never a "nudge some boxes" problem —
  find which rule above was skipped and regenerate the whole thing.
- Real examples over placeholder text, always. "Book a call" as filler teaches
  nothing; a real headline that pulled real leads teaches everything.
- A diagram nobody outside your head can follow in ten seconds isn't done yet.

Want your whole system mapped out for you?

I've built these for dozens of clinics. Book a call and I'll map yours, or come build alongside me in the AI CEO Lab.

Pick a side.

Most people read this and forget it by Friday.

The other kind joins the Community. They get a new build every single day and stop needing free guides, because they're too busy running actual systems.

Already past the basics? Same room. Go deeper, trade builds with people who are actually shipping, and see what's working in AI right now, not last year.

This is where the challenge lives.
Free · Weekly · No Fluff

AI moves fast. Most people get left behind.

One email a week. What changed, why it matters, what to do about it. Skip it and find out the hard way.

Free forever. Unsubscribe anytime.