Professional Documents
Culture Documents
ABSTRACT. The study examines employee, managerial, and ethics officer perceptions regarding their
companies codes of ethics. The study moves beyond
examining the mere existence of a code of ethics to
consider the role that code content and code process
(i.e. creation, implementation, and administration)
might play with respect to the effectiveness of codes in
influencing behavior. Fifty-seven in-depth, semi-structured interviews of employees, managers, and ethics
officers were conducted at four large Canadian companies. The factors viewed by respondents to be
important with respect to code effectiveness include:
provisions of examples; readability; tone; relevance;
realism; senior management support; training; reinforcement; living up to standards; reporting requirement; anonymous phone line; communicating
violations; and enforcement. The factors found to be
potentially important include: justification for provisions;
employee involvement; and sign-off requirements. Factors found not to be important include: objectives for
the code; prior distribution; testing; and relating ones
performance review to compliance with the code.
KEY WORDS: behavior, codes, content, effectiveness,
ethics, process
Introduction
Companies are increasingly being pushed towards
adopting a written document, typically referred to as
a code of ethics. For example, in the U.S., under
Mark S. Schwartz is Assistant Professor of business ethics and
business law at York University (Toronto, Canada). Previously he was lecturer of business ethics in the Legal Studies
Department at The Wharton School, University of Pennsylvania. He received his Ph.D. from the Schulich School of
Business, York University in 1999. His research interests
include corporate ethics programs, corporate social responsibility, and social investment.
Mark S. Schwartz
324
Mark S. Schwartz
325
326
Mark S. Schwartz
Code
Content
Employee
Perceptions of
Code
Code Effectiveness
(Legal and
Ethical Behavior)
Code
Process
Methodology
To explore the research question, the study consisted
of fifty-seven in-depth, semi-structured interviews
of employees, managers, and ethics officers at four
large Canadian companies. The selection of
respondents was random for three of four of the
companies, while a snow ball technique was used for
the fourth company. Of those contacted, 92% agreed
to be interviewed. A total of 58% of the respondents
were male (33/57), while 42% were female (24/57).
In terms of organizational level, 60% of the
respondents were managers (34/57), while 40%
were non-managers (23/57). Of the managers, 15%
(5/34) labeled themselves senior managers. Seven of
those interviewed were ethics officers, meaning that
they were responsible for the administration of the
code. The types of positions of the non-management
respondents included: telephone operators, sales
representatives, bank tellers, administrative assistants,
and assemblers on the production line. The range of
time working for the company ranged from 3
months to 33 years, with an average of 13.4 years
spent at the company. The researcher individually
interviewed all of the participants, with 51 of the
interviews being taped and transcribed. Upon the
request of several respondents, six interviews were
not taped, although extensive notes were taken of
their responses. The average length of the interviews
was 65 minutes. Respondents answers were coded
using qualitative research software (i.e. NUDIST)
and then analyzed according to the various categories of code development.
The companies represent a variety of industries:
telecommunications; banking; manufacturing; high
technology. They are among Canadas largest
companies, each earning billions in revenues and
having tens of thousands of employees. Three of
the four companies conduct multi-national activities. One of the companies was the subsidiary of a
U.S. parent company. The companies fall within
the upper echelon with respect to having well-
327
328
Mark S. Schwartz
impact code effectiveness, there were a few provisions that did cause some concern. Several provisions were perceived by respondents to be
unjustified on the basis of being too overbearing or
unfair, implying that these provisions would have a
greater likelihood of not being followed.
Inventions. For example, provisions dealing with
inventions, and the requirement of employees to hand
over any inventions made to the company, even if
they were developed outside of normal working
hours, was perceived as being unduly unfair:
I might have a bit of a problem with the section
that talks about patents and copyrights, if you come up
with an invention on your personal time that [the
company] says that it would claim, I dont agree with
that. If it is something that you do and it is something
on your own, it is not work related, but it turns out to
be an invention I dont think [the company] should
have the right to take the patent for that [emphasis
added].
The following respondent focused on the appropriateness of certain punishment for a potential code
violation: Should you lose your job if you are caught
throwing garbage on the road? [emphasis added].
329
Mark S. Schwartz
330
One:
Two:
Three:
Four:
55
21
65
25
Pages
Pages
Pages
Pages
A number of other respondents noted that although their codes might be considered lengthy, the
purpose of the document was to act as a reference
and therefore the entire document need not be read
at one time:
Well, you dont just go and read the whole thing.
I dont think it really could be shorter because I
think what happens is that some people get this
and they read it and they must go quickly through
it, and they put it away. So it is there as a reference
if they need it.
This factor may become more significant as several U.S. companies may choose to simply adopt
generic codes of ethics to comply with the SarbannesOxley Act as opposed to developing a code that is
more directly related to the nature of its business and
the activities of its employees.
(f) Realistic. If companies are expecting their
employees to engage in behavior which is perceived
by employees to be unrealistic or unattainable, many
suggest that the code has the potential to lose its
legitimacy (Harris, 1978, p. 312; Murphy, 1988, p.
909; Ethics Resource Center, 1990a, p. V-1). All of
the respondents believed that their codes were not
placing unrealistic demands or expectations upon
them. This belief appears to be confirmed by the
respondents stating that most if not all of their codes
are simply common sense as indicated above:
there is nothing in there telling them to do something that they cant do. Everything is in their clenches,
they can do it [emphasis added].
331
332
Mark S. Schwartz
333
The study found that although training was perceived positively by most of the respondents, too
much training could be perceived by employees to
be a waste of time and money, which may reduce
the legitimacy of the code.
Several respondents noted the value in training.
Essentially, training sessions provide the explanation
required for employees to become aware of the
codes usefulness, or at least to indicate the importance the company attached to the code:
[The training sessions] are how you make it real to
everyoneby showing them backing up a book.
Anyone can create a book, big deal. You back it up
with the session where you give examples why were
doing it, why do we have integrity, why is this so
important, how can your actions impact a [multimillion dollar] company? [emphasis added].
like, the room was just packed with people. You
obviously got the sense that it was very important I
mean [its very rare] that we all get together like that so
its usually something quite important [emphasis
added].
334
Mark S. Schwartz
(e) Reinforcement. Reinforcement through newsletters, e-mails, or executive speeches, has been suggested as playing a role in code effectiveness
(Trevino and Nelson, 1995, pp. 248253). This was
confirmed by the respondents who indicated that
without constant reinforcement, the code would
tend to have only a minimal impact on employee
behavior. Reinforcement appears to allow employees to perceive the seriousness and importance their
company places on compliance with the code.
Otherwise, the document becomes less of a concern,
and more easily disregarded:
its just a document. A document doesnt change
the culture, it doesnt change values, it doesnt change
behaviorwithout everything else the document is
just a document. You need the constant education, reeducation, awareness, examples and build that example
base and present it on a regular basis. Just putting in a
document, no [emphasis added].
One ethics officer discovered that the companys policies on expenses for working out during
business trips and drinking bottled water from a
hotel mini-bar conflicted with the codes emphasis
on health:
Employee Health: Okaywe talk in the code of
conduct [about] being healthy and family, all this
stuff, and I was in Hong Kong last year and I
paid my five dollars to go to a gym and work out and
when I got back I expensed it and it got kicked back to
me expense wise and they said, Im sorry we dont pay
for gym costs. Well thats crazy. A huge disconnect on
what we say and [what we do]We also said that we
dont pay for any kind of [drinks] from the mini-bar,
335
According to the respondents, perceived inconsistency between the code and how the company is
actually behaving appears to relate to the codes
potential effectiveness.
(b) Reporting violations. Most commentators suggest
that the ability to report wrongdoing is extremely
important if codes are to be effective (Gibbs, 2003, p.
40; Messmer, 2003, p. 13). Several researchers have
explored the individual and situational factors that
might influence whether employees report code
violations (i.e. blow the whistle). Some of the more
prevalent situational variables that have been considered to affect the decision to blow the whistle include:
the seriousness of the violation, perceived responsiveness, and the presence of others (Miceli and Near,
1988; Miceli et al., 1991; Sims and Keenan, 1998).
Each of the four companies codes discusses
employees obligations when they observe a code
violation. The provisions require employees to
report any and all code violations. The provisions
also indicate that failure to do so could result in
discipline. Respondents were asked how they felt
about the obligation to report all code violations.
Despite many respondents not being aware of the
reporting obligations as stipulated by the companies codes, most respondents still believed that
employees should be obligated to report all violations. By not reporting the violation, one was in
effect condoning the illicit behavior: I think
by not reporting certain things, then you are really
condoning their behavior, you are an accessory to
the fact.
Other respondents took a different position by
suggesting that companies may be creating code
provisions that are impossible to enforce:
I think that its pointless to say we can obligate you to
report wrongdoing how are you going to force me
to do it? People dont want to feel compelled [to
do] things. They might rebel if they feel that
336
Mark S. Schwartz
FACTORS
(i) Warning was Given
Aware of
Violation
Report
Violation
337
The respondents made it clear that without consistent and unbiased enforcement, the code may not be
taken seriously.
(f) Performance review. Contrary to the literature on
codes which tends to recommend rewarding ethical
behavior (Pitt and Groskaufmanis, 1990, p. 1645;
Raiborn and Payne, 1990, p. 888), most respondents
believed that compliance or doing the right thing is
already part of your job for which you are being
compensated, and therefore need not be explicitly
rewarded in any sense:
No. Because good ethical behavior is part of our job
You shouldnt be rewarded for doing something
that is expected of you. You should be rewarded for
going over and above the call of duty.
Its the right thing to do. Why should we be rewarded
for doing the right thing?
Mark S. Schwartz
338
TABLE I.
Code developmental stages and effectiveness
Code development
stage
Relationship to code
effectiveness
Concerns of respondents
Content
Justification
Examples
Tone
Length
Relevance
Potentially important
Important
Important
Important
Important
Realistic
Important
Creation
Objectives
Employee involvement
Not important
Potentially important
Implementation
Prior distribution
Not important
Prior distribution of minimal concern but couldnt hurt; employees will most likely not object to code content
Sufficient support from management must be observed or code
will not be taken seriously
Sign-off can generate increased awareness but potential indication
of lack of trust
Training must be sufficient or potential lack of awareness of codes
usefulness will result
Reinforcement must be sufficient or code will be considered just
another flavor of month
Testing ineffective; potentially patronizing
Senior management
support
Sign-off
Potentially Important
Training
Important
Reinforcement
Important
Testing
Not important
Administration
Living up to standards
Reporting violations
Important
Important
Important
Important
Not important
Code content
Companies should provide examples in the code
document or during code training, as well as main-
339
340
Mark S. Schwartz
Acknowledgement
The author gratefully acknowledges Wesley Cragg
and Linda Trevino as well as the anonymous reviewers for their helpful comments towards the
preparation of this article.
References
Adams, J. S., A. Tashchian and T. H. Shore: 2001, Codes
of Ethics as Signals for Ethical Behavior, Journal of
Business Ethics 29(3), 199211.
Akaah, I. P. and E. A. Riordan: 1989, Judgments of
Marketing Professionals About Ethical Issues in Marketing Research: A Replication and Extension, Journal
of Marketing Research 26, 112120.
Allen, J. and D. Davis: 1993, Assessing Some Determinant Effects of Ethical Consulting Behavior: The Case
of Personal and Professional Values, The Journal of
Business Ethics 12, 449458.
Arndt, S.: 1990. Discussion of Ethics Needed, National
Underwriter (Life,Health/Financial Services) 93(43), 313.
Austin, R. W.: 1961, Code of Conduct for Executives,
Harvard Business Review 53, (September/October).
Badaracco, Jr., J. L. and A. P. Webb: 1995, Business
Ethics: A View From the Trenches, California Management Review 37(2), 828.
Benson, G. C. S.: 1989, Codes of Ethics, The Journal of
Business Ethics 8, 305319.
Berenbeim, R. E.: 1988, Ethics Codes and Educational
Programs, Security (October) 9197.
341
342
Mark S. Schwartz
343