Promoting Ethical Behaviors in the Business Community

This article examines the proposal that “…Corporations and the people who make them up must have high moral standards and monitor their own behaviour because there are limits to what the law can do to establish and ensure that business behaviour is socially and morally acceptable (Shaw, Barry and Sansbury, 2009, p.206).


We begin by identifying the parties involved (i.e. the message giver and message receiver), clarifying a number of preliminary concepts and then applying ethical theory to deepen our insight on how they might respond. The discussion concludes by suggesting an alternative approach that would achieve the desired outcomes implied by Shaw et al. (2009) by appealing to the business community’s sense of enlightened self interest.

Discussion

There appear to be two parties to this statement; the message giver represented by Shaw et al. (2009) and the message receiver being the business community at large. I believe Shaw et al. (2009) is attempting to induce the business community into becoming more ethical in their behaviour. Given that the business community is primarily concerned with the outcome of generating value for shareholders, I would suggest that the ethical position for most (if not all) of the target audience members could be classed as consequentialist in the way Crane and Matten (2007, p.91) describes it. On the other hand, the stakeholder orientated language used by Shaw et al. (2009) suggests a non-consequentialist ethical position.

In the discussions that follow we will consider the key ethical responses to this statement however first there are a few preliminary concepts to clarify for the purposes of this essay; i) the assumptions underlying the statement, ii) a definition of morality and iii) origins of morality.

i) Assumptions underlying the Shaw et al. (2009) Statement

During the discussions on how the business community might respond we will reduce the Shaw et al. (2009) statement to the following key assertions:

1) Corporations have an obligation to maintain high moral standards.
2) Individuals have an obligation to maintain high moral standards.

3) Business behaviour is currently socially and morally unacceptable.
4) High moral standards are both definable and attainable.
5) Self monitoring of business behaviour will address the perceived gap left by the legal system

ii) Definition of Morality

Wines (2007) describes morality as the rules people have within them to operationalize their va

lues. However for the purposes of informing our sense of moral standard we will use the Crane et al. (2007, p8) definition of morality:

Morality is concerned with the norms, values, and beliefs embedded in social processes which define right and wrong for the individual or community” (Crane and Matten, 2007, p.8).

ii) Origins of morality

Dawkins (2006) offers an interesting commentary on the origins of morality in human beings. Dawkins (2006) suggests we are genetically predisposed to be moral and that these char

acteristics emerged from the lengthy evolutionary process. He cites in his supporting argument; genetic kinship, reciprocal altruism, reputation (of altruism) and advertising altruism to support this proposition (Dawkins, 2006, p.219). In essence individuals are statistically more likely to benefit if they adopt a behavioural strategy that exceeds a critical frequency in the population. This seemingly natural mechanism appears to have given rise to the complex moral awareness that human beings have today. Given our interest here in promoting ethical behaviours it’s important to understand how this natural mechanism can work in favour of improving the overall ethical disposition.

Apart from some evolutionary compulsions to exhibit altruistic behaviours the question of why we should be moral appears to be a key topic for ethical philosophers. Melden (1948) and Frankena (1958) seem to think this is an impossible question to answer due to, amongst other things, the difficulties defining ‘good’. Doing ‘good’ it seems, is a matter of perspective and there are many perspectives to choose from.

For the purposes of this essay, we will assume that what constitutes ‘good’ is in the eye of the beholder and in this case the beholder is the business community at large.

According to Crane et al. (2006), there are two consequentialist theories which may help us to understand how the Shaw et al. (2009) statement might be perceived by the business community. These are Egoism and Utilitarianism.

An Egoist interpretation:

I think this type of ethical lens (Crane et al., 2007, p.110) would feature strongly in the minds of the business community both as individuals and as a collective. The Egoist is chiefly concerned with their individual self-interest (Crane et al., 2007, p.93). To an Egoist business person reading this statement, the idea that individuals have an obligation to maintain high moral standards would certainly strike a chord. Especially since this would probably mean having to comply with an imposed set of moral standards that challenges their freedom of choice.

In a world where Shaw et al. (2009)’s statement has been realized, the Egoist would be looking for a personal benefit and probably won’t find one. I doubt whether the Egoist will care about corporate obligations or how business behaviour is currently perceived. On the other hand the Egoist may treat this statement as an opportunity to develop a moral façade as a way to enhance

career prospects. How this might be utilitised is of more interest to the next perspective, Utilitarianism.

A Utilitarian interpretation:

I think the Utilitarian business person would look at the Shaw et al. (2009) statement from a cost to benefit viewpoint. On the cost side the main part might be the moral obligations for both individuals and corporations over and above those required by company law. From the statement (Shaw et al., 2009) it’s not clear how onerous a high moral standard might be to maintain however it is likely to be a significant social investment. A move to this new moral world would also likely impact other social systems such as; the legal framework for businesses or the welfare system not to mention changes to the role of management. Corporations would be saddled with yet more obligations besides the usual shareholder focus.

On the benefit side meeting these obligations might position businesses well to meet an increasing public demand to behave ethically (Crane and Matten, 2007, p.9). Behaving ethically may actually be good for business according to research by Hosmer (1994) and commentary by Covey (2006). The utilitarian might also consider the distribution of benefits to be an improvement since an overall improvement in moral judgement might lead to better circulation of wealth. In my opinion the Utilitarian might view this as a worthwhile investment to make.

For Shaw et al. (2009) to appeal to consequentialists, it would need to use the language of outcomes. Outcomes that are ecologically checked and inform the participant not just on what needs to be achieved but also how it should be achieved. We now turn our attention to a compelling economic case put forward by Covey (2006) for improving ethical behaviour which would appeal to both the Utilitarian and Kantian perspectives.

Business behaviours to improve the organisational climate

I’d like to present a slightly different way of engaging the business community to achieve the same ends. To persuade the consequentialist business folks to adopt a form of enlightened self interest. That is to change to a self serving mode of existence designed to generate systemic trust.

In his latest book, ‘The Speed of Trust’, Stephen Covey (2006) proposes that trust (in organisations) affects two outcomes, speed and cost. When trust diminishes (often as a result of unethical behaviour), speed decreases while cost increases (Covey, 2006, p.13). Conversely if trust increases, speed increases and costs decrease (Covey, 2006, p.13).

This can be expressed as follows:



Figure 1. The economics of trust (Covey, 2006, p.13)

This relatively simple formula gives us the means to use a familiar language to influence business behaviours by quantifying ethical decision making in economic terms. For the Utilitarian perspectives this would support the business case ethos especially since the cost/benefits could easily be articulated. Kantian protagonists and relationship oriented perspectives (such as feminist ethicists) will enjoy the principle-centered implications of promoting trust as an attribute that can be actively cultivated.

Covey (2006) proposes a number of conduct changes that will dramatically improve levels of trust and judging from the level of book sales, this message seems to have caught the attention of the business community. ‘The Speed of Trust’ remained in the top 10 of the New York Times best seller list for 6 months (NY Times, 2007). I believe a campaign of winning hearts and minds will achieve much more than simply imposing these conduct changes with policies, codes on conduct or other methods of corporate coercion.

Conclusion

In conclusion, we have considered the statement made by Shaw et al. (2009) from the business community perspective paying particular attention to the ethical lenses described by Crane et al.(2007, p.119) of Egoism and Utilitarianism. Engaging the business community by projecting a set of values and obligations on them is not likely to achieve the outcome Shaw et al. (2009) desired. To address this we have suggested a more enlightened approach that appeals to the inherent self-interest in the community. An approach that achieves a more evolved mode of existence that is designed to generate trust system wide to the benefit of all.

References

Covey, S. M. R. and Merrill, R. R. (2006). The Speed of Trust. New York. Free Press.

Crane, A. and Matten, D. (2007). Business Ethics. London, Oxford University Press.

Dawkins, R. (2006). The God Delusion. London, Bantam Press.

Frankena, W. (1958). Macintyre on Defining Morality. Philosophy, Vol. 33, No. 125 (Apr., 1958), pp. 158-162, London, Cambridge University Press. Retrieved November 20, 2009 from http://www.jstor.org.ezproxy.massey.ac.nz/stable/3748565

Hosmer, L. T. (1994). Why Be Moral? A Different Rationale for Managers. Business Ethics Quarterly, Vol. 4, No. 2 (Apr., 1994), pp. 191-204. Retrieved November 20, 2009 from http://www.jstor.org/stable/3857491

Shaw, W. Barry, V. and Sansbury, G. (2009) Moral Issues In Business, Melbourne, Australia: Cengage Learning.

The New York Times, (2009), Best Sellers, Retrieved November 22, 2009 from http://www.nytimes.com/2009/04/05/books/bestseller/bestpaperbusiness.html?_r=1&scp=1&sq="speed%20of%20trust"&st=cse

5 easy steps to applying the entrepreneur's lesson to your next project:

Step 1) Analyze the core requirement that your deliverable is addressing.
This is very much about WHAT your deliverable is trying to achieve as oppose to HOW. The answer will give you greater flexibility when generating pilot options.

Step 2) Conceptualize a Pilot version of your deliverable that meets this requirement.
As a rule of thumb, aim to scale the solution down to about 25% of the original budget.

Step 3) Plan to pilot this release to a select set of target users.
Identify and engage your customers early. Prepare them for the release and how they can best help out. Make sure you establish several ways for them to communicate with your team.

Step 4) Set-up your development resources to respond quickly to feedback.
Make sure your own team is setup to capture and manage the changes in the following releases.

Step 5) Start planning a series of releases as required.
Be ambitious with your delivery dates. Constantly re-prioritize the tasks to maintain alignment with the overall requirement. Think
Triage! Follow this up with a schedule of release dates and commit to them publicly.

5 useful WolframAlpha features for Business Analysts



WolframAlpha has finally launched and this article takes a look at some of the features that may be useful to the IT crowd. If you're looking for a good explanation of what WA is then have a look at Stephen Wolfram's intro.


1) Estimation tools


Next time you ask your developers for an estimate point them to Wolfram's excellent set of metric computations...

Spotting trends can be hard however Wolfram can give you several perspectives on simple data streams. Drop a sequence of numbers in and the output will be several computational perspectives that will help you to spot patterns or even trends. Pretty useful when building estimation models. Try these statistical examples.

2) Present Value and other financial features


Essential for Cost Benefit Analysis, Wolfram provides a several view of projected value earned over time. Here's an example.

3) Website info

Drop your own URL in and see a breakdown of statistics. Still a bit basic but I think it has potential.

4) Historical Money


Great little feature that allows you to find out the value of money at different points in time. For instance you could find out how much $100 USD in 1900 is worth today.

5) Salary and wages

Wolfram allows you to input different job titles and returns the salary stats for comparison. These can even be targeted to a specific location. I've tried a few variations with out much success but I suspect this feature will be developed as the demand ramps up.

The release of a computational search engine like WolframAlpha is a very significant event and although this tool won't compete directly with Google, I believe it's on a par. Technologists and business people should definitely take note.

Design upfront or let your architecture emerge?


Our team is looking at rolling out a new technology stack (enterprise wide) called Pega Rules Process Commander (supported by Pega Systems and considered to be top of the Gartner magic quadrant for BPM Suites). This being the beginning of the journey there were a few obvious architectural questions to address. I was particularly concerned about the base class structure knowing from experience that this is the part to get right at the start.



On a mission to get some answers I went along to the annual Pega symposium in Sydney in February. The clear steer I got from the Pega team (including Alan Treffler) was to hold true to an agile philosophy and allow the architecture to emerge. Meaning to build the initial application using as much of the existing generic structure as possible in the first couple of iterations. In the retrospective, determine the gap between where you want the structure to be and where it actually is. Use this knowledge to make conservative specialization decisions for the classes. Essentially this will instill an important re-use enabler discipline within the development team.

This seemed a little counter-intuitive to me especially since the first project was intended to be the first of many rolling this technology out as a core capability for the company. Who knows what the next business problem may look like? The cost of 'getting the class structure wrong at the start seemed far too high to dismiss. Now consider the alternative...

The natural counter approach is to design as much of the class structure upfront (using techniques like detailed business domain modeling)... This smacked heavily of waterfall and seemed to be the safest route... "NO!" I thought "I absolutely won't give in to that kind of fear driven logic!"

Digging a little deeper with some of Pega's other customers and with our sister company in Australia, I started to get a feel for the actual cost of changing our minds about the class structure and it appears this topic is well addressed. However it depends entirely on the development approach your team takes. Pega actively discourages waterfall when using their suite however this doesn't proclude customers getting value out if they're constrained by traditional SDLC views. It just means that the potential for re-use and agility is more likely to remain locked up.

Pega supports alterations to the base class structure and more importantly they actively promote a 'build for change' philosophy for implementers.

In summary, my opinion is that it comes down to a combination of an organization's outlook and risk appetite. If they're a bit more contemporary and understand the dynamics of innovation (i.e. learning frameworks such as SCRUM) then allowing the architecture to emerge is a 'no brainer'. On the other hand if the organization is still struggling with a traditional theory based philosophy (waterfall for example) then 'design upfront' will certainly ease anxiety and get things going.

================= LnkedIn Q & A ==================

I posted this question on LinkedIn and here are a few answers I got back:

From: Paul Williams

Colart,

I think that there's a balance. My most successful projects were front-end designed to a point, then evolved from that. In essence, the core -- backbone, if you will -- of the frameworks were designed cathedral style. The application modules, then, were "evolved", bazzar style.

Occasionally, a requirement of the application would necessitate an adaptation of the framework (or a really useful component would be promoted into the framework), and thus the framework also evolved, but always and only within the spirit of the initial design.

In contrast, the application components were ad-hoc, whatever you please to get the client happy.

From: Olaf Dietzler

I believe that the term "architecture" is actually defining a few basic principles.

- Stability
- Scalability
- Integration and interfaces

The point of having an architect (both for IT and buildings) is to at least provide a framework in which technology can support business changes, both in function and volume without the whole thing coming apart.

An architect doesn't neccessarily need to define up front what colour the walls are going to be or what flooring is beeing put into the building, but he should have provide walls (which can be repainted in different colours) and a level base, so that when the flooring is beeing placed (or replaced) without harming the foundation.

Regards,
Olaf


From: Tony Fairhurst

I find the best approach is to define a business strategy. What are the goals of the business over the next 2,3,4,5 years. Once this had been understood, you can produce a roadmap of how to get there. That doesn't mean you won't deviate from the roadmap, but at least you will know you have and why you have.

The Key for any EA is to build in, Agility, Adaptability, Re-usability into the big picture view. If these principles are adhered to then the evolution of the architecture should be positive.

I suppose on Philosophical perspective you can think of Enterprise Architecture along the same lines as Darwinian Evolution. Put the right building blocks in place upfront, and the entity will have a good chance of survival.

So, design in terms of the core principles and building blocks should take place, however, don't over design as this may constrain you long term, remember, none of us know whats going to happen in the future, and my experience is expect the unexpected!


One of the key issues to consider is the cost of getting it wrong. The higher the cost of having to restructure the whole thing the more effort needs to go into planning up front.
Consider the key message from Agile Development: "build the simplest thing that can do the whole job, and emphasis is on whole' (maybe I don't recollect the exact wording here). Even for something that is considered very evolutionary, the basic architecture needs to be right up front, or you're going to hurt later on.
There is no conceivable reason to discard what is known and make your architecture too simple, or impossible to scale or what ever you know it will have to do.
That said, you can often create your architecture such that it is extremely scalable, but not implement the scaled out version from the start.

To change your architecture (not your implementation details) usually requires a major rewrite of everything. As long as the cost is small enough, do it, but as the project / system grows, the cost of doing this also grows...
Powered By Blogger