Skip to main content

Efficiency Quotes: Applying the Advice Without Losing Sight of People

How to read familiar management sayings through their sources, assumptions, and practical consequences.

Efficiency Quotes: Applying the Advice Without Losing Sight of People

A grants team is asked to process applications faster. A director suggests shortening the review window and reducing the time advisers spend answering questions. Both changes could increase the number of applications handled per week. They might also shift work to applicants, increase corrections, or make it harder to identify a proposal that needs specialist advice.

An efficiency quotation can help frame the discussion, but it cannot resolve those trade-offs. The team needs to define the intended improvement, understand the work being changed, and examine who will experience the consequences. Faster handling is useful when it supports a reliable service at an acceptable cost.

Reading management quotations carefully starts with the source. A phrase may be accurately recorded but applied beyond its original purpose. It may also circulate in a form that reverses the author’s point. The examples below distinguish verified wording and context from the practical interpretation offered here.

Parkinson’s Observation Needs a Defined Task

Work expands so as to fill the time available for its completion.

C. Northcote Parkinson used this wording in his 1955 Economist essay. The essay is a satirical examination of bureaucracy. It provides an observation worth considering, rather than a scientific law establishing that every estimate contains spare time or that shorter deadlines improve every task.

For the grants team, the phrase might prompt a useful question about open-ended review. Are advisers repeatedly revising a recommendation because nobody has defined the required evidence? If so, clearer completion criteria could reduce unnecessary work without reducing the quality of the decision.

A different case requires a different response. An application may need an external assessment that cannot be completed within the proposed window. Shortening the deadline changes the available choices: obtain another qualified reviewer, narrow the promise, or accept a later decision. It does not make the assessment itself unnecessary.

Before changing the date, distinguish work that lacks a stopping rule from work that needs real capacity. The discussion becomes more useful when the team can describe what must be checked, what level of uncertainty is acceptable, and who can authorise a departure from the normal process.

Taylor’s System Included a View of People

In the past the man has been first; in the future the system must be first.

This sentence appears in Frederick Winslow Taylor’s The Principles of Scientific Management. The surrounding passage discusses organising and developing capable people rather than relying on finding an exceptional individual. Reading the sentence as a simple instruction to disregard workers strips away part of its stated context.

That context does not settle whether Taylor’s wider approach is appropriate for a modern service. His prescription gives management a strong role in defining methods and judging performance. A present-day team still needs to examine whose knowledge shapes the process, how assumptions are tested, and whether staff can challenge a method that does not fit the case.

In the grants example, a standard review template may improve consistency and make training easier. Advisers should help develop it because they encounter the exceptions and unclear questions. A system designed without that experience may require more workarounds than the method it replaces.

The relevant lesson is to examine both the operating method and the conditions under which people use it. A procedure should provide clear expectations and support competent judgement. Where it requires an exception, staff need an authorised route to obtain one and a way to feed the experience back into improvement.

Deming Was Criticising the Measurement Maxim

It is wrong to suppose that if you can’t measure it, you can’t manage it – a costly myth.

The Deming Institute traces this statement to The New Economics. The familiar abbreviated phrase about being unable to manage what cannot be measured is often attributed to Deming as advice, despite the opposite meaning of the passage presented by the institute.

Measurement remains valuable. The grants team needs to know how long applications take, where they wait, and how often a decision requires correction. The caution concerns treating the available numbers as a complete representation of the work.

Applications differ in complexity. A specialist adviser may handle fewer cases while helping colleagues resolve difficult questions. A shorter conversation might reduce recorded handling time but leave an applicant unable to supply the evidence required. Those possibilities should be investigated through cases and feedback alongside the figures.

A manager can therefore act on evidence that includes professional judgement and qualitative accounts, while being clear about uncertainty. The alternative to an incomplete metric need not be an invented score for everything that matters. It may be a better question, a review of representative work, or an explicit decision about what the organisation values.

Define the Whole Improvement Before Optimising a Part

Suppose a new form reduces advisers’ data-entry time. That is a useful local improvement if the required information remains accurate and applicants can complete it. If the form instead creates more clarification calls, part of the cost has moved outside the measured step.

Assess the process from application preparation through to a usable decision. Record the work required from staff, specialist reviewers, and applicants. Consider corrections and repeat contacts, as well as the initial processing time. This provides a broader account of whether the service improved.

The same reasoning applies to automation. A tool can remove repetitive copying while introducing verification, maintenance, or exception handling. Those tasks should appear in the plan. Their existence does not invalidate automation; it changes the comparison between alternatives.

The article on execution bottlenecks examines where work accumulates across a process. That question helps avoid investing in a faster local step when the unresolved delay sits elsewhere.

Keep Workload and Judgement in the Account

An efficiency proposal should state what people are expected to do with the time released. The organisation might reduce a backlog, improve advice, provide training, or reduce sustained overtime. Those are different outcomes and may require different measures.

If every saving is immediately filled with additional case volume, the team should assess whether there is still capacity for unusual requests, learning, and necessary review. This is an operating question about demand and staffing. It does not require assuming that a particular utilisation percentage is always safe or always harmful.

People doing the work can explain which steps require concentration, where requests arrive unpredictably, and which changes would make their task easier. Include that knowledge before setting a new expectation. A shorter target based only on an average may fit ordinary cases poorly and exceptional cases even less well.

Managers should also distinguish a process problem from individual performance. If many advisers struggle with the same unclear evidence requirement, more pressure on each adviser may leave the common obstacle unchanged. A useful review asks what the current method allows a competent person to achieve under realistic conditions.

Identify Who Can Accept the Trade-Off

The advisers may discover that a weekly management report consumes time without informing a current decision. They can describe the burden and propose a smaller report or a trial suspension. The person commissioning it should explain which decision still requires the information and authorise any change. The team should not have to infer that an efficiency campaign has silently cancelled an established obligation.

The same applies when a saving depends on accepting a weaker service. Reducing applicant support may be an organisational choice, but the proposal should explain which applicants lose access to help and what alternative is available. Calling it efficiency should not obscure the changed service promise. The responsible sponsor can then compare that option with investment in a clearer form, additional support, or a different processing schedule. This gives the discussion an accountable decision point: who can change the requirement, what evidence they considered, and what result the team is now expected to deliver.

Test a Proposal at a Scale That Can Be Examined

A bounded trial can compare the current review process with clearer completion criteria or a revised form. Choose a set of cases appropriate to the change, establish how quality will be checked, and identify what would justify stopping or adjusting the trial.

Record what happens to waiting, corrections, staff effort, and applicant understanding. Differences in case complexity or demand may explain part of the result. A short trial can reveal practical defects without proving a permanent effect across the whole service.

Check how the change behaves when ordinary variation occurs. A procedure that works only while a particular specialist is available may need a deputy, clearer guidance, or a narrower scope. A pilot should help discover those conditions before the organisation relies on the proposed saving.

If a review step appears redundant, examine its actual purpose before removing it. The article on approval checkpoints develops that distinction between valuable assurance and duplicated waiting.

A useful efficiency quotation opens a question about the work. Its value depends on the evidence and choices that follow: what improves, which conditions matter, who carries the cost, and how the organisation will know whether the result is acceptable. Those questions give a memorable phrase a practical role without asking it to function as a complete management method.