Organization Would Introduce a Policy

¶ … organization would introduce a policy of wearing identification badges so people who work for the company could be more easily recognized (Anderson, 2005). Additionally, visitor badges are worn so the employees can tell who the visitor is and that he or she is allowed to be within the organization (Anderson, 2005). Visitors are required to sign in to get their badge, so it is safe to assume that a person with a visitor badge has signed in and the organization knows that the visitor is present. The same is true with employee badges. Each employee will have a badge issued to him or her, and that will allow the organization to determine who is an employee and who is not. However, because there are offices within the company that are not in the United States, there is the possibility of misunderstandings with the language barrier. There are, fortunately, ways to correct this potential problem.

In order to implement the policy throughout the entire company, the best thing to do is to be sure that the information about employee and visitor badges is translated into every language employees speak, and into every standard or common language which is spoken in the countries where the offices are located. That allows the employees and visitors to read important information about the badges and does not require the workers or the front office staff to speak every potential language that an employee or visitor might speak. The translation must be done correctly, however, by those who speak both English and the other language fluently. If the translation is not correct, it could be a serious problem and lead to a large number of misunderstandings. As long as the employees and visitors are properly addressed and the information is provided clearly, there shouldn't be any reason why the badge policy cannot be implemented in all of the company's offices, no matter where they are located or what language the people speak.

There are many things in an organization that are considered bad practice (Stone, 2008). These include shared accounts, unique user accounts without required passwords, unique user accounts where the password does not need to be changed, and administrators who use their privileged accounts to perform user activities. Shared accounts are a poor choice because they allow too many people access to the same thing (Stone, 2008). The administrator accounts have the same problem. Unique user accounts are a better choice, but if the password never needs changing it can eventually be hacked, and if the password is not needed at all there is very little to stop other people from using the account even if it is supposed to be unique to a particular user (Stone, 2008). That is worth considering, because it is much safer to have unique user accounts with required passwords that have to be changed as strict intervals.