I understand the attraction of a single performance figure. It is easy to put in a specification, easy to compare in a meeting and easy to remember afterwards. A product with a better peak value seems to have won a clear contest. The difficulty begins when the product does not spend its working life at that point. The customer may require several operating conditions, with different durations and different consequences. A comparison that ignores those circumstances can reward a design for an achievement that contributes less to the actual task than its prominence suggests.
For an industrial pump, I want the discussion to begin with the required duty and the system in which the equipment will operate. The pump characteristic and the system requirement matter together. A favourable point on a curve is information about a particular condition, not a universal ranking of products. This is familiar to application specialists, yet it can disappear when the discussion reaches a commercial presentation. The leadership task is to preserve the part of the technical explanation that changes the choice, without requiring every customer or director to become a pump designer.
Begin with the work being required
A duty description should state what the equipment must provide and how that requirement varies. The team needs a basis for the selected conditions and their relative importance. Sometimes the evidence comes from measured operation; sometimes it is an explicit planning assumption for a new application. Those are different foundations, and the comparison should say which is being used. An invented schedule made after the test results are available can make almost any preferred design look persuasive. I would rather expose uncertainty in the duty than disguise a convenient assumption as observed customer behaviour.
In one Caldriven programme, we used three operating points over a twelve-hour reference day. The schedule assigned six hours, four hours and two hours respectively. Both designs were examined against matched flow and head requirements at those points. That matching mattered: a lower electrical input would not be a useful improvement if the equipment had also provided less of the required service. The test method and measurement conditions therefore belonged to the comparison before anyone calculated a daily total or proposed a product decision from it.
There is an objection that such comparisons make selling unnecessarily complicated. A customer may not know the future duty precisely and may prefer a product with an attractive standard specification. I do not dismiss that practical need. A standardised comparison can be useful if its meaning is understood. The problem is treating it as the answer to every application question. A supplier should be able to explain both the standard result and the circumstances in which a more particular assessment is needed. Simplicity should make the decision easier to understand, not remove the condition that determines whether it is sensible.
I also ask what happens outside the selected points. A finite comparison cannot describe every possible condition. Some may be irrelevant to the intended application, while others may deserve further work before the product route is chosen. The answer is not to fill a presentation with unbounded caveats. It is to identify the operating range represented by the recommendation and the questions that remain. That helps the customer recognise when a later change in use requires another discussion rather than assume that the original conclusion travels unchanged.
Show the calculation and its boundary
Our measured electrical inputs for design A were 12.4,17.6 and 24.1 kilowatts. For B they were 11.2,16.9 and 25.0. Multiplying those values by the six-, four- and two-hour schedule produced 193.0 kilowatt-hours for A and 184.8 for B. The 8.2 difference was a calculated result for the reference day. It was not a measured annual saving at a customer site. Showing the inputs and durations allowed another person to examine the arithmetic and, more usefully, understand why the recommendation depended on the schedule.
The third point was worse for B. I wanted that visible because it explained when the choice could change. A product story that reports only the favourable points makes later application work harder: the customer has been given a ranking without its conditions. If the third point occupies more of the working day, the relative result may move. That does not make the original comparison dishonest, provided the original schedule was stated. It means the comparison has supplied a tool for judgement rather than a permanent label declaring one design superior in every use.
The expenditure on the development comparison was separate. Our ten-week programme cost C$1.4 million. The measured points and calculated energy difference did not, by themselves, establish a return on that investment. Such an assessment would require a view of the applicable market, customer use, product economics and other consequences. I resist the temptation to multiply a small, carefully bounded result across a large population simply because the resulting number looks proportionate to the development cost. The scale of a claim must come from its evidence, not from the size of the budget it is expected to justify.
Measurement quality also remains relevant. A calculation can be arithmetically exact while relying on inputs whose uncertainty matters to the difference being discussed. Test specialists should establish whether the method can support the intended comparison and how the result should be expressed. I do not want leadership to erase that judgement by demanding more decimal places. Nor should an uncertainty discussion be used to avoid every decision. It should help the team understand the confidence appropriate to the result and identify whether additional work would materially improve the choice.
Let the application change the recommendation
The product team chose B for further development because it better served the stated reference duty. That was a conditional engineering recommendation, not a claim that B had the most impressive peak figure. The commercial sponsor had to accept a more demanding explanation. We gained a product direction tied to the intended work and gave up the convenience of presenting one prominent specification as the whole argument. A leader should be willing to own that communication trade-off when it preserves the meaning of the result.
I would improve the next programme by settling the duty assumptions before commissioning the comparison. The test team can accurately perform a study whose purpose has been poorly chosen. By the time its results arrive, programme momentum may make it difficult to revisit the question. Bringing application, commercial and engineering colleagues together earlier gives the study a better chance of addressing the customer's decision. It also creates a shared understanding of what would cause the team to recommend another route, rather than treating a changed conclusion as a loss of confidence.
A curve is a description of behaviour under conditions. It becomes useful in a product choice when those conditions meet the work the customer needs done. I want our websites, proposals and investment papers to preserve that relationship. A responsible claim should help someone select, operate and reconsider the product intelligently. The best point remains worth measuring. It simply should not be allowed to stand in for the whole working day when the rest of that day is what determines the value of the design.