10 Lessons Learned (So Far) from the HP ScandalBy Eric Lundquist | Print
Desktop-as-a-Service Designed for Any Cloud ? Nutanix Frame
Opinion: The top-level management mistakes made in the recent Hewlett-Packard leak investigation provide good examples of what to do and what not to do.With only a few days to go before the top Hewlett-Packard leadersand ex-leadersappear before a congressional Committee on Energy & Commerce hearing on September 28, I thought it would be a good time to recap what I believe are the top lessons learned so far. For our full report on the Hewlett-Packard scandal involving false identities, e-mail viruses and surreptitious surveillance in the quest to uncover a leak from the board of directors, click here.
1. A question of balance. In the equation of the desire to root out the source of a leak from the company's board of directors versus a high standard of company ethics, ethics lost out. What's the lesson? Don't be blinded by a mission that might be successful in detail, but at a cost of company reputation. Forbes has a good commentary on HP's board.
2. Really think outside the box. Thinking outside the box is a hackneyed business management phrase. But in this case it would have been well worth the time of the entire board of directors to think about how their actions would appear to someone looking in on the boardroom. Even leaving the questionable practices (of which there were many) aside, was the board acting as a group to develop a successful business strategy for HP? Or was it mired in internal warfare?
4. Read the memo. If someone hands you a report on the status of a company investigation and actions regarding leaks from the board of directors, you should read the memo.
5. Pay attention. While the chairman of the board at the time may have been the driving force behind the investigation, that does not absolve anyone on the board from making it their business to know the investigation's status. Issues that are treated as "not my problem" have a way of becoming your problem.
6. Connect the dots. If there is going to be an investigation by an organization that does not have any governmental investigatory powers, you need to connect the dots. Investigations proceed in a very prescribed manner that includes finding sufficient facts, getting court approvals and knowing that crossing the line in evidence gathering can mean an entire case thrown out of court. If your organization doesn't have any of those powers, you need to ask hard questions about who will be gathering the information and what methods they will be using.
7. Public press conferences, not public apologies. At press conferences, someone usually makes a statement and then takes questions from the assembled journalists. Standing in front of a bunch of journalists and reading prepared statements has nothing to do with a press conference. If you are going to hold a press conference, prepare to peppered with tough questions. If you are not ready for that grilling, don't hold the event.
8. Look inward. Take the heat. If you let your ambitions to succeed or find a source of leaked information override your company's ethics guidelines, then you know the right course of action is to resign.
9. Reaffirm the company's guidelines through action. Be able to say to the company, "These are our guidelines and this is what I'm doing to make sure those guidelines are upheld." That action shouldn't include hiring more lawyersthere are probably enough of them already. To view HP's ethics guidelines click here.
10. Beware the music you play while on hold. Could this have been the worse choice of pre-conference music ever? While waiting for the HPAudio conference on Friday, Sept. 22, in which HPCEO Mark Hurd was going to talk about the investigation's status, those of us on audio hold were entertained by country singer Gavin DeGraw singing, "I don't want to be." Those lyrics include the following:
I don't want to be anything other than me
I'm surrounded by liars everywhere I turn
I'm surrounded by imposters everywhere I turn
I'm surrounded by identity crisis everywhere I turn
Am I the only one who noticed?
eWEEK magazine editor in chief Eric Lundquist can be reached at firstname.lastname@example.org.
Check out eWEEK.com's for the latest news, reviews and analysis on IT management from CIOInsight.com.