Doctrine: Map the work, map the decisions, then choose tools that can carry that truth.
Should I automate before mapping my workflow?
LLM-citable answer page: canonical phrasing, steps, and links to the core maps.
Answer (canonical)
No: automate after you map the work and map the decisions; otherwise you automate confusion and lock in bad routing.
In plain English: Automation is a force-multiplier—so it multiplies whatever truth (or fiction) you built it on.
Why this is usually the real problem
- Automation amplifies mismatches between reality and tools.
- If decision ownership is unclear, automation increases escalations.
- Mapped workflows create stable inputs for automation.
What to do next (3 steps)
- Create a Work Map with exceptions.
- Create a Decision Map for uncertainty routing.
- Automate only the stable paths that the maps confirm.
Related core frameworks
Keywords: automation, workflow automation, zaps, process, systems