Commentary

Mitch Wagner
Executive Editor, Community  

What Happened To Morgan Stanley Could Happen To Any Of Us

Reading over the tawdry details of a disgruntled employee's lawsuit against Morgan Stanley, any reasonable person is going to break out in a cold sweat and get a feeling that what happened to Morgan Stanley executives could happen to any one of us if we fail to follow some commonsense rules about doing business.

Reading over the tawdry details of a disgruntled employee's lawsuit against Morgan Stanley, any reasonable person is going to break out in a cold sweat and get a feeling that what happened to Morgan Stanley executives could happen to any one of us if we fail to follow some commonsense rules about doing business.Arthur Riel, a former Morgan Stanley IT manager who set up the company's E-mail archive, filed a wrongful dismissal lawsuit. He charges:

- CTO Guy Chiarello received hard-to-get sports tickets and other favors from tech vendors that do business with the firm.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

- Morgan Stanley investment bankers pressured the firm's IT department to buy from vendors as a way to win their banking business.

- Former CFO Stephen Crawford tried to wall himself off from all E-mail communications coming from outside his inner circle. The reason, according to Riel's complaint: to make it virtually impossible for whistle-blowers to contact Crawford.

Morgan Stanley counters that the accusations are groundless.

The courts will decide on whether Riel is telling the truth, and whether Morgan Stanley violated the law or regulations. However, we can already learn some lessons from the Morgan Stanley execs' misfortunes:

Don't put anything in E-mail you don't want to have read on the pages of InformationWeek. Or the Wall Street Journal or The New York Times or the New York Post.

When we write or read E-mail, we think we're dealing with a private, confidential communications channel. But in fact, E-mail is a public medium. Laws and regulations require companies to archive their E-mail and disclose messages under subpoena. Those messages can be made public as part of a lawsuit, which is what happened here.

Don't accept gifts of more than nominal value from vendors. Don't accept any gifts from vendors you'd be embarrassed to read about in the pages of InformationWeek.

E-Mail is fundamentally broken. Workers are overwhelmed by the amount of legitimate E-mail they're receiving.

It's not just spam--even after we've deleted all the junk, some of us don't have time to even read all the legitimate E-mail we receive. We need tools to help prioritize messages. Some of us turn to technology, some of us hire assistants to cull through our messages, and some of us rely on developing good work habits to deal with the E-mail overload.

My colleague Paul McDougall has been weighing in on these subjects on the InformationWeek Weblog. He takes Morgan Stanley to task for allegations about misconduct in how it awards IT contracts. He also quotes from some of the E-mails surrounding gifts from vendors to Morgan Stanley's CTO and asks whether Morgan Stanley was out of line. What do you think?


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

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek 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. InformationWeek 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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links