Everyone Met Their Targets. Except the Company.

Published:

How successful departments can collectively produce a poor business result—and why manufacturing profitability requires more than individual KPIs.

By Carsten Knappe-Finger
Graduate in Business Administration (Dipl.-Betriebswirt)

A Company Full of Winners

It should have been a good day. Sales had won an important contract. Procurement proudly reported a reduction in purchase prices. Engineering had stayed within its allocated hours. Manufacturing had improved output per labour hour. Project management confirmed that every report had been delivered on time.

Every department had done its homework. Someone could almost have suggested a celebration.

Then the controller entered the room.

“Ladies and gentlemen, the project is forecast to make a substantial loss.”

Silence. Sales looked at Procurement. Procurement looked at Engineering. Engineering looked at Manufacturing. Manufacturing looked at Project Management.

Eventually somebody asked the obvious question: “So who failed to do their job?”

The uncomfortable answer was: perhaps nobody.

A company full of winners. Apparently, the bottom line had forgotten to participate.

The Difference Between Local Success and Business Success

How can a company lose money when its departments are successful? Because the success of a function is not automatically the success of the enterprise.

Sales is asked to win orders. Procurement is expected to lower purchasing costs. Engineering must limit design hours. Manufacturing should increase utilisation and productivity. Project managers are expected to deliver against budgets and schedules.

None of these objectives is inherently wrong. The difficulty begins when they are pursued independently, with insufficient attention to their combined consequences.

A cheaper component may require expensive modifications. A saved engineering hour may create several days of rework on site. An attractive contract may be commercially unsound from the day it is signed.

The individual metric improves; the project result deteriorates.

The problem is not that managers measure performance. It is that they sometimes mistake a collection of departmental measures for a measure of enterprise performance.

A dashboard full of green indicators can coexist with a project that is deep in the red.

Green, it turns out, is not an accounting principle.

Procurement Saves. Installation Pays.

Consider a hypothetical industrial plant project.

Procurement identifies a supplier offering a technically plausible alternative at a significantly lower purchase price. The saving is recorded, perhaps even highlighted in the next management report.

But the alternative requires adjustments to the drawings, changes in installation sequences and additional work at the construction site.

An interface that looked insignificant in the purchase order turns out to matter greatly during assembly.

Procurement has achieved its target. The project has acquired additional costs.

The saving receives applause. The consequences receive a cost centre.

This does not mean procurement should never negotiate aggressively or seek alternatives.

It means the relevant question is not simply:

“How much cheaper is the component?”

But rather:

“What is the total economic consequence of choosing it?”

That requires input from Engineering, Manufacturing, Installation and Project Management before the decision is locked in.

The same principle works in reverse. An engineer who specifies the most elegant solution without considering supply, manufacturing and maintenance may be locally excellent and commercially unhelpful.

Functional optimisation is useful only when it supports the overall project objective.

The Contract That Was Won Before It Was Lost

Sales teams face a particular version of this dilemma.

Winning an order is visible and easy to celebrate. The financial consequences of an incomplete scope definition or optimistic assumptions may emerge months later.

A contract can appear successful when measured by order intake while already carrying risks that make profitable execution unlikely.

This does not make Sales the villain. It illustrates why the commercial assessment of an offer must be a shared responsibility.

The crucial questions belong before the signature:

  • Are quantities and technical interfaces understood?
  • Have installation conditions been considered?
  • Are exclusions and assumptions clear?
  • Does the schedule reflect reality?
  • Are the proposed margins adequate for the risks being accepted?

If these questions are postponed until the first project review, the organisation may achieve an impressive feat: explaining with great precision a loss that it could have prevented earlier.

The monthly report will be accurate. Unfortunately, accuracy after the event is not the same as control before it.

More Productivity, Less Profit

There is an even more surprising case: productivity improves while profitability declines.

Manufacturing produces more units per hour. Downtime falls. Processes become faster. The operational improvement is real.

But what if the company is becoming more efficient at producing items or delivering projects that generate insufficient contribution?

What if the bottleneck has moved elsewhere?

What if extra output increases inventory, working capital or the cost of correcting defects downstream?

Productivity is a relationship between input and output. Profitability depends on whether the output creates sufficient economic value.

The two are connected, but they are not interchangeable.

Imagine a driver proudly announcing lower fuel consumption while travelling at speed in the wrong direction. The efficiency figure is excellent. The destination is getting further away.

At the next service station, at least there will be a beautiful chart.

That is why I distinguish productivity improvements from economic effectiveness.

Not every loss problem is a productivity problem. Sometimes it is a problem of purpose.

The Hidden Price of Handovers

Industrial projects are particularly vulnerable because their outcomes depend on interfaces.

The quotation becomes a contract. The contract becomes engineering work. Drawings become purchasing decisions. Deliveries become installation tasks.

Each handover transfers information, assumptions and risks.

If one function optimises its own result while passing the consequences to the next, the overall project absorbs the difference.

The costs may appear far away from the original decision, making it difficult to see the connection.

A company can then spend weeks debating which department “caused” a variance.

The more productive question is whether the decision process allowed the full consequences to be understood before the choice was made.

A useful management report should therefore do more than display isolated achievements.

It should connect a claimed saving with any related cost, delay or risk elsewhere in the value chain.

A purchase-price reduction is not a project saving until its total effect is understood.

A reduction in engineering hours is not necessarily an improvement if installation work increases as a result.

The accounting entries may be separate. The economic reality is not.

The Conversation Before the Offer: How MGD Improved Estimation Accuracy

During my years in international machinery and plant engineering, I repeatedly encountered the importance of getting relevant functions to examine assumptions together before an offer was submitted.

One practical approach is what I call the quantity-structure review, or Mengengerüst-Durchsprache (MGD).

Sales, Engineering, Manufacturing, Assembly, Estimating and Purchasing examine the scope, quantities, assumptions and interfaces together.

The objective is not to let each department defend its own figures.

It is to determine whether those figures form a coherent and economically viable project.

In my industrial project experience, systematically introducing these structured cross-functional reviews helped reduce deviations between preliminary and final calculations from approximately 20% to below 3%.

These improvements were documented over several years through internal calculation tracking records, known as MAK lists.

A typical MGD meeting required approximately two hours.

The important change was not the introduction of a new calculation method.

It was bringing the relevant departments together early enough to identify differences in assumptions, quantities and responsibilities before those differences became costly project deviations.

The mechanism is straightforward.

A question asked before submission can expose an omitted quantity, an unrealistic assumption or a costly interface.

Once the contract is signed, the same discovery may become a budget deviation, a change dispute or a loss.

These results reflect my practical industrial experience and should not be interpreted as a guarantee that every organisation will achieve the same improvement.

The approach does not necessarily require another layer of bureaucracy.

It requires the right people, prepared questions and permission to challenge assumptions across departmental boundaries.

My guiding phrase is simple:

Estimating is communication.

Why Incentives Can Make the Problem Worse

Targets do not merely measure behaviour; they influence it.

If a manager is rewarded for purchase-price reductions regardless of downstream cost, the organisation should not be surprised when purchase-price reductions dominate decisions.

If Sales is celebrated for volume without sufficient regard to contract quality, the signal is equally clear.

This is not an argument against bonuses or departmental accountability.

It is an argument for asking what those mechanisms actually encourage.

A more useful performance discussion distinguishes between a function’s contribution and the project’s final outcome.

It asks whether local decisions created value for the whole enterprise, whether risks were transferred invisibly and whether managers raised concerns even when doing so made their own numbers look less attractive.

There will always be trade-offs.

A slightly higher purchasing price may reduce installation hours.

Additional engineering effort may prevent expensive rework.

A lower order intake may be preferable to a portfolio of contracts that cannot be delivered profitably.

Good management makes these trade-offs visible.

Bad management gives each department a trophy and sends the invoice to the project.

POWER: Start With the Shared Purpose

This is where my POWER framework becomes relevant.

POWER stands for:

  • Purpose: Establish a common economic objective before optimising individual functions.
  • Organisation: Enable collaboration rather than protecting departmental boundaries.
  • Wisdom: Use knowledge and experience distributed throughout the business.
  • Execution: Turn decisions into coordinated actions.
  • Responsibility: Own the consequences of decisions, not merely activities recorded on a departmental scorecard.

Purpose comes first for a reason.

Before improving the efficiency of individual departments, leaders must understand whether those departments are working toward the same economic result.

Think of five rowers delivering personal best performances while each pulls in a different direction.

Everyone works hard. Everyone can show evidence of effort.

Yet the boat remains beside the jetty.

The solution is not to demand that everyone row faster.

It is to agree where the boat should go.

This may sound obvious. But organisations frequently invest heavily in improving the speed of individual activities while giving far less attention to whether those activities serve the same purpose.

Four Questions Worth Asking Before Celebrating

Managers do not need to abolish departmental indicators. They need to place them in context.

Four questions can help.

1. What has actually improved for the project or company?

A reported saving should survive an examination of its full consequences, rather than merely improving one departmental scorecard.

2. Which other functions will bear the effects of this decision?

If nobody outside the originating department has been consulted, that may be a warning sign.

3. Are we rewarding an outcome or simply an activity?

Winning a contract, reducing hours and completing reports can be valuable. They are not ends in themselves.

4. Who is responsible for ensuring that the separate objectives fit together?

If the answer is “everyone”, there is a risk that in practice it means nobody.

These questions are simple, but they can change a management meeting.

Instead of exchanging success stories and then wondering why the company is losing money, participants can discuss the economic connections between their decisions.

Responsibility Is Not a Search for a Scapegoat

When a loss becomes visible, organisations understandably want to know who was responsible.

Yet identifying a person to blame does not explain why a decision process failed.

Were the targets contradictory?

Did the necessary information exist but remain within departmental boundaries?

Were interfaces overlooked?

Was someone aware of a risk but discouraged from challenging the optimistic plan?

Or was nobody explicitly accountable for the combined commercial outcome?

Responsibility is not simply finding a name after the loss.

It is creating conditions in which better decisions can be made before the loss.

Leaders must ensure that critical assumptions are tested, the relevant expertise is heard and trade-offs are considered openly.

A scapegoat may improve the mood of a difficult meeting.

It rarely improves the project result.

The Final Question

Let us return to our management meeting.

Sales won the order.

Procurement saved money.

Engineering met its hours.

Manufacturing improved productivity.

Project Management submitted every report on time.

And the project is losing money.

Perhaps the managing director should not ask:

“Which department missed its target?”

The more useful question is:

“Who made sure our targets actually fit together?”

If nobody can answer, at least the problem is clear.

The company does not have a problem achieving targets.

It has a problem with the targets themselves.

And if everyone still receives a bonus, at least the incentive system has performed exceptionally well.


About the Author

Carsten Knappe-Finger is a German management author and former industrial executive with more than 30 years of experience in international machinery and plant engineering.

A graduate in Business Administration (Dipl.-Betriebswirt), his work focuses on industrial project management, intelligent cost management, productivity management and organisational effectiveness.

His professional interests include cross-functional project estimation, Intelligent Estimating Management (IKM) and the POWER management framework.

Connect with the author on LinkedIn:
https://www.linkedin.com/in/carsten-knappe-finger-148704263


Editorial note: The MGD performance figures are based on the author’s reported industrial experience and internal calculation tracking records. The underlying records have not been independently audited by MFG Magazine.

Published as an expert contribution to MFG Magazine.

ask@mfgmagazine.com
ask@mfgmagazine.comhttps://mfgmagazine.com
mfgmagazine.com is the editorial contact for MFG Magazine. For manufacturing industry news, insights, interviews, press releases, and editorial inquiries, please contact our editorial team.

Related articles

spot_img

Recent articles

spot_img

From Leader's Desk

Beyond GPT and Claude: Why Manufacturing Needs Its Own AI Ecosystem

ChatGPT and Claude have transformed how businesses interact with artificial intelligence, but manufacturing requires much more than intelligent conversations. Dr. Rajendra Shekatkar explores why protecting intellectual property, integrating legacy infrastructure, enabling on-premises AI and understanding industrial processes are essential to building a reliable manufacturing AI ecosystem.

A ₹1 Crore Order Can Still Create a Cash Crisis: What Every Manufacturing CEO Must Understand

A ₹1 crore order can be profitable and still leave a factory ₹14 lakh short before dispatch. See how manufacturing leaders can calculate the funding gap, negotiate terms and use TReDS at the right stage.

Women in Manufacturing Leadership: Four Career Journeys at Aalberts

Four women at Aalberts demonstrate how diverse career paths strengthen manufacturing. Amber advances workforce development, Samia drives collaborative improvement, Karey connects financial insight with operations, and Anne-Lize leads people and sustainability. Their stories highlight the importance of knowledge transfer, employee involvement, cross-functional expertise, inclusive opportunities and leadership focused on enabling others to succeed.