One Name on the Parts Order: A Hangar Story About Decision Rights

One Name on the Parts Order: A Hangar Story About Decision Rights

Hangar 3 at a small regional maintenance shop had a habit. Every time a part was needed, three people held a short meeting by the coffee machine, and every time the meeting ended without a purchase order. The aircraft sat on jacks. The customer phoned. The store clerk, the lead engineer and the finance clerk each believed the final say belonged to someone else. What follows is a made-up shop with a very real problem, told as a plain account of what went wrong and what the team did about it. The topic is how a named decision-owner turns a parts purchase from a standoff into a routine.

The setup: three people, three kinds of caution

The lead engineer, Dev, cared about fit and paperwork. He wanted every aircraft part to arrive with the right certificates and the right part number, and he would rather wait than risk the wrong item arriving. The store clerk, Lalitha, cared about shelf space and lead times; she knew which suppliers were slow. The finance clerk, Abdul, cared about the monthly cap and could see that rush orders cost more.

All three were sensible. None of them was wrong. But their cautions pointed in different directions, and since nobody had the authority to weigh them against each other, the default result was delay.

The week it cost them

A small control-linkage component was needed to finish a routine job. Dev found two suitable suppliers. Lalitha said the cheaper one usually shipped late. Abdul pointed out that the quicker supplier would blow through the weekly spending limit. They agreed to “think about it” until Monday.

On Monday, Dev had been called to another aircraft, Lalitha was on leave, and Abdul assumed the order had been placed. On Wednesday the customer asked why the work was not done. By Friday the shop had paid for a second, express delivery to catch up, which was precisely the cost Abdul had hoped to avoid. A decision-free week had been the most expensive option on the table.

What the shop owner asked

The owner, Mrs. Kulkarni, did not ask who was at fault. She asked a different question: “On a normal Tuesday, who is allowed to say yes to a parts order?” The silence told her everything. Nobody could answer in one sentence.

She sat the three down for twenty minutes and wrote four lines on a whiteboard:

  • Owner for orders under the weekly cap: the lead engineer.
  • Input needed first: the store clerk reports lead times, finance reports remaining budget.
  • Time limit: the order is placed within one working day of the request.
  • Above the cap: the owner decides, but must be consulted the same day.

That was the whole policy. It did not remove anyone’s expertise; it only put the closing step in one pair of hands.

Why the engineer, and not finance

Teams often assume the budget holder should always decide. Mrs. Kulkarni chose the engineer for routine orders because the biggest risk in aviation parts is a wrong or poorly documented item, and Dev was the person best placed to judge that. Abdul still had a voice; he supplied the numbers, and a breach of the cap triggered a conversation. The rule matched the decision to the person who would feel the consequences of a mistake most sharply.

Your own shop may reach a different answer. The point is not that the engineer wins. The point is that the choice is made on purpose, written down, and does not depend on who is in the building that day.

A month later

The next time a part was needed, the sequence took an afternoon. Lalitha posted the lead times in the shared sheet within an hour. Abdul posted the remaining budget. Dev read both, picked the slightly pricier supplier because the delivery window mattered, and placed the order before closing time. Nobody held a meeting by the coffee machine.

Dev later said the surprising thing was how little the policy changed in the way people behaved toward each other. Arguments still happened, but they had a shape and an end. He read a rundown of common errors when buying control-system components and noticed that several of the mistakes listed there arise when a purchase drifts without an owner.

What the policy did not try to do

Be exact about the boundaries. It never told the team which part to buy; that remained a technical matter. It did not remove the need for proper documentation. And it did not turn Dev into a dictator, since he still had to gather input and keep within the cap. What the rule did was answer one narrow question: when the talking stops, who acts?

For the technical side of hardware choices the shop keeps reference material handy, such as a guide to aircraft fasteners and hardware. Knowledge informs the choice. Decision rights close it.

Borrowing the idea outside the hangar

When Mrs. Kulkarni described the change at a trade evening, a colleague pointed out that her own family had the same problem on a larger scale. A relative needed to travel for care, and nobody in the family could say who was supposed to book the dates, gather the paperwork or manage the money. The family had been reading BestHeartSurgery, a reading portal aimed at people who may travel abroad for a heart operation, which is careful to say it offers information and nothing clinical. The reading was useful, but it did not settle who would coordinate the practical steps. They wrote their own version of the whiteboard that evening.

The no-nonsense checklist

If you run a parts counter, a small workshop or any team that buys things under pressure, try this over the next fortnight:

  1. List the recurring decisions that tend to stall: orders, returns, supplier changes, urgent exceptions.
  2. For each one, write the name of a single owner next to it.
  3. Add the time limit between request and action.
  4. Note what input the owner must collect before acting, and from whom.
  5. Define what pushes a decision up a level, such as a cost threshold.
  6. Pin the list in plain view and revisit it after a month.

Objections you will hear

“This takes authority away from people.” It tends to do the opposite. People who were never sure what they were allowed to decide now know exactly where their authority begins and ends.

“What about emergencies?” Write the emergency rule too. Usually it is: the nearest senior person acts, then informs the owner within the hour.

“Will the owner become a bottleneck?” Possibly, which is why the time limit matters. If the owner cannot act within the limit, a named deputy does. A deputy is just another name on the list.

Closing the story

By the end of the quarter the shop had stopped paying for express deliveries caused by indecision, and Abdul reported that the weekly cap was hit less often. Lalitha said she finally knew who to chase. Dev said he slept better. The aircraft on the jacks went back to their owners on schedule. None of it needed new software or a larger team; it needed four lines on a whiteboard and the willingness to put one name beside each.