The starting point
A problem arrives. The decision is still yours.
“Service can’t do Friday. The customer is upset. What should I tell them?”
What this changes
You still have to find an available date, weigh the customer’s options, and decide what to promise.
What to do next
The gain to practice: bring a recommendation with the facts needed to make the decision.
What to keep. Keep the original request and record how long it takes to reach a decision. This is the starting record, not a result.
The next attempt
The manager does the preparation before escalating.
“I recommend moving the installation to Tuesday. Service has confirmed two engineers for that date; Friday is still unstaffed. Please approve Tuesday by noon so I can confirm it with the customer.”
What this changes
Now you can approve the recommendation or challenge it. The date, capacity, tradeoff, and decision deadline are in the request.
What to do next
Before sending: ask a colleague to make the decision using only this message. Add what they had to ask for.
What to keep. Save the revised request and the decision time. A clearer message is evidence of a changed behavior; it is not proof that the installation succeeded.
Back in the operation
Check the work after the message is sent.
“Did the installation happen on the agreed date? What follow-up was needed? What should I check earlier next time?”
What this changes
Read the request, the approval, and the installation record together. A well-written recommendation can still lead to a missed commitment.
What to do next
Compare decision time with the starting record. If staffing changed, record that too. Choose the next gain from what actually happened.
What to keep. Awareness: what the manager spotted. Behavior: what they did. Circumstance: what happened in the operation. Keep all three visible.