Operations
$47 starter
Team-ready
⌁ Diagram Explainer
Turn a messy process, SOP, or workflow into a clear text-based diagram and plain-English explanation — ready to hand to your team, paste into a doc, or share with a customer in minutes.
Who it is for
For owners and operators who explain things with words — when a diagram would do it faster.
Contractors, service businesses, agencies, consultants, and any team leader who has a process in their head (or in a long email) that needs to be visualized and documented.
- You explain the same process repeatedly because it's never written down clearly
- New hires or team members misunderstand workflows because there's no visual reference
- You want to show a customer how you work — but a wall of text doesn't convey it
- SOPs and playbooks exist as paragraphs nobody reads — diagrams get followed
Inputs and outputs
What the buyer gets.
What it asks for
- The process, workflow, or SOP in any format (notes, email, bullet points)
- Audience: team member, customer, executive, or new hire
- Output format: step-by-step flowchart, decision tree, swimlane, or linear sequence
- Any labels, roles, or decision points that must be included
What it returns
- A text-based ASCII/Unicode diagram ready to paste anywhere
- A plain-English walkthrough of each step for the target audience
- Decision point callouts (if/then logic labeled clearly)
- A copy-paste version for Google Docs, Notion, Slack, or email
- Optional: Mermaid.js or Lucidchart-compatible markdown syntax
The problem it solves
Before and after.
✗ Without this skill
- Processes live in your head or in a 12-paragraph email nobody re-reads
- New team members have to shadow you for days to learn basic workflows
- Customer questions about "how it works" get answered differently every time
- SOPs are started but never finished because diagramming tools take too long
- Knowledge walks out the door when a team member leaves
✓ With this skill
- Any process becomes a visual diagram in under 15 minutes
- New hires get a flowchart on day one — no shadowing required for basics
- "Here's how we work" is a shareable one-pager, not a conversation
- SOPs get done because the hard part (the diagram) is done for you
- Institutional knowledge is documented and transferable
Real examples
Sample outputs you can inspect.
Lead intake flowchart (ASCII)
LEAD INTAKE PROCESS
────────────────────
[Lead arrives]
│
▼
┌─────────────────┐
│ Source? │
└────────┬────────┘
│
┌──────┴──────┐
▼ ▼
[Phone] [Web Form]
│ │
▼ ▼
[Log in CRM] [Auto-email confirm]
│ │
└──────┬──────┘
▼
[Owner reviews]
│
┌──────┴──────┐
▼ ▼
[Follow up [Archive —
within 1hr] not qualified]
[STATUS: Review step labels before sharing with team]
Decision tree: Quote or decline?
QUOTE DECISION TREE
────────────────────
New request comes in
│
▼
Is job in our service area?
YES ──► Continue
NO ──► Politely decline + refer
│
▼
Is timeline realistic?
YES ──► Continue
NO ──► Discuss options or decline
│
▼
Does budget match scope?
YES ──► Prepare full quote
NO ──► Offer scaled-down option
or decline with note
│
▼
[Send quote within 24h]
[Log outcome in CRM]
[NOTE: Customize "service area" and timeline rules for your business]
Plain-English walkthrough for new hire
HOW OUR LEAD PROCESS WORKS (New hire version — plain English) Step 1 — Lead comes in Every lead arrives one of two ways: a phone call or a web form. Both go into the same system. Step 2 — Log it If it's a call, log it in [CRM name] within 15 minutes. If it's a web form, it logs automatically. Step 3 — Owner reviews All new leads go to [Owner name] first. Don't reach out to the customer until [Owner name] has looked at it and given you the green light. Step 4 — Follow up Once approved, follow up within 1 hour using the reply template in [folder/channel name]. If you're unsure about any step, ask before acting — not after. [STATUS: Replace [brackets] with your actual tool names before sharing]
Live diagram preview
What a Mermaid.js output looks like
```mermaid
flowchart TD
A[Lead Arrives] --> B{Source?}
B -->|Phone| C[Log in CRM manually]
B -->|Web Form| D[Auto-logged + email confirm]
C --> E[Owner Review]
D --> E
E -->|Qualified| F[Follow up within 1hr]
E -->|Not qualified| G[Archive with note]
F --> H[Quote or book job]
```
Paste this into Notion, GitHub README, or any Mermaid-compatible tool for a rendered flowchart.
Setup + workflow
Four steps from messy notes to shareable diagram.
1
Dump the process
Paste in whatever you have: bullet points, a long email, a voice memo transcript, or a list of steps you rattled off. Don't format it — just dump it.
2
Define the audience + format
Tell it who will read this (new hire, customer, team lead) and what format you want: flowchart, decision tree, swimlane, or step sequence. The audience shapes the language level.
3
Review the diagram + walkthrough
You get an ASCII/Unicode diagram you can paste anywhere, plus a plain-English walkthrough for the same audience. Check that every step is accurate before sharing.
4
Paste and share
Drop it into your Google Doc, Notion page, Slack, employee handbook, or customer welcome email. No design tool required — it works in plain text.
Common questions
Frequently asked.
Does this require a diagramming tool like Lucidchart or Visio?
No. The default output is plain-text ASCII/Unicode that renders perfectly in any document, email, or messaging tool. If you want a rendered diagram, it also outputs Mermaid.js syntax you can paste into Notion, GitHub, or any compatible viewer — no account required.
What if my process is too complex to fit in a single diagram?
Break it into sub-processes. Tell the skill which part of the workflow to diagram first (e.g. "just the intake step, not the quoting step"). You can run it multiple times to build a modular set of diagrams that link together.
Can I use this for customer-facing documentation?
Yes. Tell it the audience is "a customer reading a welcome packet" and it adjusts the language to be non-technical and reassuring. Great for "here's how our process works" pages on your website or in onboarding emails.
What if I already have a diagram and just need it explained in plain English?
Paste the diagram or describe it step by step and ask for a plain-English walkthrough only. The skill works in both directions: diagram → words, or words → diagram.
Explore more