Why repeated questions cost more than the reply
The most expensive operational questions are rarely dramatic. They are small questions answered in several places by different people with different levels of confidence. The visible cost may be five minutes for a reply, but the full cost includes the employee waiting, the manager reconstructing context, and the next person repeating the same search.
Consider a monitor approval request. One employee asks in chat, another emails finance, and a manager raises it in a meeting. Even if all three receive an answer, the company has paid three times to identify the policy, find an approver, and explain the decision. Nobody can easily tell whether the answers matched.
Give every request a usable first handoff
A reliable intake path should capture the question, requester, relevant context, owner, status, and next step. The goal is not a longer form. It is to remove the follow-up message that asks who is handling the request or what information is missing.
Start with one high-volume category such as equipment, leave, purchasing, or system access. Define where requests enter, who owns the first response, and what “resolved” means. Keep the original conversation attached so a reassignment does not reset the work.
Measure whether people still need to ask twice
Review a small sample each month. Count requests that were repeated in another channel, reassigned without context, or reopened because the answer was unclear. Track time to first owner and time to resolution separately: a fast acknowledgment is useful, but it is not the same as a completed outcome.
The practical target is simple: an employee should be able to see that the request arrived, who owns it, and what happens next without sending another message. A shared request desk makes that state visible and leaves a record the next person can trust.