Process Mapping Before You Add AI
Map how work really flows, find where time and errors go, then decide if AI belongs there
A taste of a lesson
Our customer refund process takes about a week. My boss thinks AI could speed it up. Where would you look first?
I would map it before deciding anything. Write down every step from the refund request arriving to the money reaching the customer, who does each one, and how long work sits waiting between steps. In many processes the week is mostly waiting, for example a request sitting in one person's queue for an approval, and that is fixed with a rule or delegation, not AI. AI might help later with reading messy requests. Try this: list the first five steps and guess where the longest wait happens.
Written by the teacher as an example. In your lesson the tutor answers your own questions, and like any AI it can be wrong.
What you will be able to do
- Map a real process from trigger to outcome with steps, decisions and handoffs
- Record time, waiting, error rates and workarounds for each step
- Identify steps to remove or simplify before considering automation
- Sort remaining steps into rules, templates, AI assistance or human judgment
- Set a baseline and plan a small test of the first improvement
Lesson plan
- 1 What a process is Describe a process as a trigger, steps, decisions, handoffs and an outcome. Start
- 2 Mapping the current state Draw how the work is really done, not how the manual says it is done. Start
- 3 Measuring where time goes Record working time, waiting time, volume and errors for each step. Start
- 4 Remove before you automate Find steps to eliminate, simplify or standardise before adding any tool. Start
- 5 Where AI fits and where it does not Sort steps into rules, templates, AI assistance or human judgment. Start
- 6 Testing the first change Plan a small, measured test of one improvement against your baseline. Start
Try asking
About this tutor
For operations staff, team leads and small business owners who have been asked to 'add AI' to a process. Most failed automation projects automate a process nobody fully understood. This free tutor teaches you to map a real process step by step, from trigger to finished outcome, including handoffs, waiting time, rework and the informal workarounds people rely on. You learn to measure where time and errors actually go, to spot steps that should be removed rather than automated, and to sort the remaining steps into those suited to rules, templates, AI assistance or human judgment. You finish with a simple map, a short list of candidate improvements and a way to test the first one.
Reviews
4.7
3 ratingsSample
- Ana G.Sample
Free and genuinely useful. The 'and then what happens' questions made me realise how many workarounds my team uses.
- Fatima Z.Sample
We mapped our purchase order process and found an approval step that nobody remembered the reason for. Removed it. No AI involved, which was exactly the point.
- Patrick H.Sample
Simple and clear. The waiting time idea was new to me. I would have liked a few more example maps to compare mine against.
About the teacher
Operations teaching: map the process first, then decide where AI earns a place
9 tutors 412 lessons taught Sample
I teach operations people how to improve real processes with AI, carefully. I come from operations and supply chain roles where a small error in a spreadsheet could mean a late shipment or a wrong payment, so I teach with a strong habit of checking. We map the process before touching any tool, measure where time and errors actually go,...
See Takeshi's profile and tutorsMore like this
Other tutors on the same or nearby topics.