The abbreviations that mean two things
Most abbreviations are only mildly annoying: you do not know them, you look them up, you carry on. The ones worth a page are the ones where you think you know them and you are wrong, because the same letters carry two established meanings in adjacent worlds.
| Letters | Sense one | Sense two | How to tell |
|---|---|---|---|
| MVP | Minimum viable product | Most valuable player | Product context versus sport. In a company that does both -- a sports platform, say -- it genuinely does get confused. |
| POC | Proof of concept | Point of contact | A POC that is a person gets a name next to it. "Who is the POC" is always the person; "build a POC" is always the concept. |
| BOM | Bill of materials | Byte order mark | Manufacturing versus text encoding. A third sense, beginning of month, turns up in finance. |
| ETA | Estimated time of arrival | Edited to add | Logistics versus forum posts. In a comment thread, ETA at the start of a paragraph is almost always an edit note. |
| EOM | End of month | End of message | In an email subject line it is end of message and there is no body. Anywhere else it is the calendar. |
| OP | Original poster | Original post | Person or thing. "OP said" is the person; "in the OP" is the message. |
| SLA | Service level agreement | Stereolithography (3D printing) | Contracts versus resin printers. Rarely confusable in context, which is the exception here. |
The useful habit is not memorising which is which. It is noticing when a sentence would still parse under both readings, and asking, because the cost of asking is a message and the cost of guessing wrong can be a week of work.
Deadline abbreviations promise less than they look like
EOD, COB, EOW and ASAP all look like deadlines and none of them name a time. EOD means the end of somebody's day, and in a team spread across timezones that is a spread of eight or nine hours. COB is nominally close of business, which assumes both parties agree what business hours are. EOW is Friday unless the working week runs Sunday to Thursday, which it does across much of the Middle East. And ASAP is not a deadline at all -- it is an intensity marker, and in an inbox where everything is ASAP it conveys nothing.
If a date matters, write the date and the timezone. "By 5pm Thursday UK time" cannot be misread, takes four more words, and removes an entire category of dispute about whether something was late.
Shipping abbreviations decide who pays
The freight terms are the ones with money attached. FOB names the point at which title and risk transfer from seller to buyer: under FOB origin, the goods become yours at the seller's dock and a loss in transit is your loss and your insurance claim; under FOB destination, they remain the seller's until delivery. It is two words in a quote and it can be the whole difference in an argument about a damaged pallet.
LTL and FTL decide how the freight travels. Less-than-truckload shipments share a trailer with other consignments, get cross-docked and re-handled at terminals along the way, and arrive later and with a higher damage rate. Full truckload is one truck, one journey, handled at each end only. For anything fragile the extra cost of FTL is often cheaper than the claims.
MOQ, PO and RMA are the operational three. Minimum order quantity determines whether a supplier is usable at your volume at all. A purchase order is what makes an invoice payable, which is why suppliers ask for one before shipping. And an RMA number is what stops a return disappearing into a receiving bay with no way to connect it to your refund.
Writing with them, and when not to
An abbreviation is a compression that assumes shared context. Inside a team, it saves time and signals membership. Outside it, it does the opposite -- it makes the reader stop, and if they cannot resolve it, it makes them either guess or ask, both of which cost more than the words you saved.
Three reasonable rules. Expand on first use in anything that leaves the team: "single sign-on (SSO)" once, then SSO throughout. Avoid them entirely in anything with legal or safety weight, where an ambiguous reading has real consequences. And do not use chat abbreviations in external writing -- TBH, SMH and IMHO read as informality in a message and as carelessness in a document.
The one exception worth defending is TL;DR. A genuine two-line summary at the top of a long message is a service to the reader, and the abbreviation itself has become the standard label for it.
Questions people ask
Does MVP mean minimum viable product or most valuable player?
Both are standard and the context decides. In software, startups and product work it is minimum viable product -- the smallest thing you can put in front of users to learn something real. In sport and in general conversation it is most valuable player. If a sentence works under both readings, it is worth asking, because the two mean nothing alike.
Is EOD the same as COB?
In most workplaces they are used interchangeably. Where people draw a distinction, COB implies the end of business hours in the sender's location and EOD implies whenever the sender finishes work, which in a distributed team can be much later. Either way neither names a clock time, so if the deadline matters, write the hour and the timezone.
What is the difference between OEM and aftermarket?
An OEM part comes from the manufacturer that supplied it to the assembly line, so it is the same part the product shipped with. Aftermarket is everything else, and it spans a very wide range -- some aftermarket parts are made by the same factory without the branding, some are improvements on the original, and some are considerably worse. The label tells you the source, not the quality.
What does FOB actually change?
Who owns the goods in transit and therefore who bears a loss. FOB origin means title passes at the seller's dock, so damage or loss on the road is the buyer's problem and the buyer's insurance claim. FOB destination means the seller carries it until delivery. It is a small phrase on a quote with a large consequence when a pallet arrives crushed.
Why is TL;DR written with a semicolon?
Because it abbreviates two clauses: "too long; didn't read". The semicolon is doing the same job it would in the full sentence. It appears as TLDR and TL;DR interchangeably, and both are searched for, so either is fine in practice.