Map the task’s journey before trying to speed it up

Map the task’s journey before trying to speed it up

A customer orders a service. Their request passes through an email, a spreadsheet, another email, and finally a phone call to the person who will do the work. Along the way, someone enters the same information twice. Employees are busy, but tasks move slowly. If you look only at individual performance, you won’t see how much work is created by the way information is handed over.

Choose a recurring task and write down what actually happens from the moment it comes in to when the result is handed over. Don’t try to draw the ideal process. Record who receives what, what they produce, and where they send it next. At each step, ask: “What value does this add? Who needs it? What would happen if we simplified it?” Some checks are essential for accuracy or safety; others may be there only out of habit.

Then look for common sources of unnecessary work: duplicate data entry, avoidable waiting, repeated corrections, or handoffs without a clear owner. Before removing a step, check what it actually does. Sometimes it protects against an error that isn’t immediately obvious. Simplifying too quickly may just move the problem further along.

To test an improvement, choose one step where the same information is entered twice. Find out whether one verified record could serve both purposes. Also keep an eye on the consequences. The goal of mapping isn’t to create a pretty diagram; it’s to understand where value is created and where there’s just more activity.

The same information is manually entered in three places in a process. What should you do first?

Efficiency in Practice: Fewer Unnecessary Steps, More Real Value

Continue the training

Enter your email address to continue the training.