7 min read<\/p>\n
City halls are not transformed by new tools alone. Reforms succeed when leadership sets the framework: what can be experimented with, who makes the decisions, which mistakes are considered learning opportunities, and which routines are to be ended. For municipalities, administrative culture is thus becoming a key location factor.<\/strong><\/p>\n Key Takeaways<\/p>\n Related:<\/span>Process optimization without permanent projects<\/a> \/<\/span> Why GovTech pilots fail before reaching full-scale operation<\/a><\/p>\n What does leadership mean for reform in local government?<\/strong> Leadership for reform means clarifying responsibilities, decision-making rights, learning cycles, and discontinuation criteria. This gives a reform an owner, a deadline, a metric, and a path to standard operations.<\/p>\n In its articles on administration, AI, and citizen-centric services, kommunal.de repeatedly highlights the same point: new possibilities are of little use if organizations cannot sustain them. This is especially true in town halls, where legal certainty, political oversight, limited staffing, and high citizen expectations collide.<\/p>\n Culture here does not refer to the atmosphere. Culture is the sum of practical rules: who is allowed to prepare a decision, who must approve it, what deviations are permitted, and how a mistake is turned into an improvement. These rules determine whether reforms gain momentum or get bogged down in endless administrative loops.<\/p>\n For leaders in the municipal sector, this is uncomfortable. Many problems cannot be delegated. A department head can procure new software, but they cannot purchase a learning culture. They must decide which tasks to standardize, where teams should have more leeway, and which old routines should be ended.<\/p>\n Many organizations talk about a culture of learning from mistakes without having a rhythm for it. In administrations, this is particularly risky. If experiments are not evaluated regularly, parallel worlds emerge: the new procedure is running, the old procedure remains, and no one makes a decision.<\/p>\n A sensible learning cadence is simple. A team tests a clearly defined process for four to six weeks, collects a few key metrics, and then decides: keep, adapt, or end. The metrics do not have to be perfect. They only need to show whether waiting times, inquiries, processing effort, or satisfaction are measurably improving.<\/p>\n Administration learns when a test is given an owner, a date, and a decision.<\/p><\/blockquote>\n This cadence is also important for employees. Reforms create uncertainty when they run indefinitely. A clear test protects teams from the feeling of constantly having to work in both the old and new systems simultaneously.<\/p>\n The shortage of skilled workers in administration and municipal operations is not just a recruiting issue. Employees are more likely to stay when they see the impact of their work, can take on responsibility, and are not thwarted by unnecessary red tape. Leadership, therefore, is a decisive factor in employer attractiveness.<\/p>\n This is especially true for young administrative staff and career changers. They do not expect every rule to disappear. They expect rules to be justifiable and for improvements to be given a chance. When every idea gets stuck at the boundaries of departmental jurisdiction, the organization loses energy.<\/p>\n For MBF readers, this is familiar territory. Mid-sized companies recognize the same mechanism: processes do not improve because a system is introduced, but because leadership reorders responsibility. Municipal administrations face the same task, only under greater public scrutiny.<\/p>\n What hinders reform<\/p>\n What supports reform<\/p>\n First, every reform project needs a person in charge with direct access to decision-makers. Project groups without a clear path to a decision produce good papers, but little change. The owner must be technically close enough to the process and organizationally close enough to management.<\/p>\n Second, every manager should ask one process-related question each month: Which task are we still performing even though it no longer provides any value? This question creates capacity without immediately requiring new personnel.<\/p>\n Third, the administration needs a clean distinction between experiments and standards. An experiment can be small, fast, and incomplete. A standard must be documented, taught, and permanently funded. Many reforms fail because this boundary remains blurred.<\/p>\n Sources and anchors: kommunal.de articles on AI in municipalities, citizen-centric administration, and municipal organizational practice; kommunal.de debates on personnel pressure, participation, and administrative modernization.<\/p>\n Municipal leadership operates between several different logics. Politics expects transparency, citizens expect accessibility, employees expect protection from burnout, and oversight bodies expect legal certainty. Reforms only succeed when these logics are translated.<\/p>\n This translation work is demanding. A process may be technically sound but politically difficult to communicate. A digital service may appear citizen-friendly while triggering extra work internally. A quick solution may be legally risky. Leadership must make these tensions visible instead of hiding them in project plans.<\/p>\n For vendors, this is an important insight. Those helping town halls should not just explain a solution, but also provide the internal decision-making logic: which roles change, which risks decrease, which committee questions arise, and which tasks are eliminated. This makes procurement easier and implementation more realistic.<\/p>\n Many administrations launch change with high energy. After a few months, old and new processes run in parallel because no one terminates the old procedure. This parallelism is one of the greatest productivity killers. It consumes time and creates the impression that modernization makes everything more complicated.<\/p>\n Leadership must therefore not only enable the new; it must shut down the old. This is politically and organizationally more difficult than launching a pilot, but significantly more important. Every new workflow requires a decision on which old workflow ends, which data is migrated, and which exceptions remain accepted.<\/p>\n This termination decision should be made early. If a test is successful, the transition is prepared. If it fails, it is ended. Both represent progress. Stagnation occurs when a test continues indefinitely out of consideration for all involved parties.<\/p>\n The first question is: Which task consumes a lot of time and generates little impact? This directs focus toward routine, not prestige. Much relief lies in forms, follow-up queries, committee templates, internal approvals, or manual lists.<\/p>\n The second question is: Which decision is missing? Often, the problem is not the analysis, but the lack of a final determination. A team knows what would make sense but waits for approval, priority, or protection from criticism.<\/p>\n The third question is: What is allowed to disappear once the new way works? This question is uncomfortable and precisely why it is effective. It prevents reforms from simply adding more layers to an already burdened organization.<\/p>\n Many administrations have experienced a high number of projects in recent years: OZG, energy, housing, climate adaptation, recruitment, new participation formats. Reform fatigue arises when every new topic is added on top and rarely does anything become visibly easier.<\/p>\n Leadership must therefore limit priorities. Three small improvements with visible relief are more effective than ten working groups without a decision. Employees measure change not by strategy slides, but by their workday.<\/p>\n For local democracy, this is not an internal detail. An overloaded administration responds later, explains less effectively, and appears more defensive. An administration capable of learning can resolve conflicts earlier and better show citizens why decisions are made.<\/p>\n The practical start lies in a simple inventory. Which three processes generate the most follow-up queries, which three appointments are postponed most frequently, which three pieces of information are regularly missing for citizens or employees? This list is often more valuable than a grand strategy presentation because it thinks about administration from the perspective of daily life.<\/p>\n After that, a test with limited risk is needed. One department, one process, one timeframe, one metric. After four to six weeks, management decides whether the approach remains, is adjusted, or is ended. This is how modernization becomes a work routine rather than an exceptional state.<\/p>\n For external partners, this logic is also helpful. It forces proposals to describe impact in administrative language: fewer follow-up queries, clearer responsibilities, faster resolutions, lower operational load. Exactly these effects can be defended internally in a municipal environment because they sound like relief, not just a trend.<\/p>\n This makes the topics relevant for MyBusinessFuture. It is about leadership, capacity, budget logic, and the question of how public organizations deliver better results with scarce resources. The technical component is only one part of the decision.<\/p>\n The benefit, therefore, does not arise from a grand promise, but from a precise change in everyday life. Municipalities need exactly this precision when they want to justify new paths internally and explain them to citizens.<\/p>\n Because technology only works when responsibilities, decision-making authority, and workflows are clearly defined. Without leadership, it simply becomes another process layered on top of existing routines.<\/p>\n<\/details>\n A culture of failure means allowing for limited testing, evaluating results transparently, and making decisions accordingly. It does not replace legal review or personal accountability.<\/p>\n<\/details>\n Four to six weeks are often sufficient for simple workflows. Larger changes require longer phases, but even then, interim decision points should be firmly scheduled.<\/p>\n<\/details>\n Employees are more likely to stay when they see the impact of their work and aren’t stuck in endless, unnecessary loops. Having room to maneuver is a key retention factor.<\/p>\n<\/details>\n Select a project that is small enough to test, yet significant enough to demonstrate relief. Then, define the owner, key metrics, and a firm decision date.<\/p>\n<\/details>\n\n
Why culture is not a soft topic<\/h2>\n
\n\n
\n \nLeadership Question<\/th>\n Why it matters<\/th>\n Typical mistake<\/th>\n<\/tr>\n<\/thead>\n \n What is allowed to be tested?<\/td>\n Teams need a safe framework<\/td>\n Pilot without decision criteria<\/td>\n<\/tr>\n \n Who decides after the test?<\/td>\n Learning requires closure<\/td>\n Permanent testing without standard operation<\/td>\n<\/tr>\n \n Which mistakes are acceptable?<\/td>\n Risks must be distinguishable<\/td>\n Misunderstanding error culture as a free pass<\/td>\n<\/tr>\n \n What will be ended?<\/td>\n Capacity is created by letting go<\/td>\n New tasks piled onto old routines<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n Learning requires a strict cadence<\/h2>\n
Employee retention starts with room for maneuver<\/h2>\n
\n
\n
Three leadership routines for town halls<\/h2>\n
The leader as a translator<\/h2>\n
Why reforms must avoid an endless loop<\/h2>\n
What leadership should ask in the next meeting<\/h2>\n
Leadership protects against reform fatigue<\/h2>\n
Frequently Asked Questions<\/h2>\n
Why is leadership more important than technology?<\/strong><\/summary>\n
What does a culture of failure mean in administration specifically?<\/strong><\/summary>\n
How long should a reform test run?<\/strong><\/summary>\n
How does this help with the shortage of skilled workers?<\/strong><\/summary>\n
What is the first step for department management?<\/strong><\/summary>\n
Editor’s Reading Recommendations<\/h2>\n