Benefits of setting and following standards include ease of use and common usage. If everyone knows the standard way to implement an ERC-20 token contract, things are simplified. Like using an SOP, Standard Operating Procedure, in the real world. It’s demanded by many companies who must follow regulations, like pharmaceutical or food production, that their employees follow the written standard ways of doing things. A written standard allows for auditing of procedures to uncover irregularities and non-adherence to the protocol. With some type of governance protocols and contracts can be improved upon in a regular fashion. I like how Ivan stated that having a standard will reduce friction.
The ERC-20 Token Standard specifies that each token smart contract include the name, totalSupply(), symbol, and decimals for the given token. Token names are usually short, like one or two descriptive words, totalSupply() refers to how many tokens will ever exist, and symbols are 3-4 characters that represent the token, like a stock ticker. Decimals describes how finely divided each token is, ranging from whole numbers where decimals equals zero, up to 18 divisions.
Token contract functions include balanceOf() which allows you to query the balance for any address and transfer() which allows direct sending of tokens from one address to another. When sending tokens to a smart contract additional steps are needed so approve(), transferFrom() and allowance() are used together. Allowance refers to the number of tokens that a particular address can transfer, but allowance can be larger than an address balance so checks must be made prior to using transferFrom().