Mapping Your Processes
You can't automate what you can't see. Let's make the invisible visible.
What You'll Learn
- How to document a process without overcomplicating it
- The input-action-output framework for any task
- How to score processes for automation potential
- Building your first process map
The Input-Action-Output Framework
Every process, no matter how complex, breaks down into three parts: something comes in (input), something happens to it (action), and something comes out (output). An invoice arrives, you verify the numbers, you approve it. A customer asks a question, you find the answer, you send a reply.
When you map a process this way, automation opportunities jump out at you. Any step where the action is predictable and the rules are clear? That's automatable.
The 5-Step Process Audit
Step 1: Pick one process you do at least weekly.
Step 2: Write down every single step, even the ones that feel obvious. "Open email" counts. "Click the link" counts.
Step 3: Mark each step as either decision (requires judgment) or mechanical (same every time).
Step 4: Note where data moves between tools — email to spreadsheet, form to database, chat to task board.
Step 5: Score the process: frequency (daily/weekly/monthly) × time per run × number of mechanical steps. Higher score = higher automation priority.
Mapping a Real Process
Process: Weekly client report
Steps:
1. Pull analytics data from dashboard (mechanical)
2. Copy numbers into spreadsheet template (mechanical)
3. Write summary paragraph (decision — AI can assist)
4. Add client-specific notes (decision)
5. Export as PDF (mechanical)
6. Email to client (mechanical)
Result: 4 of 6 steps are fully automatable. Step 3 is AI-assistable. Only step 4 truly needs you.
What People Get Wrong
The biggest mistake is trying to automate your most complex process first. Start with the boring stuff — the processes so routine you could do them half asleep. Those are the ones where automation delivers immediate, obvious value and teaches you the fundamentals without high stakes.
The second trap: skipping the map entirely and jumping to tools. Tools change. Your understanding of your own processes is forever.
Try It Now
Map one of your weekly processes using the Input-Action-Output framework.
Pick a task you do every week. List every step from start to finish. For each step, write: [Input] → [Action] → [Output] and mark it as "mechanical" or "decision."
Process Mapping — Match Each Concept
Tap one on the left, then its match on the right
The 5-Step Process Audit
Process Audit Steps — In Order
Arrange the five audit steps in the correct sequence