What follows is an invented story about an invented hospital administration team. Treat it as pure make-believe: no real organisation sits behind it and no real person is in it. The aim is to show, with a plain narrative, how a set of people-process habits known as PeopleOps plays out inside the non-clinical side of a cancer care setting. Nothing here touches treatment, patients or medicine.
Monday: the rehire nobody planned for
The operations manager of a mid-sized cancer hospital opened her inbox to find a note from the records office. A coordinator who had left the previous year was coming back on a short contract, and the old account was still on file. Someone had already switched it on, because that was the quickest way to get her working. The manager felt a small chill. What else came back with that account?
She pulled the history. The coordinator had once worked in billing support, then in scheduling, and her old login still carried rights from both. Nobody had misbehaved. The system had simply remembered everything.
The team gathered around a table and sorted the problem into three parts. The first was the rehire itself. The second was the way access piles up when people change posts. The third was that nobody could say, with a number, how long it took to close an account when someone left. Those three questions happen to be the same ones raised in the Ops Atlas write-up on PeopleOps, which the manager had been reading on the train.
Tuesday: reading the reference with a pencil
The Atlas describes the employee journey as a chain of owned transitions on top of one dated record. It lists several risky moments in that chain, and the team found all of them uncomfortably familiar. An accepted candidate who never turns up, though an account was already built for them. A person who departs while on leave, so the leaving date falls in a quiet period nobody is watching. A rehire whose earlier access is reactivated along with the identity. And the mover whose access only ever grows.
On the rehire, the entry is direct: bring the person back with a fresh identity record and none of the earlier permissions, then grant what the new role needs. The manager wrote that on the whiteboard in capital letters.
Why a worker number matters here
The records office had matched the returning coordinator by email address, which had changed since her first stint. The Atlas warns about precisely that: a permanent worker ID should be the key, never an email, because addresses change with name changes and with rehires. The team realised that two of their systems still joined people by email, which explained a duplicate entry the payroll clerk had complained about in the spring.
Wednesday: a modest plan, not a department
It would have been easy to ask for a new team. The manager resisted. In the Atlas, a small organisation working in one country is told to appoint one accountable owner and lean on a decent provider, not build a large function, and it labels its own size guidance as editorial opinion rather than benchmark. She appointed herself the owner for six weeks and listed what she would do:
- Issue a permanent worker number to every staff member and use it in every list.
- Enter leaving dates in advance, with the exact time they take effect.
- Compare three lists every working day: the leavers list, the roster and the active accounts.
- Re-read access whenever someone changes post.
- Write a short promise for how fast a leaver’s access should close, and check it.
The last item is where the Atlas gives numbers to borrow. One of its sample targets: close access inside an hour for ninety-nine per cent or more of leavers. The team felt this was ambitious for a small office, so they started with a same-working-day promise and planned to tighten it later.
Thursday: the awkward discovery
The first daily comparison turned up two accounts belonging to contractors who had finished months earlier. Nobody in the hospital had thought of them as employees, so no leaving date had ever been entered. The Atlas touches on this as well: temporary-staff arrangements often run through procurement rather than the people function, and orphaned contractor accounts are a common failure. The fix was not clever. The team agreed that the contracts desk would send a notice to the roster owner whenever a contractor finished.
They also found a shared login used by the evening reception desk. It belonged to no person, so it would never appear on any leavers list. The Atlas lists shared credentials and automated bots among the things teams forget. The manager replaced it with individual logins and moved on.
One more rule: never queue the sensitive stuff
While reviewing the help mailbox, the team noticed that a staff concern about a colleague had been sitting in the same shared queue as holiday requests. The Atlas calls for a private route for employee-relations cases, kept away from any shared view, and the manager set one up the same afternoon. She did it quietly, with one named contact, and told staff where the route was.
Friday: what changed, and what did not
Five days in, the hospital had bought no software and hired nobody. What it did have was a rehire rule, a worker number, a daily three-way comparison and a written promise about leavers, which cost almost nothing but attention. The manager also pinned a one-page summary of the new routine beside the records office door, so that whoever covered during holidays would not need to ask what the rules were or why they existed. For anyone interested in how steady routines keep complex systems running, the post on keeping a fleet of working robots moving with simple routines makes the same point from the engineering side.
The things left untouched were just as telling. Pay decisions, performance conversations and workforce planning stayed exactly as they were. The Atlas is clear that development talks, pay talks and under-performance should not be mixed into one conversation, and that rating-based pay needs calibration, but the team had decided to leave all of that for a later quarter. Doing a little properly beat promising a lot.
What a real team could take from the story
Because this account is invented, treat its details as a thought experiment. The useful bit is the order of work:
- Start from an incident or near-miss, since it makes the case better than any slide.
- Name one accountable person rather than creating a committee.
- Fix identifiers before fixing anything else, because every later comparison depends on them.
- Pick a promise, measure it and tighten it slowly.
If your own team wants wider context on how operations disciplines relate, the article explaining XOps, its disciplines and study routes is a reasonable companion. PeopleOps simply points the same measuring habits at the people side of the building.
Finally, remember the limits the Atlas sets for itself. It is not legal advice, it is not surveillance of individuals, and its figures are examples to learn from rather than targets imposed from outside. A hospital administration team can borrow the habits freely and leave everything else.
