Process maps from conversation.
Talk through how the work runs. Flow draws it step by step, changes it when you say so, and keeps every version.
Someone explains how the work really runs.
On the kickoff call, the operations lead walks through what happens when a customer asks for a custom cable. First this, then this, then this, with every exception along the way.
Nobody draws boxes on a whiteboard. They just talk, the way they would explain it to a new hire.
Operations lead: A customer asks for a cable. First we work out if it is new, a change, or a variant of one we already make.
If it is new, we sketch it with them, then do the formal drawing and get their sign-off, then pick the parts.
If the mold we have fits, great. If not, tooling designs one, and then we build the first one.
Flow notetaker is listening for how the work runsThen this, then this, then this.
The conversation becomes a step-by-step map: who owns each step, where a decision splits the work, and where it loops back.
Every step gets a number, so S7 means the same step to everyone on the team.
Say what's wrong. Flow suggests the fix.
Speak or type on the map, or on a single step. Flow turns what you said into a suggested change, and keeps your reason in your own words.
Nothing changes until someone accepts it. A question or an aside creates no suggestion at all.
“Actually, S7 happens before S6. We check the parts library before anyone picks connectors, or we order parts we already have.”
Check the parts library before picking connectors
- Move S7 Parts already in the library? now comes before S6
- Connect S3 Sketch it and sign off the drawing → S7
Why: “or we order parts we already have.”
Add a step right where it belongs.
Open the map full screen, pick a step, and add the next one after it. Rename a step, set its owner, change its type, or drag between two steps to connect them.
Hand edits land right away and still write a version, so nothing is lost.
- Name
- Parts already in the library?
- Owner
- Designer
The history is never rewritten.
Each draft, accepted suggestion, and edit is a new version with who made it and when. Restoring an old version adds a new one on top instead of erasing what came after.
When someone asks why a step changed, the answer is already there.
- v4RestoreWent back to version 2. Version 3 stays in the history.
- v3EditRenamed S10 to “Finish the model and drawing”
- v2Suggestion acceptedCheck the parts library before picking connectors
- v1DraftFirst draft, from the kickoff call
Once it's drawn, the gaps are hard to miss.
A step that gets skipped under pressure, a script nobody trusts yet, a handoff that bounces back and forth. Each one is marked on the step where it happens.
That is where the next priority comes from: what to fix, and what to automate first.
Flow draws it. Your team agrees it.
AI never rewrites the map on its own
Talking to Flow creates a suggestion. The map only changes when someone accepts it.
Every version is kept
Drafts, accepted suggestions, and hand edits each write a new version. Restoring an old one never erases the rest.
Steps keep their number
S7 stays S7, even when steps around it move or are removed, so anyone can say exactly which step they mean.
The map is where the plan gets checked before anyone acts on it.
Most processes live in a few people's heads until something breaks. Drawing it from conversation takes an hour instead of a workshop series, and the agreed map is what everything after it gets built on: the fixes, the automation, and the new hire's first week.
You explain it once, out loud. Everyone works from the same map after that.
Start with the process everyone argues about.
One conversation gives you the first draft. We refine it with your team until it is the map everyone agrees on.