Article

The Tool Changed. Did Anyone Explain the Job?

The tool might work exactly as advertised. The job can still fall apart around it.

Share card: The Tool Changed. Did Anyone Explain the Job?, white and orange type on a dark textured plate, BigBeardedGinger.com

A new tool arrives. Somebody gives a demonstration. The team gets a login, a new screen, and a date when the old way stops working.

The project is called complete.

Then the questions start.

Who makes the call when the tool and the customer disagree? Who owns a mistake nobody could make before? What still needs a person to check it? What does good work look like now?

The tool might work exactly as advertised. The job can still fall apart around it.

There is a difference between showing someone how a tool works and explaining how their work changes. Too many leaders finish the first part and mistake it for the second.

THE NUMBER IS NOT THE WHOLE STORY

Gallup reported on October 28, 2026 that U.S. employee engagement fell to 29% in the third quarter, down from 31% in the first half of the year. The same report found that the share of employees who strongly agreed they knew what was expected of them fell from 49% to 46%. The share who strongly agreed someone at work cared about them as a person fell from 40% to 37%.

Those are Gallup survey measures, not a diagnosis of every workplace. The decline was sharper among remote and hybrid employees, particularly in organizations adopting AI. That does not prove AI caused the decline. It does put a useful question on the table.

Are leaders changing the work faster than they are helping people understand it?

That question is older than artificial intelligence.

It was there when somebody brought in the first computer instead of a paper form. It was there when schedules moved to an app, when customers started checking themselves out, and when a machine started making decisions that had belonged to an experienced operator.

There is always a new tool. There is not always a clear agreement about the job that surrounds it.

A login tells someone they have access. It does not tell them they have authority.

THE DEMONSTRATION IS NOT THE HANDOFF

Picture a small service business adopting scheduling software.

The trainer shows how to enter a job, move an appointment, and send a confirmation. Everybody follows along. The demonstration goes well.

On Tuesday, a customer calls with an exception. The software has one answer. The dispatcher knows something the software does not. The owner is unavailable. The customer is waiting.

Should the dispatcher override the system? Call the owner? Tell the customer no? Leave the slot open?

Nothing in the demonstration answered that question.

So the dispatcher makes a reasonable guess. Another employee makes a different reasonable guess. By Friday, the business has two ways to handle the same problem and no clear owner for sorting them out.

The training was fine. Nobody decided who makes the call.

The business taught the buttons but left the boundaries unwritten.

WHEN THE WORK CHANGES, IDENTITY CHANGES TOO

The person who used to catch bad orders by memory might now be told the system will catch them. The team lead who knew every handoff might now see a dashboard that calls the work complete while someone is still fixing it.

That person is not always fighting progress.

They might be asking a reasonable question: where does my judgment fit now?

People want to know they can do the job well. They want some say in how they do it. They want to belong to a group that would notice if they were missing.

Check the rollout against those three needs.

Competence: Does the person know what good work looks like in the new system?

Autonomy: Can the person still make the decisions they are responsible for, or has every ordinary call moved into a queue?

Relatedness: Is there still a person who listens when the new process makes work harder?

A tool can help all three. A careless rollout can make all three feel weaker.

If you take an experienced person’s judgment out of the job, do not act surprised when the person stops acting like an owner.

You might have changed a task. They might have heard that their experience no longer counts.

SOME LEADERS CALL THAT RESISTANCE

Resistance is an easy label because it makes the problem somebody else’s attitude.

Sometimes the label fits. People can prefer the old way simply because it is familiar. A new method can expose poor habits that were easier to hide under the old one.

But before calling somebody resistant, ask what the new process actually requires from them.

Do they know who approves an exception?

Do they know what to do when the tool gives an answer they can show is wrong?

Do they know whether they are measured on speed, accuracy, customer experience, or a combination?

Do they have a way to report a failure without being treated like the failure?

If the answers are missing, you do not have a resistance problem yet. You have an unfinished handoff.

A manager who refuses to name the rules cannot fairly accuse the team of refusing to follow them.

THE THREE GAPS THAT KEEP SHOWING UP

The first gap is the decision gap.

The new process changes who sees information, but nobody agrees on who is allowed to act on it. Everyone can spot the problem. Nobody can close it.

The second gap is the standard gap.

Leaders announce that work will be faster and more accurate. They never show what counts as done. Employees begin measuring themselves against whatever the screen rewards, even when the customer or the next person in line needs something else.

The third gap is the feedback gap.

A new tool will get something wrong. A handoff will be awkward. A rule that made sense on a slide will break against an ordinary day. If the people who find those problems have nowhere useful to send them, the defects become workarounds. The workarounds become normal. Leadership sees a rollout that worked while the team carries the hidden labor.

The trouble with a quiet rollout is not that nothing went wrong.

It is that the people who found the problems stopped bringing them back.

CHANGE THE JOB ON PURPOSE

The better approach does not require another committee or a stack of training binders.

Before the rollout, write a short agreement with the people who will use the tool. Put five things on one page.

What changes. Name the task or decision the tool now handles, in ordinary language.

What stays human. Name the judgment, service, relationship, or quality call that remains with a person.

Who decides an exception. Name one role with authority to make the call, not a vague instruction to escalate.

What done means. Describe the result the next customer or teammate should receive. A green status light is not enough.

Where failures go. Name one place to report a problem and one person responsible for closing the loop.

That is the handoff.

Now ask someone who was not in the planning meeting to read it back. If they cannot explain what they own, the document is not finished.

Do not blame the reader. Fix the instruction.

THE TEN-MINUTE TEST

You do not have to wait for a major technology launch.

Pick one tool, rule, schedule, or process that changed recently. Sit with the person who uses it most and ask: “Where does the new way make you guess?”

Let the person walk you through a real exception. Do not interrupt with the reason leadership chose the tool.

Write down the point where the work becomes uncertain. Then finish one sentence together: “When this happens, this role makes this call, using this standard.”

Try that rule during the next normal work period. Check the result with the same person. If the rule fails, fix it before you roll the lesson into everybody else’s day.

The entire point is to move one decision out of the fog.

If you have ten minutes for a progress meeting, you have ten minutes to clear up a decision people keep guessing about.

THE OBJECTION: WE CANNOT EXPLAIN EVERY EDGE CASE

Correct.

Nobody can map every possible exception in advance. Trying would create a rulebook so thick that nobody could use it.

That is not what this calls for.

You are not promising that nothing unexpected will happen. You are making clear who owns the unexpected when it does.

A good system has a standard for routine work and a route for the surprise. A poor system has a standard for presentations and a search party whenever reality disagrees.

The difference is not more control.

It is clearer authority.

A strong manager does not need to make every decision. They need to make it obvious where each decision belongs.

THE WORK IS BIGGER THAN THE SCREEN

The same mistake shows up outside a company.

A school introduces a parent portal, then families have to guess whether a message in the portal replaces a conversation with a teacher. A volunteer group moves assignments into an app, then nobody knows who takes over when someone gets sick. A household creates a shared calendar, then members assume the calendar itself will settle conflicting needs.

The tool holds the information. People still own the relationships.

A calendar cannot have a hard conversation. A dashboard cannot apologize to a customer. An automated summary cannot decide what is fair in a situation it was not built to understand.

Those things require judgment, clarity, and a person willing to take responsibility.

This is not an argument against technology. It is an argument against making technology carry leadership’s unfinished work.

WHEN A ROLLOUT IS REALLY WORKING

Do not judge a change only by the number of accounts created, screens opened, or hours of training completed.

Look for a cleaner result.

Can someone explain the new standard without calling the supervisor?

Does the person handling the exception have the authority to act?

Does a reported problem get an answer back?

Can the next person in the process trust the work that reaches them?

Are you removing work or simply moving it where your dashboard cannot see it?

The answers tell you whether the new tool is part of a working system or just another thing people have learned to work around.

There is a cost to making people guess. They spend time checking with others, waiting for permission, repeating work, and protecting themselves from blame.

The cost is real even when it never appears as its own line on a report.

A company can give everyone a smarter tool and still ask them to work in a dumber system.

YOUR NEXT MOVE

On your next shift, pick one change that is already in place. Find the person closest to the work. Ask where the new process forces them to guess.

Write one clear decision rule with that person. Make sure they know what they can decide and when they should stop and ask.

Then check whether the rule helped on the next shift.

The point is not to slow down new technology. The point is to stop treating a software launch as proof that people understand their work.

If you change the tool, own the translation.

The job will not explain itself.

SOURCES AND RESEARCH LIMITS

Jim Harter, Gallup, “U.S. Employee Engagement Below 30% for First Time in 15 Years,” October 28, 2026. Original Gallup reporting and trend tables: https://www.gallup.com/workplace/716117/employee-engagement-below-30-first-time-years.aspx

News trigger: Peter Saalfield, Fast Company, October 29, 2026, reporting Gallup’s October 28 release: https://www.fastcompany.com/91632505/employee-engagement-in-u-s-hits-lowest-point-in-15-years