What configuration debt looks like in a mature Unit4 estate

Configuration debt is not a defect list. A defect is something that does not work. Debt is the set of things that do work, individually, for reasons nobody in the organisation can now reconstruct.

Every mature Unit4 Business World estate carries it. An absence code was created for a scheme that ran for two years and was then withdrawn, and the code stayed. A flexi field group was added so that one directorate could record something the standard tabs did not hold, and the group is still live, still visible, still being filled in by people who were never told what it is for. A workflow route was amended so that an approval could clear during a reorganisation, and the amendment outlived the reorganisation by six years. None of these was a mistake on the day it was made. Taken together they are the estate’s real design, and the real design has no owner.

There is a quick test for whether an estate has drifted, and it is uncomfortable. Ask three people who run HR and payroll to describe, without opening the system, how one process works from the moment a manager raises it to the moment it reaches a payslip. If you get three answers and all three are partly right, the estate has drifted.

Drift is not spread evenly. In an HR and payroll estate it collects in four places, and they are much the same four in every installation.

Attributes and attribute values. Position and resource attribute sets, equal opportunities and diversity values, and the document types linked to them are easy to add and almost never retired. Value lists grow, superseded values stay selectable, and reporting quietly stops meaning what its readers think it means.

Flexi fields. Group headers, members and value lists, placed at tab level with conditional hide and show rules, are the fastest way to capture something the standard model does not hold. They are also the fastest way to build a screen that half the organisation completes and half ignores. Groups that were supposed to be closed but remain active, and members whose value lists were never rationalised, are ordinary findings rather than exotic ones.

Workflow. Element type routing, approval chains that run from line manager to cost-centre approver to HR and payroll, and the substitute and proxy configuration behind them are where drift turns operational. Ghost tasks, approvals that were bypassed, and routing that silently misses a step are the symptoms people report. The cause is usually an amendment made for one case and then left in place for every case.

Absence configuration. Absence codes, categories and grouping, special leave reasons and the sickness, annual leave and statutory schemes built on top of them are the most sensitive part of the estate, because absence feeds pay. A category that was grouped wrongly at build does not announce itself. It waits for the first employee whose circumstances cross the boundary.

Three reasons, and none of them is incompetence.

First, configuration is nobody’s job. It belongs to HR when it is a form, to payroll when it is an element, to finance when it is a cost distribution and to IT when it breaks. The one thing it is never assigned is a single owner who reads the whole estate and keeps a current picture of it.

Second, documentation is the first thing cut under service pressure. The change gets made because the pay run is on Thursday. The build note that would have explained why it was made in that particular way gets written later, which in practice means never, and the person who held the reasoning moves on.

Third, testing follows the change rather than the estate. A change request is tested against itself and passes. The interaction between that change and the eleven earlier changes touching the same element, code or route is not tested, because no one holds the list of eleven.

Underneath all three sits the reason debt is so easy to live with. The system behaves correctly for most people most of the time. Drift shows up on the exception path, and that path is small enough to absorb as manual work until somebody counts the manual work.

Debt is cheap to carry and expensive to discover, and an upgrade discovers all of it at once.

A major-version upgrade or a move to the web client puts every HR and payroll process at risk of silent regression. To prove that nothing regressed you need to know what correct behaviour was before the release, process by process. That knowledge is exactly what an undocumented estate lacks, so the first weeks of the programme go on rediscovering the current system at programme rates, with the timetable already fixed.

The same debt then shows up in the decision itself. A strategic decision about a Unit4 estate should not be taken against a system the organisation does not currently understand. That is the argument for diagnosing before deciding, and it is why a structured review is worth more before a business case than after one.

A useful review is not a tour of the screens. It reads the estate across six domains: configuration drift, defect inventory, control gaps, undocumented architecture, capability deficit and cloud-readiness posture. Written for an executive audience, it sets out findings, the remediation options against each one, and an estimate for the work, so that the leadership team gets a decision to take rather than a description to absorb.

On a major-version Unit4 upgrade in local government, acceptance was run across sixteen HR and payroll process areas, from position administration, applicant, starter, induction and probation, through grievance, capability, disciplinary, competence, planned and unplanned absence, occupational health, leaver and contractual change, followed by a further phase covering loans, deductions, back pay, overpayments, auto-enrolment, payroll reversal, cost distribution and court orders.

The artefact that made the release acceptable was not the execution. It was the master script library written before it, because writing the scripts forced the estate’s actual behaviour to be stated in advance, area by area. The upgrade was then accepted against a phased, documented library rather than against spot checks.

Read the engagement in full on the case studies page.

Three routes, in ascending order of commitment, and none of them requires an email address to start.

• Run the free configuration health check. Twelve questions across the six assessment domains, scored on the page: the Unit4 configuration health check. It gives you the shape of the debt before anyone is commissioned.
• Read the diagnostic brief. The fixed-scope engagement that turns the six domains into findings, remediation options and an estimate a leadership team can act on is described in full on the Unit4 X-Ray brief.
• Read the worked example. The upgrade acceptance programme above is written up as an upgrade acceptance programme across 16 HR and payroll process areas.