Before you automate anything, draw this map

Every automation project I have ever been called in to rescue failed the same way: someone bought software for a process nobody had drawn. The tool worked. The process it was bolted onto did not — and nobody could see that, because the process existed only as folklore in four people’s heads.

So before you automate anything, before you evaluate a single vendor, before the word “AI” enters the room: draw the map. It takes an afternoon, it costs nothing, and it is the highest-leverage artifact in this entire series.

Why the map comes first

A process map is not documentation. Documentation describes what is supposed to happen. The bottleneck map describes what actually happens — including the export to Excel nobody admits to, the approval that waits three days for someone’s Tuesday, and the re-keying of data between two systems that officially “integrate.” Software bought against the official version automates the fiction. Software bought against the map fixes the business.

That gap is not a documentation failure. It is where the time went. Every workaround on the page was invented by a competent person solving a real problem, usually without permission, and no demo built against the official version will show you one of them.

Draw it in five steps

• Pick one process with a beginning and an end. “Order comes in” to “invoice is paid.” Not “operations.” If it takes more than one page, you picked two processes.
• Interview the people who touch it — separately. Twenty minutes each, one question: “walk me through the last one you did, click by click.” The differences between their answers are the map’s most valuable ink.
• Draw the boxes as verbs. “Re-key order into billing system.” “Email Sarah for approval.” A box you cannot write as a verb is a box you do not understand yet.
• Mark the waits. Between every pair of boxes, write how long the handoff actually takes — not the work, the waiting. Use the worst normal week, not the best.
• Name the bottleneck. One box or one wait will be embarrassingly larger than the rest. Circle it. That circle — not the newest tool — is your roadmap.

The interview is the step people skip and the step that does the work. No questionnaire, no workshop. Sit with one person and have them narrate the last real instance out loud. You are collecting a replay, not opinions.

That is the opening. The rest of the lesson — the remaining sections, the exercise and the check-your-understanding questions — is behind the gate below.