Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Jonathan Feldman

Jonathan Feldman

Contributing Editor

Dishonesty Flourishes Because We Enable It

When IT holds the keys to our business-critical systems, employee dishonesty can have serious repercussions. Duke professor Dan Ariely says we're wrong about how to keep employees honest.

If your responsibilities include managing budgets, people, or inventory, one of your worst moments is getting that phone call informing you about some type of dishonest behavior. For those of us in large IT shops, the dishonesty runs the gamut--from analysts who use their system access to compare salaries to an employee who got busted for changing records in a property appraisal system to benefit his buddies. As an FBI agent I once worked with used to quip: "The big-money bank robbers don't use a gun; they use a keyboard."

IT employees hold the keys to the treasure rooms, so their honesty or dishonesty is obviously of great interest to us and our organizations. From a societal perspective, one could even argue that in the era of voting machines and complex stock market transactions, IT is the one ring that rules them all.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

It's not just about keeping IT personnel from looting our riches or rigging our elections, of course. Rampant, dishonest behavior can lead to a corporate brain drain, as an organization's best and brightest, sick of being part of the Enron Nation, say "to hell with it, I'm not playing anymore."

For all of these reasons, most of us try to support an atmosphere of honesty. We check references, reject resumes with obvious falsehoods, and implement processes that support honest behavior. Turns out, we're probably doing it wrong.

[ Will Microsoft's management practices--more than its competitors or products--be the cause of its decline? See Microsoft A Victim Of Its Own Success. ]

I just finished Duke professor Dan Ariely's latest book, The (Honest) Truth About Dishonesty," and was wide-eyed at a couple of passages. For example, when people deal with tokens of value instead of actual value (such as poker chips instead of dollars), they cheat more. Ariely discusses the rampant overstating of billable hours in most professional services organizations. A personal example involves the "near money" of frequent flier miles and other loyalty programs, all of which are tracked by the systems IT supports.

For years I've assumed that putting folks into teams would cut down on cheating. But Ariely's experiment-based research identifies something called "altruistic cheating," the cheating someone does because he's working on a team and wants others on the team to get a bonus or promotion or avoid punishment.

Ariely urges readers to leave behind the outmoded "simple model of rational crime" (SMORC), which assumes that when there's a favorable risk-benefit ratio to dishonest acts, such acts will be committed, and when there isn't a favorable risk-benefit, they won't be committed. Ariely buries that theory through the experiments he details in the book.

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our online community and information resource for CIOs operating in the global economy.
Organizations must also understand the forces that increase dishonesty. Those include basics such as hunger and fatigue from working on projects late at night without a company-supplied dinner.

Dishonesty is contagious. If it's well known in your organization that individuals are stealing a competitor's secrets, or if you're at one of those professional services organizations that regularly overstates billable hours, don't expect that the rest of employee behavior will be a model of honesty. The Talmud compares keeping bad company with hanging around in a tannery--the stink will stay with you. (But quoting the Talmud or your mom or scoutmaster at a meeting probably won't be as effective as pointing to serious behavioral science, and for that we can thank Ariely.)

When small dishonest acts accumulate, individuals start feeling what Ariely calls the "what the hell" factor. That is, once you've committed a bunch of dishonest acts, you sort of go with it, and they get bigger.

I had an email conversation with Ariely regarding Scott Thompson, the former Yahoo CEO who claimed (falsely) that he had a degree from Stanford. I wondered what would happen if I didn't correct the folks who refer to me in email as "Dr. Feldman." Might I one day be listed as such on a conference brochure and then not correct the organizers because I didn't want to cause them grief? Might someone then ask me where I had gotten my PhD? Would I make something up and watch it snowball after a colleague overheard the conversation?

If someone told me that I would act this dishonestly, I would argue against that notion vigorously, but wouldn't we all? Trouble is, I could see it happening to someone else, which--to be (honestly) honest--probably means it could happen to me.

Ariely agrees that "small slips that get larger over time are the main problem," and that this may well have been the case with Thompson. My point: It could happen to any of us if we don't watch the small stuff.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.