Sustainable Pace on a Rescue — Personal Rules That Survive the Push

The handover was a third go-live date, a PAS-to-EPR interface that had already missed two cutovers, and a Slack channel named War Room with no planned close. The programme director asked, reasonably, whether I could just be available evenings until it worked. Nobody had written what until meant. The date owned the calendar. My remaining hours were about to become the unofficial buffer.

That scene is more common on a rescue than delivery culture likes to admit. It is also more recoverable than either a hero story or a rest manifesto will say.

Rescue Pace Is Not a Rest Essay

A rescue is not a hot programme with worse slides. The stall is already public. Trust is already thin. The social script is already written: if you cared, you would stay until the interface cleared.

That script is efficient. It converts unnamed hours into apparent commitment. It also hides the only capacity the plan never budgeted: you.

Rest-as-resistance writing makes the other error. It treats every extra hour as a betrayal of sustainable pace, as if the cutover were optional theatre. Dates on a patient administration switchover are not theatre. A ward still needs the feed to land. Pretending otherwise is how reserved people get talked over by whichever manifesto is louder that week.

Sustainable development, in the sentence that actually got signed, is a constant pace that sponsors, developers, and users can hold indefinitely. A named, finite push is not a contradiction of that sentence. An unnamed one is. The first has an exit. The second becomes the new baseline, because nobody can point at the moment it was supposed to stop.

The named push is still work. The unnamed one is how you vanish.

The Push Window

Call the named version a Push Window: extra hours with a duration, an exit criterion, and a person who may extend it. If those three are missing, you do not have a surge. You have an overtime policy that never went to a steering pack.

On the PAS rescue the director wanted a war room "until cutover." Cutover was six weeks out and had already moved twice. That is not a window. That is the rest of the quarter, spoken softly.

We wrote a window instead. Ten working days, evenings included, ending at dress-rehearsal plus one. Exit criterion: the late-file path either proved in the rehearsal or went on the risk log as unproven, owned by a named integrator. Extension: the director, in writing, with a new exit — not a Slack reaction at 23:40.

Beck's old XP rule is blunter than most modern rest essays, and more honest than most war-room invitations. One week of overtime can be a choice. A second consecutive week is a signal that hours are no longer the remedy. The Push Window is that rule, made visible on a rescue that will try to spend you by the hour.

You can still miss the date inside a window. You can also miss it after three unlabelled weeks, with worse mappings, because tired judgement is not extra capacity. Sleep restriction shows up in executive function and sustained attention, not only in mood. The morning after the third late night, I signed off a translation that treated a duplicate PAS identifier as a new patient. The defect was cheap to write at midnight. It was expensive at rehearsal.

Write the window before the first late night, not after the fourth. Once evenings have no label, asking for an end sounds like withdrawal. Naming it on day one sounds like a plan.

A window does not promise the date. It promises that the hours you do give still belong to thinking.

Self-Erasure

Self-erasure is quieter than burnout slogans. You remain employed. You remain the person they praise in the stand-up. You answer. You pre-read. You catch the file that arrives at 22:15. What disappears is the version of you that still has recoverable capacity — sleep, one protected hour, the right to be unreachable without a named exception.

The programme cannot see a buffer you never named.

So it will budget you forever.

The mechanism is not always the minutes. After-hours mail and chat are less poisonous, in the better studies, than the expectation that you are monitoring them. If that word expectation feels too mild, keep this version: the unofficial SLA. You do not need a full evening of work for the leash to stay on. You need the belief, shared in the war-room channel, that a quiet phone is a small betrayal.

On the PAS job the unofficial SLA was me. Integration questions routed to my handle after 21:00 because I had answered once, then twice. Detachment from work during non-work time is not a spa idea. It is the name researchers give to actually leaving the job in your head, and it tracks better sleep and — this is the part rescues skip — task performance. Stay mentally on the interface until 1am and you do not merely feel worse. You analyse worse the next morning, which is when the mapping still has to be right.

Intensive phone use after hours makes the same pattern worse, not because the device is magic, but because it keeps the leash in your pocket. A rescue Slack channel with no close date is that finding, wearing a programme name.

Self-erasure looks like loyalty. It is how a recovery programme quietly writes you out of your own week while still listing you as the analyst.

Standing Hour and Booked Recovery

A Push Window without a floor still spends you. The floor I will defend is one Standing Hour: a visible, recurring block that the war room does not get to eat, used for the analysis the evenings will otherwise ruin.

On the PAS rescue it was 08:00–09:00, labelled on the calendar as identifier-reconciliation, not as wellness. The war room could have me after 18:00 inside the window. It could not have the first hour, because that was when duplicate-ID defects were cheapest to catch with a working brain. A standing hour that protects a deliverable is programme hygiene. It is not a focus block you hold against a hostile calendar — that practice is separate. This hour has to survive a named push. A standing hour performed as self-care branding will be overwritten, and it should be — the room can smell theatre.

Booked Recovery is the sibling rule. If recovery is a mood you will have after go-live, you will not have it. Hypercare starts. The next fire starts. The next date is already in someone's deck. Put two half-days on the calendar before the window opens, named, after the exit criterion. Protect them the way you would protect a freeze. If the director needs those half-days, that is an extension of the window, with a new exit — not a silent cancellation.

People who cannot detach after work are not weak. Workload predicts that outcome; lack of detachment then feeds strain the next day. Booking recovery is how you stop pretending the nervous system will invoice the programme on its own.

None of this is a team overtime policy. You may not rewrite the organisation this fortnight. You can still name a window, keep one hour, and put recovery where a date can see it.

If a sponsor will not accept any exit at all, you do not have a rescue plan. You have an unnamed overtime culture. That is a different diagnosis than this article's.

All-In Until the Date

The strongest counter-argument is the one the director actually had. The Trust had already missed two cutovers. Commissioners were watching. A named window looks like a person protecting themselves while the organisation takes the risk.

That objection is right about the politics. It is right that a finite push costs visible hours the date might have used. Where it stops holding is in what unbounded hours buy. They buy presence. They do not buy better identifier logic, better exception paths, or a rehearsal that fails for an honest reason instead of an exhausted one. Extra time after a first overtime week, in the XP reading, is a symptom to investigate — not a second helping of the same remedy.

If you already said yes to unbounded evenings, retrofit the window mid-push. Write the end that should have been there. Name the next exit. "Two more days," said four times, is not a personality trait. It is the unofficial SLA with better manners.

The three rules are personal because they are the part you still own when the culture will not move this sprint. They are not a rest essay. They are how a rescue keeps an analyst who can still see the feed.

---

The rescue needs hours you can still think in.

It does not need you to disappear into the date.