What to Do When It Will Not Move
The constraints that genuinely cannot be relaxed, how to work around one honestly, and why recording the attempt matters more than the outcome.
Some constraints do not move. The document is current, the author confirms it, the risk holder says no, or the arithmetic shows the pattern collapses without it. That is a legitimate end to the exercise and it needs recording as carefully as a success.
The test in “What to Do When It Will Not Move” needs an unchanged baseline and a trustworthy record of what happened after the change. Teams exploring how should teams assess how to detect mouse jigglers? for how to detect mouse jigglers can strengthen that comparison while preserving corrections, exceptions and the decision owner’s explanation.
What should not happen is the third outcome, where nobody decided anything and the constraint remains in place by exhaustion.
For an outside reference relevant to “What to Do When It Will Not Move”, consult SHRM timekeeping resources. Compare the general material with the organisation’s jurisdiction, sector and written agreements.
The four honest reasons a constraint stays
It is externally required. It manages a risk somebody is accountable for and they are not prepared to accept the alternative. The people affected do not want it changed. Or the cost of changing it exceeds the cost of keeping it.
- It is required externally and nobody here can vary it.
- It manages a risk somebody is accountable for, and they will not accept the alternative.
- The people affected do not want it changed.
- The cost of changing it exceeds the cost of keeping it.
Each is a decision with an owner, and each is a different entry on the register.
The difference between no and not now
A great many refusals are really timing: not during the peak season, not while the vacancy is open, not until the new equipment lands.
Those should be recorded with the date they become possible. A register full of permanent noes is demoralising and usually inaccurate; the same list with dates is a plan.
Working around it honestly
Where a constraint stays, the question becomes what can be done given it. That is different from pretending it is not there, which is the usual response.
Adjusting the shifts around the constrained one, changing the order of work, moving a task to a different day — the surrounding arrangements are often more flexible than the constraint itself and have never been examined because all the attention went to the constraint.
The constraint that is doing something else
Some immovable constraints are proxies: a rule about staffing that is really about trust, a pattern that is really about pay, a requirement that is really about somebody's workload.
Where a constraint will not move and the reasons keep shifting, the subject of the conversation is usually not the one being discussed. Finding out what it is takes a different kind of conversation and is frequently where the actual problem has been all along.
Telling people it will not change
Clearly, once, with the reason. Ambiguity here is worse than a no: people continue to expect a change, plan around the possibility and are disappointed twice.
Where the reason cannot be shared in full, say that as well. "This is required by a contract I cannot share the terms of" is a complete and credible answer.
Recording the attempt
The constraint, what was proposed, who decided, the reason, and the date it should be revisited.
This is the entry that saves the most future effort. Without it the same proposal is made every eighteen months by somebody new, refused for the same reason, and the refusal is experienced as obstruction rather than as a settled position.
Revisiting
Everything on the immovable list gets looked at once a year, briefly. Circumstances change: a contract is renewed, a risk holder moves, a piece of equipment is replaced, a service redesign opens the question.
Most years nothing changes. The review takes twenty minutes and occasionally finds that a constraint everybody treats as permanent expired eight months ago.
What the immovable list is for
Two things. It tells whoever builds the rota what the real shape of the problem is, which is useful every fortnight. And it tells whoever is asked to improve the rota where not to spend their time.
Both of those are worth having even if nothing on the list ever moves, and the list is also the evidence that somebody looked.
The constraint that moves when something else does
Worth noting against each immovable entry: what would have to change for this to become possible. A different contract, a second qualified person, a room, a decision somebody else owns.
That field turns the immovable list into a set of conditions, and when one of those conditions is met for an unrelated reason — as happens every couple of years — somebody notices. Without it, the opportunity passes unobserved, which is how constraints outlive their reasons in the first place.
The sentence to end on
"We examined this, here is why it stays, here is when we will look again" is a defensible position in front of any audience: a team, an auditor, a regulator, a tribunal.
"That is how the rota has always been" is not, and it is the answer every organisation gives until somebody writes the register.