Improving Operations Without Adding Complexity

When work feels slow, the instinct is often to add something: a new tool, a new meeting, a new report. Sometimes that helps. More often it adds another place where information has to be entered and another thing to remember.

Start by tracing one piece of work

Pick a task that happens regularly, such as taking a customer request, preparing a quote, or closing out a job. Follow it from beginning to end and write down each step, each handoff, and each wait. The slow parts are usually obvious once they are written down.

Look for repetition and waiting

Two common patterns appear. The same information is entered or checked in more than one place. Or work sits idle because it is waiting for a person, an approval, or an answer. Both are candidates for simplification without any new software.

Remove before you add

For each step, ask what would happen if it were skipped. If the answer is that nothing important would change, remove it. If a step exists to catch a specific kind of mistake, consider whether the mistake can be prevented earlier instead.

Write the simpler version down

A process that exists only in people’s heads changes slightly with every person. A one-page description of the simplified steps, who does each, and what done looks like makes the improvement last.

Operational improvement is rarely dramatic. It is a series of small removals that leave the same work taking fewer steps and fewer questions.