Administrative Efficiency Analysis (VEA): why the sequence decides success

Many authorities optimise everywhere at once and still feel no relief. The reason rarely lies in the methods, but in the sequence in which they are used.

Most authorities are not short of willingness to reform. There is analysis, optimisation, digitalisation and reorganisation. Processes are modelled, projects set up, programmes agreed. The commitment is high and so are the expectations. And yet the impression remains that the structural overload is barely easing. This article describes why that is, and how the Administrative Efficiency Analysis works against it as an ordering framework.

The problem does not lie in the methods

Most of the instruments in use make sense in themselves. Process optimisation can simplify workflows, digitalisation can shorten processing times, organisational adjustments can clarify responsibilities. The problem lies not in the methods themselves but in applying them in isolation. They work alongside each other, not together.

The logic of the individual initiative is typical. Efficiency is organised in projects, each of which looks at a limited section of the organisation. One process is optimised, one specialist system introduced, one area given a new remit. Each initiative is coherent in itself, well justified and often successful too. What is missing is the view of the administration as a whole: what part does the single initiative play in the wider picture, and what contribution is it meant to make to structural relief?

This fragmentation leads to a paradoxical situation. The growing number of individual initiatives creates additional coordination work, ties up resources and leaves initiatives competing for attention. The result is that efficiency itself becomes a burden. The organisation is permanently in change mode without its underlying condition improving noticeably. It works on itself but does not relieve itself.

A second effect comes on top of this: individual methods are often used with an implicit claim to universal validity. Process optimisation is expected to work everywhere, digitalisation is treated as the universal solution, organisational development as a cure-all. This overstretching means that methods are applied where their effect is limited, or where they are even counterproductive.

Why the sequence is a management principle

Efficiency initiatives often start where visible results seem quick to achieve. Processes can be modelled, digital solutions presented, project plans communicated. The question left out is whether these measures start at the right moment and on the right tasks. Three sentences describe what happens then.

Anyone who optimises processes before the purpose of a task has been clarified risks perfecting workflows that make no relevant contribution. Anyone who digitalises without questioning standards automates existing inefficiencies and locks current administrative practice into technology. Anyone who changes structures without prioritising tasks moves problems to another part of the organisation instead of solving them.

The pressure of expectation for quick results reinforces this misdirection. The clarifications that should come first are skipped, the stock of tasks is left untouched, standards are taken as given, and questions of purpose and benefit are put off. Efficiency is in effect pushed down to the operational level of the staff, even though there is only limited scope to shape it there. Efficiency requires patience in the right place. Not in the sense of delay, but in the sense of deliberate clarification.

First analytical perspective: tasks and standards

The first analytical perspective of the VEA is a critical look at the task portfolio of the administration as a whole and at the standards that apply to those tasks. It starts with the most basic question: what does the administration do, and to what standard does it carry out each of its tasks and services?

At this stage the existing set of tasks is not accepted as given. Every task is ranked by the contribution it makes to the objectives of the administration, and the defined standards are examined for whether they are appropriate. The aim is clarity about which tasks justify handling in depth and where lean standards are sufficient. This differentiation is uncomfortable, because it calls for decisions that cannot be conveyed equally comfortably to everyone involved. But it determines where efficiency becomes relevant at all. Without that clarification, every further measure remains blind to where the real relief lies.

Second analytical perspective: purpose review and process optimisation

The second perspective follows on this basis, combining purpose review with process optimisation. Only once it is clear which tasks carry which weight does the question of how those tasks should be organised make sense.

Purpose review (Zweckkritik) means looking at processes not only in their sequence but questioning their point and their necessity altogether. Process optimisation thereby stops being an end in itself and becomes the deliberate adjustment of workflows to clearly prioritised tasks. The aim is to reduce friction, cut complexity and shorten processing times, but always in relation to tasks with a high contribution. The same optimisation effort has an entirely different effect on a prioritised task than on a subordinate one.

Third analytical perspective: automation and digitalisation

The third perspective is made up of automation and digitalisation. They start where tasks are standardised and processes sensibly designed. Only under these conditions can technology realise its potential.

In this logic, automation is not innovation for its own sake but the consistent continuation of decisions already taken. Digitalisation replaces neither task review nor process optimisation; it amplifies their effect. In this perspective efficiency is scaled by technology, it is not created in substance. The distinction sounds academic but has very practical consequences: it explains why the same software rollout brings noticeable relief in one authority and creates additional work in another.

Four typical misapplications

The VEA only takes effect when it is understood as a coherent logic of analysis and sequencing. In practice, however, individual perspectives are often picked up in isolation or taken out of order. Four patterns occur particularly often here.

The first is digitalisation without a prior analysis of tasks. Technical solutions are introduced to speed up existing ways of working. The stock of tasks is left untouched and processes are reproduced digitally without their purpose being questioned. The result is an administration that is technically modernised but structurally unchanged.

The second is the automation of inefficient standards. Where the depth of handling was never consciously determined, it is translated tacitly into technical systems. Every special case is mapped, every exception accommodated. The technology thereby takes over the logic of overload from analogue practice, and the extra work this creates is written into systems and hard to correct.

The third is process optimisation without purpose review. Processes are analysed and improved in detail without any clarity about the contribution the underlying task makes. Workflows become faster and more transparent, the benefit stays limited. The work is efficient without it being clear what it is for.

The fourth is the blurring of the analytical perspectives. The task, process and technology levels are worked on at the same time, without clear priorities. Discussions run in parallel and decisions are postponed because the dependencies remain unclear. Efficiency becomes more complicated instead of creating clarity.

What all four patterns have in common is that they get around the uncomfortable decisions at the start. Task review, the assessment of effects and the differentiation of standards are put off. Instead, measures are taken that are visible, easy to connect to and politically easier to explain. Efficiency thereby becomes a question of technology or organisation, not of leadership and steering. These misapplications are rarely a sign of a lack of competence. They arise where efficiency comes under pressure to act and quick solutions are sought.

Not a staged plan but a frame of thinking

A common misunderstanding is to read the VEA as a project plan to be worked through once from top to bottom. It does not describe a one-off sequence but a recurring frame of thinking. Efficiency does not come from all three analytical perspectives being taken into account at some point, but from their serving permanently as the frame of reference for decisions.

New tasks, changed conditions or technological developments are reason at any time to apply the triad again. The ordering framework therefore has to meet two requirements at once: it must give direction without narrowing the view, and set a sequence without supplying rigid recipes. Certain questions have to be settled before others can sensibly be addressed. Ignoring these dependencies leads to friction and superficial solutions.

What this means for leadership

Activism brings short-term relief because it signals action. A structured approach, by contrast, demands restraint, clarity and a willingness to justify decisions. Within this ordering logic, leaders have to tolerate the fact that efficiency does not become visible straight away, even when it starts in the right place. That stance is demanding, but it is necessary if efficiency is to be more than symbolic politics.

The gain shows itself elsewhere. A clear sequence of analysis gives everyone involved a sense of direction and makes it understandable why some subjects are dealt with first and others follow later. Efficiency then stops being a matter of individual interpretation and becomes a shared logic of proceeding across the organisation. That reduces friction, increases acceptance and strengthens the capacity of the administration as a whole to steer itself.

The first step in your own administration

Applying the VEA in your own organisation does not require a major project. A sensible way in is to lay out the current efficiency initiatives side by side and to answer, for each one, which of the three analytical perspectives it starts from. Experience shows that the initiatives pile up in the third perspective while the first is barely occupied. That overview alone makes the imbalance visible.

The second step is the honest question of when a task in the administration was last consciously downgraded or a standard lowered. Where no answer is found, the first analytical perspective has not yet been taken seriously, however many optimisation projects are running. Efficiency does not arise where the most is done, but where decisions are taken most consistently.