@Leones I am not saying you have to make an "owner's manual" of every little thing that happened. I am saying that in order for the masses to understand on why certain things are warranted precise answers would have sufficed. No one is buying the "internal reasons" excuse, especially if it's something that is a game changer for everyone that plays. I had 8 hours of work to do as well, but I do take the time in getting in touch with my clients to let them know what's going on and how long it's going to take; and I don't sugarcoat it, either. If something is bad, I am going to tell them that. If something is going to be good, they will know... because it's one less thing for anyone to sit and "wonder" about and they can go about on their day.
Like how in a restaurant you wouldn't expect the Chef to have the time to both cook the meal and do all the front of house tasks. You either would never get any food actually cooked if the chef had to take the orders and facilitate every transaction, or it'd tie them down so much trying to do everything themselves that the entire service would degrade in comparison to having a dedicated person to the task of serving.
You reminded me of a time where a well-oiled machine means something. I was like that Chef in your story with an incompetent partner (well, more like a complaining one). We were working in a building, trying to figure heads or tails as the last team didn't leave anything (not even as much as a note). I told him to assist the other vendor (HP) in moving the equipment while gathering data port information while I was dealing with a person who keeps calling me every 5 minutes requesting a status update. Twenty minutes later, he comes in asking "are we done yet?" I looked at him and ask if he was done with his task, which he answered "no". I told him to get back in there as I am still compiling a list since I have to walk between two floors worth of network rooms to translate their port information to what was on the user end (yeah, it was all "Greek" to me). Another twenty minutes and after telling the caller to "stuff it" since they cannot take a hint that I would call them to give them the update, he comes back and asks again "are we done yet?" I asked him one more time if he was done which he answered "no" again. This time, I asked him, "what were you doing in the last hour?" To which he answered, "nothing, just waiting on you." Oh my, you got to be kiddin' me. I was putting together a composite list to which I was also waiting on his information so I can enter it and he done nothing in that time. Time stopped for me as he told me that he wants to go home so he can get up to take his son fishing (granted, this was on a Friday night of all sorts). I closed my eyes and told him to go; but told him that the moment he leaves the building zone, his time will end. I usually reward people when we do things as a team in an efficient way that it would take if we done it separately. Alone and with odds against me, I took a few minutes to ask my friends in the HP for assistance while I call in my family to take on the mission, to which they arrived, team up with HP, and started to get things rolling. The nightmare that was on the phone was replaced by a friend I know all too well that everyone was done by 2am and went home. Three floors, two network rooms, one phone call. I had to answer for my "call" and decision, but it was later understandable on why.
Your chef should have a contingency plan in place. Replace the incompetent ones with those who can perform the task. And, if needed, get outside help as appropriate.