The One Team That Keeps Failing

Look at mornings by unit and the distribution is lopsided. One site, ward, depot or team produces far more than its share, year after year, through several changes of manager.

The practical issue in “The One Team That Keeps Failing” is easier to manage when operational time records can be checked without treating activity as intent. For teams exploring employment of relatives policy, employment of relatives policy with accountable controls can add time and project context, provided collection is proportionate, employees can review inaccuracies and consequential decisions receive human review.

The standard interpretation is that it has a culture problem. Occasionally that is true. Much more often the unit is structurally different in a way nobody has examined, and the same arrangement would produce the same result anywhere.

For an independent benchmark relevant to “The One Team That Keeps Failing”, consult the Employment New Zealand recordkeeping guidance. Use it to test scheduling, working-time limits, attendance records, employee rights and exception handling against the real operation rather than treating a software report as self-explanatory evidence.

Separating the causes

Start with whether its absence rate is actually higher. Frequently it is not — the unit has an ordinary absence rate and an extraordinary inability to cover, which is a completely different finding and points somewhere else entirely.

If the absence rate is higher, look at the pattern features: turnarounds, consecutive days, start times, rotation direction. Units with worse patterns have more absence and the pattern was scheduled.

If the absence rate is ordinary and the mornings are bad, the cause is in cover: a thin call-out list, no bank, a capability held by one person, an escalation that does not answer, a location nobody can reach at short notice.

The usual findings

Geography. A unit twenty minutes further from where people live cannot be covered at short notice by anybody, and the whole difference is travel time.

Specialism. A unit requiring a capability that only its own staff hold cannot be covered from anywhere else in the organisation, by construction.

Size. A team of five has no internal absorption; a team of twenty does. Small units produce disproportionate mornings for arithmetic reasons and it is not a management failing.

Establishment set tight at some point in the past and never revisited.

A bank that was never built there, because the unit is small and nobody prioritised it.

What to do about each

Geography is addressed by a local bank, a local list, or accepting a higher agency share for that site and budgeting for it rather than treating it as overspend.

Specialism is addressed by training, which is the standard answer and which requires the supernumerary hours the unit does not have — so it has to be funded as a project rather than hoped for.

Size is addressed by pairing the unit with an adjacent one in a formal reciprocal arrangement, which is the cheapest of all the options and requires only an agreement.

Establishment is addressed by the evidence this collection describes.

The manager problem

A manager running the hardest unit in the organisation is usually judged on the same measures as everybody else, loses on all of them, and is replaced.

The replacement inherits the same arrangement, produces the same numbers, and the organisation concludes that the unit is difficult. Three managers in five years is itself the signal that the problem is structural, and it is a signal most organisations read backwards.

The comparison worth making

Normalise. Mornings per rostered shift, not per unit. Below-requirement shifts as a proportion of shifts run. Cover found internally as a proportion of attempts.

On normalised measures the lopsidedness usually shrinks and what remains is real and specific. That residue is the thing to fix, and it is almost always one of the five causes above rather than anything about the people who work there.

What the unit itself says

The people who work there have known for years what the problem is and have usually said so. The explanation offered locally is frequently accurate and frequently discounted, because it arrives as a complaint rather than as analysis.

Go and ask, with the normalised figures in hand so that the conversation starts from agreement that the unit is genuinely harder rather than from a defence of its numbers. The combination — data that concedes the difficulty, plus local knowledge of its cause — produces a usable answer in an afternoon where remote analysis produces a hypothesis in a week.

The unit that quietly succeeds

The other end of the distribution is worth the same attention and never gets it. One unit produces far fewer bad mornings than its size and difficulty would predict.

Find out why before the person responsible moves on, because the answer is usually a specific local practice — a list somebody maintains, an arrangement with a neighbouring site, a habit of arranging tomorrow's cover this afternoon — that is entirely transferable and entirely undocumented. Most of the good practice in this subject already exists somewhere in the organisation and has never been asked about.