Public Sector

Good improvements
that don’t stay in place.

In municipalities, agencies and institutions, the will to improve is rarely the problem. It is the anchoring that is missing — the systems and leadership behaviour that make sure the right habits hold, even when the project has ended.

A scenario you know

The project succeeded.
The improvement didn’t last.

You ran an improvement project. Workshops, mapping, a new workflow. It worked for two months. Then came a staff change, a new political focus and an acute stop — and suddenly you were back to the old patterns.

It isn’t a leadership failure. It is the absence of the daily structures that carry a new practice forward. A project ends. Management routines don’t.

We build precisely those routines: simple, concrete and anchored in daily leadership behaviour — not in a project document.

Improvements are launched but don’t last

The change lives in the project, not in the routines.

Workflows are person-dependent

Cases are handled differently depending on who holds the task.

Documentation creates extra work

Requirements are treated as hassle rather than as overview.

No visibility of case progress

Managers discover problems too late — or from citizens’ complaints.

The concrete problems we solve

Improvements don’t last

  • The project ends and the habits slide back
  • New leadership or staff turnover resets the progress

Anchoring in daily leadership behaviour — the improvements live on because the systems carry them.

Responsibility falls between two stools

  • Cases circulate across departments without a clear owner
  • Decisions drag on — no clear decision-maker

A clear responsibility matrix and escalation structure — everyone knows who owns what.

No visibility of case progress

  • Managers discover problems too late — or from citizens’ complaints
  • No fixed daily status review

Visual management and daily operating routines that surface and resolve deviations in time.

Prozanta Operating Model

From project improvement to
lasting change.

M-B-E-A is the four phases that give improvements roots. Not as a project, but as a new way of leading and organising the daily work.

M

Map

We map your case flow and workflows — from enquiry to completion — and uncover precisely where time and capacity disappear in waiting, rework and unclear responsibility.

B

Build

Board meetings, visual case overviews and daily coordination routines that create visibility and shared direction — without introducing heavy IT solutions.

E

Execute

Standard workflows for the most frequent and most error-prone processes. SOPs short enough to use and clear enough to follow — no matter who holds the task.

A

Anchor

We anchor the systems in leaders’ daily behaviour, so they survive staff turnover, organisational changes and the next project that demands all the attention.

How we work

From improvement project
to a lasting operating culture.

01

Map the case flow

We follow a case from start to finish and mark every place where it stops, circulates or depends on a specific person. Typically 1-2 days.

02

Build visual case visibility

A simple shared overview of case status, volume and obstacles — visible to everyone and updated daily. No new IT systems required.

03

Establish standard workflows

Concise SOPs for the 3-5 most frequent and most error-prone processes. Drawn up with the employees who perform them.

04

Anchor in leadership behaviour

Middle managers and department heads are trained in the daily follow-up routines. We follow up after 4 and 8 weeks.

Free tools for public organisations

Start with a diagnosis or find out which phase you are in — before you decide.

From the knowledge base

See all articles

Frequently asked questions

Can Lean be used in the public sector without colliding with legislation and contractual obligations?

Yes. Lean is about removing non-value-adding activities from the workflows — not about circumventing rules or reducing documentation requirements that have a legal basis. We always adapt the approach to the regulatory context.

We have already tried improvement projects — they never last. What do you do differently?

Most improvement projects fail in the anchoring phase. We don’t start with a project, but with building the daily management routines that carry the improvements forward. That means: visual management, daily follow-up routines and middle-manager anchoring — not a report on a shelf.

What is the timeframe for a typical public-sector engagement?

A typical engagement lasts 10-16 weeks, depending on complexity. The first visible changes — such as a shared overview of case status and shorter meetings — typically appear within the first 3-4 weeks.

Does it involve a lot of meetings and workshops?

No. We work close to daily operations — not in the meeting room. Typically it involves shorter, focused observations and co-design sessions with the people who actually do the work, not just the managers.

Who we work best with

Is this for you?

We work best with public-sector units where the will to improve is there, but the day-to-day and the complexity take over. Here is when we are the right match, and when we are not.

This is built for you, if…

  • Complex workflows and heavy documentation requirements eat time away from the core task.
  • Good improvements are launched but disappear again when everyday life takes over.
  • Operations hang on a few experienced employees, and knowledge is rarely shared systematically.
  • You have been through projects before that looked good on paper but didn’t change the day-to-day.

We are probably not the right fit, if…

  • You are looking for a report for a drawer — not a lasting change in the day-to-day itself.
  • You want a consultant who takes over — rather than building your employees up to manage it themselves.
  • You are in an acute situation that calls for a turnaround here and now.

By saying it up front, we save you the time — and ourselves an engagement that wouldn’t have lasted anyway.

Ready for improvements
that last?

We start with a no-obligation conversation where we go through your workflows and give an honest assessment of what it will take to anchor the improvements.