Here is a tale from an invented parts desk inside a maintenance shop. Three people share one inbox and one counter. They handle incoming hardware, match it to work orders and answer a constant stream of “where is it?” calls from the hangar floor. Nothing about their work is glamorous. What changed their year was a stack of if-then rules, short written agreements about what happens when a predictable problem shows up. None of it really happened, yet plenty of readers who have worked a receiving counter will recognise the shape of it.
The situation before the rules
Every morning started the same way. A box would arrive and somebody would open it. Sometimes the paperwork was missing. Sometimes the quantity was short. Sometimes the part looked right but the label did not match the order. Each time, the person at the counter had to decide on the spot what to do, and each person decided differently.
One technician would hold the box until the supplier answered an email. Another would quietly shelve it and hope. A third would phone the hangar and promise it would be ready by lunch. The supervisor spent most afternoons untangling who had promised what to whom.
The cost was not only time. Stress built up, small errors crept in, and the same arguments came back every week. The supervisor eventually admitted the team was not short on skill. It was short on pre-made decisions.
Building the first rules
The supervisor called a short meeting and put a simple question to the group: which five problems did they handle most often? They wrote them on a whiteboard. For each one, they agreed on a single response, phrased as an if-then sentence, and kept it deliberately plain.
- If a shipment arrives without the expected paperwork, then it goes to a marked hold shelf and the supplier is contacted the same day.
- If the quantity is short, then the team receives what is there, records the gap and tells the requester.
- If a label and the order disagree, then nobody shelves the item until a second person has compared both.
- If a request is marked urgent, then the desk confirms the status within the hour even if the answer is “not yet.”
- If something cannot be matched to a work order, then it is tagged and listed on the Friday review sheet.
The wording mattered. The team avoided anything that sounded like a policy document. Each line had a clear trigger, a single action and an owner implied by the role at the counter.
The hardware mix-up that tested the system
A few weeks in, a box of small fasteners arrived. The labels looked right at a glance, but one of the technicians noticed a mismatch with the order sheet. Under the old habits, the box might have been shelved and found later by someone in a hurry. This time, rule three applied. The item stayed on the counter until a colleague compared the label and the order line by line.
The mismatch was real. The supplier had shipped a similar but different item. Because nobody had yet issued it to the floor, the fix took a single email. The supervisor later pointed out that the rule had not required any special skill, only the discipline of doing a second check before shelving. For anyone who wants background on why this area deserves care, a post on the basics of aircraft fasteners and hardware is a sensible companion read.
Where the rules paid off most
The biggest gain turned out to be on the phone. Before, a call from the hangar triggered a scramble. Afterwards, the desk could answer in a sentence: it is on the hold shelf, the supplier has been contacted, and you will hear from us by the end of the day. Requesters stopped calling back every twenty minutes because they knew what the process was.
The second gain was onboarding. A new hire joined in the fourth month and was productive within days, because the answer to most odd situations was already written on the wall above the counter. The supervisor no longer had to be present for every judgment call.
The third gain was less visible. The team stopped arguing. When a rule did not fit, they changed the rule rather than relitigating the incident. Conversations became about wording, not blame.
What went wrong along the way
Progress was bumpy. The first draft of the rules had eleven lines, and nobody remembered them. The team cut it to five and added new ones only when a problem had appeared at least three times. Another early rule read “if something looks wrong, then escalate,” which was too vague to follow. It was replaced with a precise trigger and a specific person to inform.
There was also a drift problem. After a busy stretch, the hold shelf filled up with items nobody revisited. The fix was another if-then line: if an item sits on the hold shelf past the end of the week, then it appears on the Friday sheet with a note on who is chasing it. The rule that protected the process needed its own backstop.
A note for crews who travel for work
Parts people sometimes visit suppliers, trade shows or distant shops. Travel brings its own predictable snags, so the team wrote a couple of travel rules too. If a flight is delayed, then email the host and shift the meeting rather than rush. If a phone loses signal abroad, then rely on the contact sheet stored on the handset itself. Those who cross borders can look at eSIMRoamly’s country and plan pages for SIM and eSIM options before they leave, so the connectivity question is closed in advance.
On the money side, the team also wrote a rule about the monthly budget. If a purchase pushes the month past its limit, then it waits for approval. The article on errors buyers make with control system components reinforces why a pause before purchase is worth building into the routine.
Lessons you can copy tomorrow
- Start with the problems that already repeat, not the ones you imagine.
- Keep every rule to one trigger and one action.
- Post the rules where the work happens, not in a shared drive.
- Review them on a schedule and delete lines that no longer earn their place.
- Treat a failed rule as a drafting problem, not a people problem.
The imaginary team still has bad mornings. A box still arrives with the wrong paperwork or a supplier still sends the wrong item. The difference is that the first reaction is no longer a debate. It is a sentence on the wall, and everyone already agreed to it. For a desk that lives on accuracy and small details, that quiet agreement is worth more than any heroic recovery.

