Abbreviations are a common source of friction between users, maintaining staff and developers. For example, imagine a user comes across an abbreviation they don't understand during a payment process and have to cancel the payment. They contact maintenance, who have to say it's nothing to do with them. User gets annoyed pretty quickly, so do maintenance staff. Maintenance then get onto the dev and tell them to fix it, but the dev has other more important things to do.
You get the point. And whether your system is dealing with critical issues like payment or not, it's wise to keep less well-known abbreviations well away from users. My suggestions for your problem:
- You can and should use abbreviations while developing. They will make processes quicker, even if only marginal.
- You should remove any and all undefined abbreviations from your system before it goes live.
- You should provide definitions for any abbreviations left in. This is often done in the form 'Abbreviation Text Here (ATH)'. After this you can use the abbreviation without definition.
Some references, mainly for grammatical accuracy and international standards compliance:
Also from the Grammarly page:
It's important that when writing, your reader doesn't get so bogged down in figuring out the short forms that they forget what they're reading.
Good advice to follow. Where users are concerned, use abbreviations sparingly.