The Bottom Line: Where's the Money?

PDFPrintE-mail

Suppliers and consultants regularly make recommendations to their client companies. In many companies, these suppliers of products and services are trusted advisors, often having the responsibility of making a final decision on a project. Even with best intentions, however, the supplier's decision of what is right for the customer is a difficult decision because there is a potential conflict of interest. The supplier has something to gain as a result of the decision if it recommends that its services or products are included as part of the recommended course of action. The monetary value and type of transaction may determine the severity of the conflict and the course of action that should be taken to deal with it, but in each case the clear potential for a conflict of interest requires a thorough comparison of potential benefits and costs for each party.

The Bottom LineConsider, for a moment, how similar matters are treated by the law in relation to positions of trust. The law requires that a person who advises or acts on behalf of another must act in the best interest of the other person. In sales and consulting, there is certainly not an equivalent legal duty to a potential customer, but there is an ethical duty along the same lines. This conflict of interest comes into play in many scenarios. If you are a consultant billing on a long-term project and you discover that there is software that will do the same project for a much lower cost for your client and complete it much quicker, what do you tell the client? Similarly, if you are from a software company, and your software fulfills most of the client requirements, but not all of them, how do you approach the project? How do you rationalize the loss of personal income, billable hours, or an opportunity for your company with the benefits and value to your customer? There are criteria to help you evaluate whether you have a conflict of interest, and some suggestions for making your input as unbiased as possible.

The first principle for properly addressing these ethical questions is to remember that your primary duty is to your client. The discipline of obtaining a requirements definition and performing a gap analysis among all the available alternatives is necessary to determine whether or not a product or service is optimal for a client project. Benchmarks or parameters should be defined in order to provide the framework for a systematic method of determining, describing, and disclosing a conflict. Parameters should include costs and benefits to each party involved in the transaction in the forms of capital, personnel costs, time requirements, risks, and any other relevant costs and benefits

There are three major points of potential breach of ethical duty for a supplier of services or products:

1. Failure to disclose a conflict of interest.
2. Failure to accurately describe the extent of the conflict.
3. Deliberate or knowing use of bad or questionable judgment.

There is the most risk of a conflict when the benefits to supplier and the difference in the comparative cost to the client are very high. In such a case, the supplier is most likely allowing his or her own interest to interfere with the best interests of the client. In a consulting situation, often the service provider is compensated with bonuses and commissions that are heavily weighted on billable hours and utilization, so a software product that effectively reduces the compensation to the consultant is spurned. In the case of a software supplier, the tendency is to claim functionality that is not a standard part of the packaged software just to make the sale or to ignore gaps that the software does not address. In those cases, the costs to the client escalate in relation to the work needed to fill the gaps not covered by the software that were not disclosed by the software supplier in promoting the sale. It is easy to see how each party could be financially motivated to sell its own product or service, even when careful assessment clearly indicates that such a product or service is not the optimal solution for the client.

Add comment


Security code
Refresh

Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Enter your email address to sign up for our Newsletter

Sign up now

captcha
TEChanges - Agility by Design

January Puzzle

A traveler gets lost on a deserted island and finds himself surrounded by a group of n cannibals.

Each cannibal wants to eat the traveler but, as each knows, there is a risk. A cannibal that attacks and eats the traveler would become tired and defenseless. After he eats, he would become an easy target for another cannibal (who would also become tired and defenseless after eating).

The cannibals are all hungry, but they cannot trust each other to cooperate. The cannibals happen to be well versed in game theory, so they will think before making a move.

Does the nearest cannibal, or any cannibal in the group, devour the lost traveler?

Show solution...

Solution

The short answer is the traveler’s fate depends on the parity of the group. If there is an odd number of canibals, the traveler will be eaten, but if there is an even number, the traveler will survive.

To prove this, we will consider small groups and use mathematical induction to explain the solution for larger groups.

Case n = 1: this is an obvious case. If there is one cannibal, the traveler will be eaten. It doesn’t matter that the cannibal will get tired because there are no other cannibals around as a threat.

Case n = 2: this is a more interesting case. Each cannibal wishes to each the traveler, but each knows he cannot. If either cannibal eats the traveler, then he will become defenseless and the other one will eat him. So each cannibal uses backwards induction to realize that the only strategy is to not eat the traveler. The hapless traveler finds a bit of luck, therefore, and actually survives.

Case n = 3: this is where the problem gets interesting. The best strategy is for the closest cannibal to make a move and eat the traveler. The cannibal will be defenseless after eating, but ultimately he will be safe. Why is that? The reasoning is due to induction: once the cannibal eats the traveler, the resulting situation has 2 unfed cannibals and the 1 defenseless cannibal. But as we just showed above, when there are 2 unfed cannibals, neither will make a move for fear of being eaten by the other! Thus the first cannibal to make a move will be safe as the remaining 2 cannibals block each other.

We can prove the higher cases using mathematical induction. If the number n is odd, then the closest cannibal can safely eat the traveler because the remaining number of unfed cannibals is even (and by induction, with an even number of unfed cannibals no one makes a move). If the number n is even, then no cannibal will eat the traveler, for if he did, the remaining number of cannibals would be odd, meaning he will get eaten by the induction hypothesis.

Success Tips for Oracle Project Management

  • Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
  • Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
  • If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
  • Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
  • Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
  • Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
  • Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
  • Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
  • Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
  • Include governance, risk, and compliance management as part of the project plan.
  • Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.

The Analyst Corner

John Van Decker, Research VP of Gartner, states:

"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."