After You Hand the Decision Back
They keep bringing the call back because the last time they made it, you changed it.

You told them it was their call. You defined the boundary. You walked away. They still brought it back an hour later.
That is not because they forgot. It is because the last time they decided, you quietly changed it after they did.
The Answer Key does not stop when you stop answering. It stops when they stop needing the answer.
Picture a second-shift lead who has heard the speech. The supervisor said the sequencing calls are theirs. The boundary is clear: stay inside the existing priority, do not move the rush job, call if the customer changes the date. The lead makes the call. It works. Then the supervisor walks by, sees the order, and quietly swaps two jobs “just to help.” The lead notices. Next time the same question comes up, the lead brings it back. Why risk the correction when the faster path is to ask?
That is the failure mode. Handing it off is the start. Checking the thinking and leaving the result is the rest. If you take it back because your answer is faster, you taught them that asking is safer than deciding.
The objection is real: they get it wrong. Yes. That is the point of practice. The cost of them getting it wrong once is smaller than the cost of them never getting it at all. A wrong call inside the boundary teaches the standard. A perfect call you made teaches them to wait.
Tomorrow: when they bring a routine call you already handed off, ask three questions before you touch it. What do you see? What do you recommend? What would change your mind? Then let them make it. Review the result later, not the decision in the moment.
The room gets quieter when the answers live on the floor instead of in your head.
Marc Bradburry · bigbeardedginger.com/after-you-hand-the-decision-back/