Tool Support

Picture a team trying to do good work, but the tools around the work keep getting in the way.

The system requires information from three different places. The form asks for details people don’t have yet. The template is outdated. The report is missing the one thing people actually need. The handoff depends on memory instead of a clear process.

So people start building their own fixes.

One person creates a spreadsheet. Someone else keeps a private tracker. Another person saves screenshots. Someone else uses an old version of the template because it works better.

For a while, that can look like resourcefulness.

People are adapting. They’re solving problems. They’re keeping the work moving.

But when the workaround becomes the workflow, the work gets harder than it needs to be.

People spend more time searching, re-entering, checking, correcting, chasing, and translating information from one place to another.

Have you ever been in a situation where the official tool existed, but the real work happened somewhere else?

Maybe people had to enter the same information in multiple places.

Maybe the system didn’t match the real workflow.

Maybe the job aid was outdated.

Maybe everyone had their own version of “how we do this.”

Maybe the official tool existed, but nobody trusted it enough to use it.

That is Tool Support.

Tool Support asks whether the systems, processes, job aids, templates, handoffs, and information sources actually make performance easier.

Because when tools don’t support the work, people don’t just lose time. They lose accuracy, consistency, confidence, and capacity.

When Tool Support is affecting performance, the issue may look like people are disorganized, inconsistent, or slow.

But sometimes the work is slow because the tools around the work are making it harder than it needs to be.

You may see duplicate work.

People enter the same information in multiple places, keep side trackers, or rebuild reports manually because the official system does not give them what they need.

You may see inconsistent processes.

One person uses the new template. Someone else uses the old one. Another person has their own spreadsheet. Over time, the team ends up with several versions of “how we do this.”

You may also see delays caused by searching, checking, correcting, or waiting for information.

That matters because the delay is not always in the task itself. Sometimes the delay is in everything people have to do around the task to make the tool usable.

Tool Support issues can also create errors and rework.

If information is hard to find, easy to enter incorrectly, or stored in too many places, people are more likely to miss details, use outdated information, or make decisions from an incomplete picture.

So when you see these outcomes, don’t only ask, “Why aren’t people following the process?”

Ask the better question:

Is the process actually helping people do the work well?

If Tool Support may be affecting your performance issue, start with the actual path of the work.

What tools, systems, forms, templates, checklists, reports, dashboards, handoffs, or job aids do people use to complete the work?

Then look at where people are creating workarounds.

That is one of the clearest signals. If people are using private spreadsheets, screenshots, side notes, copied emails, old templates, or informal trackers, ask why. Usually, they are compensating for something the official tool does not provide.

Next, look at where information gets lost, duplicated, delayed, or translated.

Do people have to enter the same thing twice? Do they have to pull information from several places? Does the system match the real workflow? Is the report giving them the information they need at the point they need it?

Also examine whether the tools are trusted.

If the checklist exists but no one uses it, ask why. If the dashboard exists but people keep their own numbers, ask why. If the template exists but everyone edits around it, ask why.

Finally, look at whether the tool reduces effort or adds effort.

That’s the practical test. Good tool support makes the right work easier, clearer, and more consistent. Weak tool support creates extra steps, hidden labor, and more chances for error.

Tool Support is not solved by telling people to “use the system” if the system does not support the work.

It is addressed by improving the tools, processes, job aids, handoffs, and information sources so people can perform with less friction.

That’s the lens I want you to use when you move into the Tool Support section of the estimator.

As you answer the Tool Support questions in the Performance Leak Estimator, think about the tools, systems, forms, templates, reports, job aids, handoffs, and information sources connected to that issue.

The question here is not just, “Do people have a tool?”

The better question is, “Does the tool actually help them do the work well?”

Look for places where people are working around the system instead of through it. Are they keeping side spreadsheets? Re-entering the same information? Using old templates? Saving screenshots? Chasing information from multiple places? Depending on memory because the process is not clear enough?

Also pay attention to the people doing the work.

What are they complaining about? Where do they say the process slows them down? What do they avoid using? What do they say they have to double-check, re-enter, chase down, or fix after the fact?

Those complaints may not be negativity. They may be signals that the tool, system, handoff, or information source is creating friction.

This is not about blaming people for being inefficient. It’s about noticing whether the work has unnecessary friction built into it.

Take a few minutes to complete only the Tool Support section. Answer based on what is actually happening in your situation, not how the process is supposed to work on paper.

When you’re done, stay on that section. We’ll come back together before moving on.