A department identifies an opportunity to improve efficiency.

The team reviews its activities, eliminates unnecessary steps, and introduces a faster way to complete the work.

The results look promising.

Productivity increases. Turnaround time decreases. Employees spend less time completing their assigned activities.

From the department’s perspective, the improvement is successful.

But something unexpected happens.

Another department begins experiencing delays.

Information that was previously available is now missing.

Employees spend more time requesting clarification.

Additional corrections become necessary.

Work begins moving backward through the organization.

One department has become more efficient, but the overall process has become less efficient.

How does that happen?

It happens when organizations improve individual activities without fully understanding how those activities affect the rest of the workflow.

An improvement for one department isn’t necessarily an improvement for the entire process.

1. Departments Perform Activities. Processes Deliver Outcomes.

Most organizations are structured around departments.

Sales has responsibilities.

Operations has responsibilities.

Finance has responsibilities.

Customer Service has responsibilities.

Each department has its own activities, performance expectations, and management structure.

But many important business processes don’t begin and end within a single department.

Consider the process of fulfilling a customer order.

Sales receives the request.

Operations prepares and fulfills the order.

Finance handles the financial transactions.

Customer Service may address questions or concerns throughout the process.

Each department performs part of the work.

But the customer experiences the outcome of the entire process.

That’s why improving an individual department doesn’t automatically mean the end-to-end process has improved.

The activities are connected.

And changes in one area can affect what happens elsewhere.

2. A Faster Handoff Isn’t Always a Better Handoff

Imagine Sales introduces a simplified order-entry procedure.

The objective is to reduce the time required to process customer orders.

Several fields are removed from the intake form.

Employees can now submit orders faster.

Sales productivity improves.

But Operations discovers that some of the removed fields contained information needed to fulfill the orders correctly.

Now Operations must contact Sales to obtain the missing details.

Some orders sit waiting for clarification.

Others are returned for correction.

The time Sales saved during intake becomes additional work for Operations.

And depending on the circumstances, the overall order fulfillment process may take longer.

The problem wasn’t necessarily the decision to simplify the form.

The problem was simplifying the form without fully understanding what the next department needed.

A handoff isn’t successful simply because work leaves one department quickly.

It’s successful when the receiving department has what it needs to continue the work.

3. Eliminating a Step Can Create Additional Work

Process improvement often involves identifying activities that appear unnecessary.

That’s appropriate.

But before eliminating an activity, it’s important to understand its purpose.

Consider an employee who verifies customer information before sending a request to another department.

Management may view the verification as an extra step that slows down the process.

Removing it could reduce processing time.

But what if that verification prevents incomplete or inaccurate information from moving downstream?

Without it, the receiving department may experience more errors, corrections, and delays.

The eliminated activity may have served an important purpose.

That doesn’t necessarily mean it should remain unchanged.

Perhaps the verification could occur earlier.

Perhaps the information could be validated automatically.

Perhaps the source of the errors could be corrected.

The point is that an activity shouldn’t be eliminated solely because it consumes time.

Its effect on the overall process must also be considered.

4. Departmental Metrics Can Tell Only Part of the Story

Performance metrics help leaders evaluate results.

But departmental metrics may not reveal the full effect of a process change.

Suppose Sales measures how quickly orders are submitted.

Operations measures how quickly orders are fulfilled.

Finance measures transaction accuracy.

Each department is evaluated against its own targets.

Now suppose Sales reduces its order-entry time by 20%.

That’s a positive departmental result.

But if Operations experiences more incomplete orders, additional clarification requests, and increased rework, the organization may not realize the expected overall benefit.

Sales improved its metric.

Operations absorbed additional work.

And the customer may experience a longer fulfillment time.

This raises an important question:

Did we improve the process, or did we move the work somewhere else?

That’s a question worth asking whenever an improvement appears successful within one department but creates new problems downstream.

5. Moving Work Isn’t the Same as Eliminating Work

Sometimes organizations believe they’ve improved a process because one department is doing less.

But the work hasn’t disappeared.

It’s simply moved.

A department stops verifying information, and another department begins correcting it.

A team eliminates a tracking activity, and downstream employees create their own spreadsheets.

An approval is removed from one area, and another department introduces an additional review to manage the resulting risk.

One department reduces its workload while another inherits the responsibility.

That may be appropriate when the receiving department is better equipped to perform the activity.

But the change should be intentional.

Leaders should understand whether the activity has been eliminated, simplified, automated, or transferred.

Because transferring work doesn’t automatically reduce the total work required to complete the process.

6. Understand the Entire Workflow Before Changing Part of It

This is where process mapping becomes particularly valuable.

Before making a change, establish how the current process actually operates.

Identify the activities.

Understand the decisions.

Make the handoffs visible.

Clarify responsibilities.

Capture alternate paths and rework.

Most importantly, involve the people who:

• Do the work.
• Feed the process.
• Are impacted by the process.

Those perspectives matter because no single department necessarily sees everything that happens across the workflow.

The people performing an activity understand what they do.

The people providing inputs understand what happens before that activity begins.

The people receiving the outputs understand what they need to continue the work.

Bringing those perspectives together helps reveal how a proposed change could affect the rest of the process.

You can’t reliably evaluate the impact of a change if you only examine the department making it.

7. Evaluate the Impact Before Implementing the Change

Once the current process is understood and validated, leaders can begin evaluating improvement opportunities.

But before implementing a proposed change, ask several important questions.

What problem are we trying to solve?

Be specific about the condition that needs improvement.

Which activities will change?

Identify what will be eliminated, added, simplified, automated, or reassigned.

Who receives the output of those activities?

Determine whether the proposed change affects another employee, department, system, or customer.

What information does the next person need?

Make sure the change doesn’t remove something necessary for downstream execution.

Could the change create additional work elsewhere?

Consider possible delays, clarification requests, corrections, and new handoffs.

How will we know the overall process improved?

Identify measures that reflect the performance of the end-to-end workflow, not just the department introducing the change.

These questions help organizations avoid solving one problem while creating another.

8. Measure the Overall Process, Not Just the Local Improvement

Departmental performance measures remain important.

But when evaluating cross-functional improvements, leaders should also consider how the entire process performs.

Depending on the process, useful measures may include:

• Total time from process start to completion.
• Time spent waiting between departments.
• Percentage of work received complete and ready for processing.
• Number of requests returned for correction.
• Frequency of clarification requests.
• Total rework across the process.
• Customer response or fulfillment time.
• Total effort required to complete the work.

These measures can help reveal whether a local improvement produces a genuine benefit.

For example, reducing order-entry time by five minutes may sound positive.

But if the change adds twenty minutes of downstream clarification and correction, the overall process hasn’t improved.

The organization has simply shifted the burden.

The objective should be to reduce unnecessary effort across the process, not just within one department.

9. Process Improvement Requires Cross-Functional Thinking

Organizations often encourage department managers to improve performance within their areas of responsibility.

That’s reasonable.

But when the process crosses departmental boundaries, improvement decisions should account for those connections.

A change to Sales may affect Operations.

A change to Operations may affect Finance.

A change to Finance may affect Customer Service.

And a change anywhere in the workflow may ultimately affect the customer.

This doesn’t mean every small improvement requires a large committee or lengthy approval process.

It means leaders should understand the dependencies involved and include the appropriate people when a change could affect their work.

The goal is to prevent unintended consequences.

And to make sure an improvement in one area supports, rather than undermines, the performance of the overall process.

10. Improve the Process, Not Just the Department

A department can become more efficient without making the business more efficient.

That’s an important distinction.

When evaluating a proposed improvement, don’t stop at asking whether the change will make one team’s work faster or easier.

Ask what happens to the work before it reaches that team.

Ask what happens when the team hands the work to someone else.

Ask whether the change affects information quality, responsibilities, decisions, waiting time, or downstream execution.

And ask whether the total effort required to produce the intended outcome will actually decrease.

Because business processes don’t operate independently within departmental boundaries.

They connect people, activities, information, and decisions across the organization.

An improvement for one department isn’t necessarily an improvement for the entire process.

The real opportunity is to make the entire workflow perform better.

You can make one department more efficient while making the business less efficient.

Don’t mistake one for the other.

Business Process Mapping: The Foundation of Operational Excellence

Why Your Best Employees May Be Hiding a Broken Process