Your support problem may not actually begin in Support.

The observation

Support is measured on how well it resolves work, but a meaningful share of that work was manufactured somewhere else — in a confusing process, an unannounced change, a policy nobody explained or a system that fails on schedule.

Why it happens

Support is the only function whose queue is filled entirely by other people's decisions. Every unclear instruction, every gap between two teams and every predictable defect eventually arrives as a contact.

Because the volume lands in one place, it looks like one team's performance problem. Leaders then optimize the team that received the symptom rather than the process that produced it.

What it may be costing

• Capacity spent resolving avoidable demand, repeatedly.
• Improvement effort aimed at handle time when the real lever is volume.
• A support organization that gets steadily better at absorbing a problem nobody upstream is asked to fix.

What I would look at

1. 01Take one week of tickets and classify them by origin rather than category: product, process, communication, change, access, or genuinely novel.
2. 02Find the top three origins outside Support and put a name to each one's owner.
3. 03Ask whether any upstream team currently sees the volume they create.