I honestly think a lot of coders fail to realize just how far they've come, sometimes. Programmers seem to settle into ends of the spectrum ego-wise (either they think they're the hottest shit that ever excreted, or that they know nothing), and so I think those towards the latter end don't always realize that small fixes can have great user impact in some cases.
Little things, as always, can have big impacts. :)
(related to this, my business classes exposed me to some small-to-medium org experiences and stories, and one of them was about a dev who was frustrated to be stuck with handling "internal support" just as much as development -- company was too small to have any sort of filtering for that stuff.
they solved a lot of flooded emails by application of a direct interaction process, which I've run out of space to outline properly -- but will next toot
So: They'd visit their users, and they were in a small enough business they could do so directly, one-on-one, for five minute walk-by check ins. "Hey, I know we talked about X issue. Is it working okay for you?"
That reduced one major problem they had -- people would have a problem, the 'solution' solved a technical aspect but not a user aspect, and so the user issue was 'solved' ticketwise, but unsolved and slowing the worker in reality.
Those issues sometimes needed a promise of return -- "I need to get some notes, but I'll email you once I've looked into it" -- but even that, once followed up, usually improved employee experience.
The question right after would be "Are you having any problems now?" This usually provided one or two extremely simple, or genuinely impossible, user issues, which could be demonstrated in real time in front of the dev.
The simple ones were fixed the easy way. "Oh, no, no. There's a key for that. Ctrl-N does it." The impossible ones were handled a little less directly, with an explanation of why it was impossible or infeasible, and a basic apology of a sort. "Yeah, we'd have to put half the servers into handling that kind of thing. I'm really sorry."
This shit cut the dev's 'tech support' time significantly, for the cost of (IIRC) an hour of talking to people.)
Not to say, of course, that ticket systems lack value. It's simply that some users don't 'fit' a ticket system -- and they always exist. The user who pulls a P&R Jerry move and searches up Google, then Googles Yahoo! Mail -- they're always gonna exist.
If they're Jerrying and can be shown better ways, that's useful. If they want impossible things, having that stated and empathized at least gives them the feeling someone is sorry it can't be done.