Map Before You Buy

Follow one real piece of work

A demo can show what a tool does. It cannot tell you whether your business needs it. Before comparing software, follow an order, a quote, or a service request from arrival to completion.

Ask the people doing the work to help. Explain that the purpose is to improve the process, not to monitor or rank individuals. Use task descriptions rather than customer or employee details.

Ask four questions at every step

Where does the work arrive from? Name the trigger: an email, a phone call, a form, or another person.

Who touches it? Record each handoff and who owns the outcome. Work can cross several desks without anyone owning it from start to finish.

What are they waiting on? Separate active work from waiting for information, approval, or a correction. A faster draft will not fix an unclear decision.

How do we know it is done? Describe an acceptable result and who checks it. Producing an answer is not the same as completing the job.

Delete, simplify, then consider automation

The map may reveal a step that no longer needs to exist. It may point to unclear ownership, a missing field, or repeated work your existing software could handle. AI is one possible response, not the required conclusion.

Bring the map back to the team before choosing the next step. For a first AI-assisted task, look for a bounded job with usable inputs, clear exceptions, and an output a person can check.

Measure the whole job

Record the current time spent. During a trial, include checking, corrections, and maintenance in the new total. Compare a similar mix of work rather than only the easiest examples.

Time made available is not automatically cash saved. Its value depends on what people can do with it and what the new process costs. Start with the Floor Walk worksheet, then take your map to a vendor with a clear question: which part of this job should change, and why?