- Ethics Toolkit
- Ethics Glossary
- Definition of Values
- Code of Conduct
- Code Construction and Content
- Common Ethic Code Provisions
- Writing Tips for an Effective Code of Conducts
- The PLUS Decision Making Model
- Avoid Being the Next Enron
- Business Ethics Timeline
- Ethics Publications
- Helpful Links
- MAXIMize the Moment
- Resource Articles
- ERC Fellows Research Series
PLUS: The Decision Making Process
We selected a six step decision making process that synthesized the decision making models used in existing training, not just ethics training.
The model is descriptive of how people intuitively make decisions and makes the steps explicit.
The six steps of this natural, intuitive decision-making process are:
- Step 1:
Define the problem
- Step 2:
Identify available alternative solutions to the problem
- Step 3:
Evaluate the identified alternatives
- Step 4:
Make the decision
- Step 5:
Implement the decision
- Step 6:
Evaluate the decision
The most significant step in any decision making process is describing why a decision is called for and identifying the most desired outcome(s) of the decision making process.
One way of deciding if a problem exists is to couch the problem in terms of what one wanted or expected and the actual situation. In this way a problem is defined as the difference between expected and/or desired outcomes and actual outcomes.
This careful attention to definition in terms of outcomes allows one to clearly state the problem. This is a critical consideration because how one defines a problem determines how one defines causes and where one searches for solutions.
The limiting aspect of the problem definition step is not widely appreciated. Consider this example.
Your company owns an old, downtown office building. Tenants are complaining that their employees are getting angry and frustrated because there is always a long delay getting an elevator to the lobby at rush hour.
You are asked for a reaction on how to solve this problem. As with most problem situations there are several ways to define the situation and several solutions that suggest themselves.
This scenario has been presented to over 200 groups in a training environment. The most common alternatives these groups offered were:
- Flexible hours- so all the tenants' employees wouldn't be at the elevators at the same time.
- Faster elevators - so each elevator could carry more people in a given time period.
- Bigger elevators - so each elevator could carry more people per trip.
- Elevator banks- so each elevator would only stop on certain floors, increasing efficiency.
- Better elevator controls - so each eltor would be used more efficiently.
- More elevators - so that overall carrying capacity could be increased.
- Improved elevator maintenance - so each elevator would be more efficient.
- Encourage employees to use the stairs - so fewer people would use the elevators.
If you examine each alternative you will see that several different definitions of the problem must have existed.
- If the solution is "flexible hours" the problem must have been defined as, "Too many people getting off work at a given time." No other problem makes sense for that solution.
- "Faster elevators" comes from, "The elevators are too slow."
- "Bigger elevators" comes from, "The elevators are not carrying enough people."
- "More elevators" comes from, "Too few elevators."
The real life decision makers defined the problem as "people coming about having to wait". Their solution was to make the wait less frustrating by piping music into the elevator lobbies. The complaints stopped.
There is no way that the eventual solution could have been reached if, for example, the problem had been defined as "too few elevators".
As you can see, how you define the problem determines where you go to look for alternatives/solutions, so define the problem carefully.
The key to this step is to not limit yourself to obvious alternatives or what has worked in the past but to be open to new and better alternatives. How many alternatives should you identify? Ideally, all of them. Realistically, we teach that the decision maker should consider more than five in most cases, more than three at the barest minimum. This gets away from the trap of seeing "both sides of the situation" and limiting one's alternatives to two opposing choices; either this or that.
As you evaluate each alternative, you should be looking at the likely positive and negative cones for each. It is unusual to find one alternative that would completely resolve the problem and is heads and shoulders better than all others. Differences in the "value" of respective alternatives are typically small, relative and a function of the decision maker's personal perceptions, biases and predispositions.
As you consider positive and negative cones you must be careful to differentiate between what you know for a fact and what you believe might be the case.
The decision maker will only have all the facts in trivial cases. People always supplement what facts they have with assumptions and beliefs.
This distinction between fact-based evaluation and non-fact -based evaluation is included to assist the decision maker in developing a "confidence score" for each alternative. The decision maker needs to determine not just what results each alternative could yield, but how probable it is that those results will be realized. The more the evaluation is fact-based, the more confident he/she can be that the expected outcome will occur.
When acting alone this is the natural next step after selecting the best alternative. When the decision maker is working in a team environment, this is where a proposal is made to the team, complete with a clear definition of the problem, a clear list of the alternatives that were considered and a clear rationale for the proposed solution.
While this might seem obvious, it is necessary to make the point that deciding on the best alternative is not the same as doing something. The action itself is the first real, tangible step in changing the situation. It is not enough to think about it or talk about it or even decide to do it. A decision only counts when it is implemented. As Lou Gerstner (CEO of IBM) said, "There are no more prizes for predicting rain. There are only prizes for building arks."
Every decision is intended to fix a problem. The final test of any decision is whether or not the problem was fixed. Did it go away? Did it change appreciably? Is it better now, or worse, or the same? What new problems did the solution create?
ERC now offers federal agencies GSA contracts, contact us for more information.
Get Email Updates
Subscribe to receive periodic updates. Join our email list.
Connect with ECI
ERC's Benchmarking Services
ERC's team can help you design and administer an ethics survey to fit your organization.