When the Workaround Becomes the System
A terminal occasionally loses a booking. The person at the desk keeps a notebook beside it and writes down the reference number, calls the office at the other end and waits for confirmation. The customer receives the room they reserved. By the time anyone examines the incident, the practical problem has been solved.
The notebook records something the terminal cannot reliably retain, but its value depends on more than paper. Someone must recognize which booking has failed. They must know which office to call, and a person in that office must be available to check the record. A replacement member of staff needs to know all this before a customer arrives. The workaround is already an arrangement between people.
Suppose the faults remain occasional. The desk worker continues to resolve them, and the end-of-day report counts occupied rooms correctly. A manager can reasonably conclude that the process is functioning. Customers are being served, the figures agree and the repair has a cost. The manager need be neither stupid nor malicious. The information reaching the manager has been improved by the employee’s effort.
The next question is whether that effort remains visible. If the report records only the final result, two very different days can look identical: one in which the terminal worked and one in which the worker spent an hour reconciling bookings. The second day contains less time for other work. It also contains a dependency the first day does not have. A count of completed bookings cannot tell us which day occurred.
Now change one condition. The office answering the calls closes earlier, or the person who knows the reference numbers takes leave. The terminal has not become worse. The notebook is still beside it. Yet the desk worker can no longer obtain confirmation, and a procedure described as a fallback fails because one of its unrecorded conditions has changed. The customer experiences the failure at the desk, where the person with the least authority has to explain it.
A useful test would reproduce that absence before it became an emergency. Give the notebook and written instructions to someone unfamiliar with the process. Let them attempt a failed booking without help from its usual owner. Watch where they stop. If they need to call a particular colleague, record the need. If nobody can confirm the booking after a certain hour, the instructions should say what happens then. The test is unfinished until it reaches a real decision about the customer’s room.
This is also the point at which praise can become evasive. Calling the desk worker resourceful may be accurate. It does not answer who will maintain the workaround, train a replacement or decide when the terminal must be repaired. Those are different responsibilities. Appreciation cannot quietly transfer them to the person who happened to solve the first failure.
The operating hours matter as much as the reference number. If only the other office can authorize a room, a desk worker who has promised to resolve the problem may have no next step after that office closes. The completed-booking report will eventually register a failure. It cannot show how long the worker stood with the receiver to their ear while the customer waited for a key.