Participation in Administrative Modernisation: Why Involvement Is Not a Nice-to-have

Nov 2, 2026

Michael Ahr - Autor

von Michael Ahr

Participation in Administrative Modernisation: Why Involvement Is Not a Nice-to-have

Leaving staff out of change processes costs you the acceptance of the solution before it is even introduced.

In many public-sector projects, involvement is treated as a courtesy. The workforce is informed, feedback is collected at the end, and that is called participation. Anyone who approaches administrative modernisation methodically needs to correct that view. Involvement is not a side activity. It is one of four methodological guardrails that decide whether a transformation project succeeds or fails.

Four guardrails, one shared purpose

Successful administrative modernisation rests on four application principles that act as methodological guardrails: complexity reduction for manageable projects, evidence-based work for valid findings, participation for accepted solutions, and an analysis matrix as a standardised tool for documentation and evaluation. Each of these principles addresses its own risk factor. Without complexity reduction, a project gets lost in too many workstreams at once. Without evidence-based work, decisions rest on assumptions rather than robust findings. Without participation, a solution may be technically sound but is rarely carried by the people who are meant to use it.

These four principles do not work in isolation. They interlock: an analysis with reduced complexity creates the framework in which involvement can take place in a concrete and targeted way. An evidence-based foundation gives participation substance, because those involved discuss real findings rather than assumptions. Participation, in turn, feeds evidence-based work with its most important source: the knowledge of the people who actually work within the structures. The analysis matrix finally records all findings so that they remain traceable and evaluable for everyone involved.

Accepted solutions beat perfect solutions

The key statement in the method is this: participation leads to accepted solutions. That may sound modest, but it captures the core of every transformation in public administration. An administrative organisation cannot be changed by decree. Structures, processes and responsibilities are carried by people, and these people decide in their daily work whether a new solution is actually applied, or falls back into the old routine once the introduction phase is over.

A technically elegant solution developed without the people affected often remains theory. A solution developed together with staff already carries part of its own implementation within it. Those involved know the reasons for the change, have contributed their own ideas, and thereby take on shared responsibility for the outcome. That is what makes participation a strategic element rather than a mere communication measure. For senior managers, this means involvement belongs in the project plan, with fixed points in time and clear formats, rather than being a spontaneous reaction once resistance is already visible.

Three levels of analysis as a shared foundation

For involvement to be more than an exchange of opinions, it needs a shared analytical basis. The method works with three levels of analysis: structures, which capture what exists in the organisation, potential, which shows what could be developed, and resources, which describe what is actually being worked with. These three levels give participation a clear subject. Those involved do not discuss change in the abstract, but concrete findings on the structures, potential and resources of their own organisation.

This noticeably changes the quality of involvement. Someone asked how they feel about an abstract vision of the future gives vague answers. Someone asked, based on concrete analysis results, whether a described structure matches reality and what potential they see themselves, gives robust and often surprisingly specific input. Participation gains substance as a result, and the analysis gains closeness to practice. Both sides benefit: project leadership receives more robust data, and staff experience that their assessment genuinely feeds into the analysis.

The balance between depth and feasibility

Participation needs a sound measure. Formats that are too superficial produce superficial results, formats that are too elaborate overstretch the already limited resources of an administration running day-to-day operations. The art lies in the balance between analytical depth and practical feasibility. A structured approach that anchors involvement at clearly defined points in the project, rather than scattering it arbitrarily, helps to keep that balance. It matters that the participation formats match the respective level of analysis: structural questions call for different formats than gathering potential or resources.

For senior managers, this means in practice that participation can be planned and steered, but it has to be considered a fixed part of the project from the outset, not an optional addition at the end. Anyone who only looks for involvement once a solution is already fixed will usually no longer get genuine input, only after-the-fact agreement or open resistance. When participation is instead treated from the start as an independent principle alongside complexity reduction, evidence-based work and the analysis matrix, the dynamic of the whole project changes: change is then not planned past the workforce, but developed together with it.

My book Verwaltungsmodernisierung mit Methode describes in Chapter 3 how these four application principles interlock with the analysis matrix in practice, and how administrative organisations can thereby be treated as systems that can be shaped rather than as unchangeable structures. Anyone practising modernisation with method builds in participation from the start, rather than treating it as a correction once resistance has already set in.

This article explores themes from Chapter 3 of my book
Verwaltungsmodernisierung mit Methode. More on this in the book.

About the book