A department misses its performance target.

Where do leaders usually look first?

Inside the department.

They examine staffing. Productivity. Training. Workload. Procedures. Individual performance.

Those are reasonable places to investigate.

But what if part of the problem isn’t inside the department at all?

What if the department’s performance is being affected by how work reaches it, what happens when work leaves it, or what occurs between departments?

That’s where cross-functional process friction becomes important.

Departments are measured vertically. Processes run horizontally.

And sometimes improving the horizontal flow is exactly what improves the vertical metrics.

Departmental Performance Doesn’t Exist in Isolation

Departments have their own responsibilities, employees, managers, goals, and performance measures.

Operations may track cycle time.

Finance may track accuracy.

Customer Service may track response time.

Sales may track conversion or follow-up activity.

Those metrics are assigned to individual departments, but the work producing those results may travel through several departments.

That means a department can be accountable for a metric while being dependent on activities that occur outside its organizational boundary.

Your Department’s KPI May Depend on Another Department’s Process

Imagine Operations is measured on turnaround time.

The Operations team may work efficiently once it receives everything needed to begin.

But what if requests frequently arrive from Sales with missing information?

Operations has to stop.

Someone contacts Sales.

Sales finds the information.

The request comes back.

Then Operations can continue.

From a measurement standpoint, Operations’ turnaround time may have increased.

But the source of that additional time wasn’t necessarily an Operations activity.

It was friction in the cross-functional workflow.

The same pattern can appear throughout an organization.

Finance accuracy may depend on the quality of information created upstream.

Customer Service response time may depend on how quickly another department provides status information.

Sales follow-up workload may increase because downstream fulfillment problems generate additional customer questions.

The department owns the metric.

But it may not own every condition influencing the metric.

Handoffs Can Affect Departmental Results

Every time work moves from one department to another, something has to transfer.

Information.

Responsibility.

Documentation.

Approval.

Customer requirements.

System data.

Or simply knowledge that the work is ready for the next person.

If that handoff isn’t clear, the receiving department may spend time figuring out what should have arrived.

Employees may chase missing information.

They may clarify requirements.

They may correct errors.

They may wait for responses.

They may create workarounds.

Those activities consume departmental capacity even though they may not be part of the department’s intended work.

And eventually that additional effort can show up in the department’s metrics.

Different Definitions of “Complete” Create Friction

One department may consider its work complete when something has been sent.

The receiving department may consider the handoff complete only when everything required to begin work has been received.

Those aren’t necessarily the same thing.

Sales may say:

“We sent the order to Operations.”

Operations may say:

“We received it, but we can’t start because information is missing.”

From Sales’ perspective, the work moved forward.

From Operations’ perspective, it didn’t.

This is why cross-functional process mapping needs to examine the workflow from both sides of the handoff.

What does the sender believe it must provide?

What does the receiver actually need?

What determines that the work is ready?

Who owns the next action?

When those expectations don’t match, friction develops between the departments.

Local Improvement Has Limits

Suppose a department is missing its cycle-time target.

Leadership responds by improving procedures within that department.

Employees receive additional training.

Internal activities are streamlined.

Responsibilities are clarified.

Those changes may help.

But if a significant portion of the delay is caused by incomplete inputs, upstream waiting, or cross-functional handoffs, improving only the department’s internal activities may not solve the entire problem.

The team can become more efficient at processing the work once it is ready while continuing to lose time waiting for the work to become ready.

That’s why departmental improvement and process improvement aren’t always the same thing.

Sometimes you have to look beyond the department to improve the department.

Follow the Process Horizontally

When a departmental metric isn’t where you want it to be, don’t stop your investigation at the organizational boundary.

Follow the work.

Where does it begin?

What happens before it reaches the department?

What information is required?

Where does the department receive the work?

What causes it to wait?

What gets returned?

What requires clarification?

Where does responsibility change?

What happens after the department completes its portion?

Mapping the workflow horizontally can reveal conditions that aren’t visible when performance is examined only through the organizational chart.

Measure the Friction Too

Departmental KPIs tell you what happened to departmental performance.

Process measures can help explain why.

Depending on the workflow, useful measures might include:

Percentage of incoming work that is complete and ready
Number of requests requiring clarification
Time spent waiting between departments
Frequency of work returned upstream
Rework caused by missing or inaccurate information
Handoff acceptance or rejection rates
Time between one department completing its activity and the next department beginning

These measures don’t replace departmental KPIs.

They provide additional context for understanding them.

A department may discover, for example, that its internal processing time is acceptable while a significant portion of total cycle time occurs before the department can begin its work.

That’s a very different improvement problem.

Improving the Process Can Improve the Department

Cross-functional process improvement isn’t about finding another department to blame for poor performance.

It’s about understanding the conditions under which departments depend on one another.

When those dependencies become visible, teams can improve them together.

Better information upstream can reduce downstream rework.

Clearer handoff requirements can reduce waiting.

Better ownership can reduce follow-up.

Earlier checks can prevent problems from traveling farther through the workflow.

Clear definitions of “ready” and “complete” can reduce confusion between departments.

The result can be a better end-to-end process and better performance within the departments participating in it.

Look Beyond the Department

When a departmental metric is underperforming, examine what is happening inside the department.

But don’t automatically assume that’s where the entire problem exists.

Ask:

What happens to the work before it gets here?

What happens when the work crosses into this department?

What dependencies affect our ability to perform?

What happens after we hand the work to someone else?

Because departmental performance doesn’t occur independently of the processes connecting the organization.

Departments are measured vertically. Processes run horizontally.

And improving the horizontal flow can improve the vertical metrics.

Business Process Mapping: The Foundation of Operational Excellence

Process Mapping vs SOPs: What Growing Companies Get Wrong