Process visualization: three formats your team understands
When you look into process visualization, you quickly end up with software for diagrams, boxes and arrows. That looks tidy. In daily work, though, your team mainly needs a format it can work with: to see what exists in the first place, to hand a process over to someone else, or to understand where decisions are made inside it. For these three purposes, we use three formats: the list, the process profile and the flowchart. In this article, we show all three, explain when each one fits, and show one real process from a tax advisory firm in all three formats.
Purpose first, then format
If the first thing you have is a program for flow diagrams, you draw every process as a diagram. Then every change needs a new picture, and the visualization goes out of date quickly. That's why, for us, the purpose comes before the format.
So ask first: What do you need the visualization for?
- Overview: You want to see which recurring processes exist in your business, who does them and how much time they take. That's what the list is for.
- Handover: A process is supposed to go to another person or to an AI employee. They need the edges, the variants and the path for uncertainty. That's what the process profile is for.
- Understanding: A process has many decision points or passes through several stations, and nobody on the team has the whole thing in their head. That's what the flowchart is for.
One process can have all three formats. But it doesn't have to.
Format 1: the list
The list is the simplest way to visualize processes, and the one we start with. Every row is a process, every column a question. In our template, it's called the process inventory; in daily work, we call it the process map.
To begin with, these columns are enough:
| Process | Who does it today? | Trigger | How often per month | Minutes per run | Thinking or doing? |
|---|---|---|---|---|---|
| … | … | time, event or a nudge | … | … | … |
The list shows what exists, without the flow. That's its strength: in a short time, you see where time goes, which processes only start when someone asks for them and which work depends on you. And it's easy to maintain. A new row is written quickly.
Tool: a spreadsheet. You don't need more than that. How the list comes together with your team and how you choose process no. 1 from it is covered in Creating a process map: an example and choosing process no. 1.
Format 2: the process profile
The process profile, our word for a process description, shows a single process in a way that lets someone else take it over. It describes the process by five points: trigger, start, work per variant, end and report. On top of that comes a sixth part, the escalation path: what happens when whoever runs the process is unsure?
In short form, it's a table with two columns: the six parts on the left, one or two sentences about your process for each on the right.
The process profile sets the edges; click-by-click steps don't belong in it. The fine details are added during training, when someone demonstrates each variant once.
Tool: a text file or a table with two columns. The version to fill in with all the fields, and how to find the variants, is in How to document business processes: the template for handing a process to an AI employee.
Format 3: the flowchart
The flowchart shows the path through a process: step by step, with the places where the path splits. When people want to visualize a process, this is often what they mean. There are dedicated notations for it, such as BPMN, with fixed shapes for tasks, decisions and events. For a business with a team, much less is usually enough: boxes for steps, questions at the branches, arrows in between.
A flowchart pays off in three cases:
- Many decision points. When the path splits several times, it's easy to lose the thread in a text.
- Several stations. When a case goes from one person to the next, the picture shows where the handoffs are. At a handoff, things easily get left lying around.
- Disagreement about the flow. When two people on the team describe the same process differently, it helps to draw it together. Then you can see where the differences are.
Tool: a whiteboard or a sheet of paper. Once the picture is finished, write it down as numbered steps with questions in a text file. With us, the AI employee gets the flow as text, because text is easier to change and to proofread than a drawing. How to describe a flow so that it can actually be carried out is covered in Writing a process flow description: trigger, steps, variants and handoffs before someone else takes over.
Which format fits when
| What for | Format | What it shows | Tool |
|---|---|---|---|
| Overview of all recurring processes | List | what exists, who, how often, how long | Spreadsheet |
| Handing over one process | Process profile | edges, variants, escalation path, report | Text file or table |
| Understanding a branching flow | Flowchart | steps, decisions, handoffs | Whiteboard, then text |
Drawing a flowchart with your team
If you need a flowchart, don't draw it alone. Bring in the person who does the process most often today. They know the cases that aren't in any description.
- Start with the trigger. At the top goes what starts the process: a time of day, an incoming email, a phone call.
- Stop at the report. At the bottom goes who learns what at the end. If this point is missing, that's already a finding.
- Write every question as a question. At every branch, there's a question that can be answered with yes or no. If the answer is "it depends", there are variants hiding there. Those belong in the process profile.
- Mark every hesitation. Wherever the person pauses briefly while explaining, there's a decision. It belongs in the picture or in the process profile.
- Draw in the unclear case. What happens when something is missing or doesn't fit? That arrow leads to the escalation path.
After that, you copy the picture out as numbered steps. That keeps it maintainable.
Why we start with the list and rarely need the flowchart
In Owner Autonomy, the first month starts with the process map, in other words with the list. After that, your process is defined by the five points, in other words in the process profile.
We only draw a flowchart when a process branches so much that the process profile alone is no longer enough.
There are two reasons for this.
First: the list answers the most expensive question first. Which process is worth it at all? If you start with a flowchart, you put a lot of work into one process before it's clear whether it's the right one.
Second: variants don't fit well into a picture. A process with few branches is clear as a picture. A process with many case distinctions becomes unreadable as a picture. In the process profile, there's one line per variant instead: how you recognize it and what's different then. That stays readable even as the list gets longer.
The flowchart still has its place. When a case passes through several stations, it shows the handoffs better than text does. That becomes important as soon as AI employees hand a case over to each other. In Owner Autonomy, that's a goal once your first process runs on Autopilot.
What this looks like for us
At a tax advisory firm, tax assessment notices also arrive on paper. They reach the firm's inbox by email. A second AI employee checks the inbox every 30 minutes, spots the emails with paper notices and hands them over to the AI employee that also files the digital notices. Anything the filing employee can't match with certainty goes to the office team by email, and the AI employee is trained on it afterwards. At the end comes a completion email. The process is at Autonomy Level 2, Autopilot (as of September 2026).
Here is the same process in all three formats. The steps are our simplified description.
As a list
| Process | Who does it today? | Trigger | Before | Thinking or doing? |
|---|---|---|---|---|
| Filing notices that arrive on paper | two AI employees, previously the office team | schedule, every 30 minutes | up to 2 hours, depending on volume | doing |
One row is enough to see that the process used to take time, starts on a schedule and is pure doing. That's all the list is supposed to show.
As a process profile
| Point | Paper notices |
|---|---|
| Trigger | fixed schedule: a look at the inbox every 30 minutes |
| Start | new emails in the firm's inbox |
| Work | spot emails with a paper notice and hand them over; file each type of assessment according to the trained rules |
| End | every paper notice is filed or reported as unclear |
| Report | completion email |
| Escalation path | email to the office team, followed by a feedback session |
The process profile shows what whoever runs the process needs to know: when to start, when it's finished and what to do when unsure.
As a flowchart
- Schedule: every 30 minutes.
- Look at new emails in the inbox.
- Question: an email with a paper notice? No: not part of this process. Yes: hand it over to the filing employee.
- Recognize the type of assessment.
- Question: can it be matched with certainty? Yes: file it. No: email to the office team, the case stays open.
- Completion email.
The flowchart shows what the other two formats only hint at: the handoff between two AI employees and the two places where a decision is made. What it doesn't show are the variants. Behind "Recognize the type of assessment", the whole assessment notice process has around 45 rules, because there are many types of assessment and letters from the city look different. They belong in the process profile, one line per variant.
Runs without me
Every two weeks, one process that runs without the owner: what came in, what the AI did, where a person decided. Two minutes to read.
Worksheet
Process Potential Check
With five questions and a first process list to fill in, you find the process that could run on its own first. Comes as a PDF by email once you confirm your sign-up.
Strategy session
In a 20-minute strategy session, you tell us where things get stuck. We'll tell you honestly whether an AI employee is a good fit for you.
Book a strategy sessionFrequently asked questions
What software do I need for process visualization?
For the list, a spreadsheet; for the process profile, a text file; for the flowchart, a whiteboard. Programs for process models tend to pay off when many people are drawing many processes. In a business with 3 to 15 people, you're better off starting without one.
Do I have to draw every process as a flowchart?
No. Many processes only need one row in the list and, if they're handed over, a process profile. A flowchart pays off when there are many branches or handoffs between several stations.
Can an AI employee work with a flowchart?
With us, it gets the flow as text. So write the picture down as numbered steps with questions. That way, your team and the AI employee can work with the same version, and changes are quick to make.
What's the difference between visualizing a process and describing it?
The visualization is the format, the description is the content. The list, the process profile and the flowchart are three formats. What has to be in them so that someone else can run the process is decided by the content.
How do I keep the visualizations up to date?
Through the escalation path. Every unclear case that lands with your team points to a variant that's still missing. After the feedback session, it goes into the process profile as a rule. You change the list when a process is added or dropped.
The method behind it
Kevin describes the whole path on his blog in four steps: make processes visible, evaluate what's worth it, clean up first and then hand off, and finally choose the right level of automation. You can read it in Process Optimization With AI: The Method. Visualizing belongs to the first step: only once a process is visible can your team evaluate it.
Your next step
Start with the list. Once you see which process takes up the most time in your business, the process profile is the next step. On a call, we put your list on the table and look at which process deserves a process profile first.