When we started down the path toward Salesforce-ification, it involved lots of bulleted feature lists. Maybe 1-2 wireframes. Then this was handed to contractors who implemented it exactly as written without an eye towards usability. Simple things like saving a ticket with some fields blank or unknown we’re not supported and made the entire ticketing process miserable.
I eventually stepped in as the voice of the “customer”, customer in this case being fellow engineers and support staff. I eventually left the company before the final implementation, but even by then no one prioritized usability and design.
Even trivial amounts of text can put people off, even when the individuals are supposedly high calibre (ie university educated/heavily interviewed)
The problem is this encourages brevity to the point of omission by the writers of tickets and then these various ticketing systems lose a big chunk of their value because no one has much of a clue what they're for afterwards!
On the one hand, companies ask me to put all this work into my tickets. Fill out this field, fill out that field, link to this thing, organize it this way... etc.
On the other hand, the company puts NEAR ZERO real effort into making this experience easy and efficient.
I've seen it happen most often with companies that flip-flop between defining themselves as a "start-up" but in the same breath talk about their worldwide enterprise presence. Of course they have 500+ employees. Sometimes thousands. They like to put on their startup hat when refusing to pay money for things and they like to put on their large scale enterprise hat when instituting ticket requirement policies.