The People Closest to the Work Know Things Management Doesn’t

If I want to understand an operation, I want to talk to management. I want to see the reports and understand the objectives, measurements, constraints, and problems leadership believes need to be solved.

Then I want to go where the work is actually being done.

Those are two different views of the same organization.

And you need both.

The Process on Paper

Most organizations have an official process. This is how an order moves through the system. This is how inventory is received. This is how a customer issue is handled. This is how production is scheduled.

Then there is the process people actually use to get the work done.

Those two processes aren’t always identical.

That doesn’t necessarily mean employees are doing something wrong. Sometimes they’ve created a workaround because the official process doesn’t work very well.

Someone keeps a handwritten list because the system doesn’t give them information when they need it. Someone walks across the building to ask a question because the formal communication process takes too long. Someone has learned that a particular machine needs attention before the maintenance data says it does.

And someone may know which orders are likely to create trouble before the problem ever appears on a management report.

That knowledge matters.

Ask the Person Doing the Job

Consultants can make a mistake when we arrive with expertise and immediately start demonstrating it.

Managers can do the same thing.

We know systems. We know processes. We know what the reports say. But the person who has performed a particular job every day for the last ten years knows something too.

Ask them.

What makes your job harder than it needs to be? What do you spend time doing that doesn’t make sense? Where do things usually go wrong? If you could change one thing about this process tomorrow, what would it be?

Then listen.

Not every suggestion will be practical, and not every complaint identifies a real problem. Sometimes a workaround that makes one person’s job easier creates problems somewhere else in the operation.

But dismissing frontline knowledge because it isn’t expressed in management language is a mistake.

Respect Is Operational

There is something else happening when leaders ask people about their work.

We’re communicating respect.

We’re saying:

You know something I need to understand.

That doesn’t mean management abdicates responsibility for making decisions. It means those decisions are informed by the people who live with the process every day.

Some of the most useful information in an organization never makes it into a KPI. It lives in experience and repetition. It lives in the employee who knows that every Tuesday afternoon the same thing goes wrong and nobody has ever asked why.

Go See

Reports are valuable. Data is essential. Management perspective matters.

But none of them eliminates the need to go see the work.

Walk the floor. Watch the process. Ask questions. Talk to the people doing it.

And don’t ask questions merely to confirm what you’ve already decided. Be prepared to discover that the operation works differently than you thought it did.

The people closest to the work don’t know everything.

Neither does management.

Neither does the consultant.

That’s why good improvement work brings those perspectives together.

Before changing someone’s process, understand their process. And one of the best places to begin is remarkably simple:

Ask the person doing the job.