Process and Performance Maturity

Definition

The problem it addresses

Structure is the first thing a district reaches for when a department is struggling. It is rarely the binding constraint.

A department at the Ad Hoc level has no written process, no measures, and no way to improve except by the effort of the people currently in it. Reorganize that department and you get the same performance under a new chart. Give it documented process, an owned metric, and a working handoff with the departments upstream and downstream of it, and performance moves without touching a single reporting line.

Maturity also explains a pattern superintendents describe often. A department runs well for years, one person retires, and it stops running. That department was operating on individual mastery rather than on process, which is a maturity condition with a known failure mode.

How it works

The assessment runs by department and by category. LEAN Frog scores what the evidence supports, which means documents that exist and measures that are actually reported, rather than what a department intends to do.

The five categories

• Process documentation. Whether the work is written down, current, and specific enough that a competent newcomer could perform it.
• Performance measurement. Whether the department knows how it is doing while the work is underway, and who owns each number.
• Continuous improvement. Whether there is a mechanism that turns a problem into a change, or whether problems are absorbed and repeated.
• Interdepartmental integration. Whether handoffs to and from other departments are defined, or whether the space between two departments belongs to nobody.
• Software and processes. Whether the systems in place support the work, and whether the process was designed around the software or worked around it.

The five levels

• Ad Hoc. Work depends on the individual performing it. Nothing is written, nothing is measured, and knowledge leaves when people do.
• Fragmented. Some documentation and some measures exist, inconsistently, usually where a capable person built them for their own area.
• Defined. The process is documented and understood across the department, with an owner.
• Managed. The process is documented, measured, and actively managed against its measures.
• Optimizing. The department improves its own process on a cadence, using its own data, without an external prompt.

Most district departments score between Ad Hoc and Defined, and the distribution across categories is more useful than the average. A department that is Managed on measurement and Ad Hoc on documentation has a specific, fixable problem.

Evidence required

• Written procedures, process maps, desk manuals, and their revision dates
• Reports the department currently produces, and the named owner of each measure
• The system of record for the department's core process, and how work enters and leaves it
• Records of process changes made in the past two years, and what prompted each one
• Handoff points with other departments, and what happens when one side is late
• Interviews with department staff at more than one level, because the documented process and the performed process often differ

Indicators and measures

• Share of the department's core processes with current written documentation
• Number of measures reported, and how many have a named owner
• Cycle time and backlog for the department's primary transaction
• Rework and exception rates, where the system records them
• Work performed outside the system of record, in spreadsheets, paper, or email
• Time from a known problem to an implemented change
• Single points of failure: processes only one person can perform

Appropriate uses

• Inside an organizational review, to separate a structure problem from a process problem
• Inside a departmental efficiency review, to set the improvement sequence
• Before automating anything, because automating an undocumented process installs the workaround permanently
• To decide where to spend limited improvement capacity across many departments
• To assess succession risk in a department that runs on one person's knowledge

Inappropriate uses

• As a performance evaluation of the department's leader. Maturity is a condition the organization produced, usually over years.
• As a ranking for public comparison between departments. The scores are diagnostic and they invite defensiveness when they are published as a league table.
• As a target in itself. Optimizing is expensive and is rarely the right level for every category in every department.
• As a substitute for measuring outcomes. A mature process can reliably produce the wrong result.

Limitations

The assessment is a judgment against evidence, and evidence is uneven. A department that documents nothing will score low even where its practice is disciplined, because practice that lives only in people's heads is precisely the exposure the framework is built to surface.

The five levels also compress a wide range. The distance between the bottom and the top of Fragmented is larger than the distance between Managed and Optimizing, which is why LEAN Frog reports the level with the evidence behind it rather than the level alone.

Maturity explains reliability. It does not, on its own, tell a district whether the department is the right size or whether the work belongs there at all.

An example

In one school system, the operations review found a work order system configured with sixty-six crafts against a vendor recommendation of fifteen to twenty. Corrective work orders were printed and re-keyed by hand. Preventative maintenance was tracked outside the system entirely.

Read through the framework, that is a single department scoring low on three categories at once. Software and processes: the configuration had never been revisited, so the department built workarounds around it. Process documentation: the workarounds became the process without ever being written down. Performance measurement: with preventative maintenance outside the system, the department could not report its own completion rate.

None of that was a software failure and none of it was a staff failure. It was a configuration decision made once, and a decade of reasonable adaptation to it. The corrective sequence follows the scores: fix the configuration, document the process that results, then measure it. Reorganizing the department first would have changed nothing.