Showing posts with label whistleblowing. Show all posts
Showing posts with label whistleblowing. Show all posts

Monday, May 20, 2019

How Not To Do It: Elizabeth Holmes and Theranos


As the engineering sage Henry Petroski likes to say, we often learn more from failures than from successes, at least when it comes to ethical behavior.  And we now have a book-length record of one of the most spectacular failures in recent business history:  Theranos, a medical-equipment company founded by Elizabeth Holmes when she dropped out of Stanford at the tender age of 20.  Although the ethical misdeeds of Holmes and her close associates are many and various enough to fill a book—investigative reporter John Carreyrou's excellent Bad Blood—I would like to focus on just one aspect of wrongdoing described therein:  the falsification of test data sent to regulators.

Holmes, who is presently undergoing a federal trial in connection with her time as CEO of Theranos, began her venture with a remarkable vision:  to make all medical blood tests as simple and easy as the diabetic's pin-prick test for blood-glucose monitoring.  She based this vision on nothing more than an internship she spent at Stanford in a research lab one summer.  But she brought to the table considerable family connections (she was able to raise over six million dollars for her new company in less than two years) and a personal magnetism that convinced older and wiser persons (men, mostly) to give her whatever she wanted.   And if it had been possible to achieve her goal with enough money and talented people in the time she had, she would have achieved it.

The history of technology teaches us that there are optimum times for certain technical advances, and the key to profiting from a new technology is to try it at the right time.  Even Steve Jobs, who Holmes idolized and emulated whenever possible, could not have invented the Macintosh in 1953—the technology simply wasn't there yet.  So in retrospect, Holmes' idea of a tiny credit-card-like machine that would do everything a whole clinical blood lab currently does with a small fraction of the blood volume now required, was simply too far ahead of its time. 

The farthest her company got technically was to build some kludgy prototypes that were basically robot versions of what a human lab technician does.  When they worked, which wasn't often, their results compared to conventional blood-testing machines were unreliable and full of errors.  The only way Theranos employees could get results approaching the accuracy of standard commercially available lab testing devices already on the market was to run six of their robot machines at once on the same sample, and average the results.  Needless to say, this was not a practical solution, but as Holmes had already gone out and negotiated contracts with big retailers such as Safeway and Walgreens, and blood samples from real people were coming in to be tested, the engineers had to do something, and this was their temporary makeshift solution.

Then the question of federal certification came up.  Labs in the U. S. that are not purely research-oriented—that is, blood testing establishments that test blood for the general public—are required to meet certain standards enforced by the U. S. government under the Clinical Laboratory Improvement Amendments (CLIA), the laws governing such labs.  At Holmes's insistence, Theranos fudged on meeting these standards as long as it could.  By the time Theranos hired a young engineer named Tyler Shultz, the firm was following a home-brew procedure to certify its lab tests that looked funny to him.

The CLIA required periodic "proficiency testing" of samples to ensure that the lab was getting accurate results.  The rule was that these samples should be tested "in the same manner" as actual patient specimens "using the laboratory's routine methods."  But at Theranos, there was nothing routine about the way they were handling tests.

In order not to look completely foolish, the company had bought a number of on-the-market blood test machines that it was using along with its own units, called (regrettably for Edison) "Edisons."  The Edisons could handle some types of tests with the dodgy averaging method, but others were sent to the outsider machines and the results passed off as being done by Theranos devices.  When Tyler tried to run the proficiency tests on the Edisons and they failed, he got in hot water with management, who ordered him to report only the good results from the non-Edison machines.  After Tyler's protests proved fruitless, he contacted an outside state regulatory body to see whether his suspicions about Theranos's way of doing things was well-founded. 

It was, and Tyler decided to go to the most powerful person he knew who was associated with Theranos:  his grandfather.  This was not just any grandfather.  It was George Shultz, former U. S. Secretary of State, now in his 90s, but very much interested in Theranos as a member of the board.

Without passing judgment on the quality of relationships in the Shultz family, I can still say that Tyler's complaints to his grandfather fell on deaf ears.  Not only that, but his grandfather told on him to Theranos management, who made it so hot for Tyler that he concluded to resign, despite threats that if he quit and went public with his information, "he would lose."

Tyler turned out to be a critical source for John Carreyrou, a Wall Street Journal investigative reporter who also caught legal flak for trying to report the truth about Theranos.  But Carreyrou persisted in contacting current and former employees of the firm who gave him enough information to write a series of blockbuster articles that turned the climate of public opinion against Theranos, and led eventually to the demise of the company (it went out of existence last fall) and the indictment of Holmes and her second-in-command for fraud.

As whistleblower stories go, Tyler Shultz got off fairly easily.  He helped bring down an organization which richly deserved its fate.  But far more commonly, whistleblowers' allegations are challenged vigorously and often successfully, even if they are true.  And whatever happens ultimately to a whistleblower's career, he or she is guaranteed to undergo considerable emotional pain as the accused organization tries to defend itself, almost like an immune response to a therapy that will ultimately do a patient good, but which causes discomfort initially.

The story of Holmes and Theranos is of a noble cause gone bad, and continues to play out in the courtroom.  But we know enough already to use the story as a bad example of how startups should not handle problems with regulators.  The lesson for young engineers is, if you smell a rat, don't just hold your nose and keep on going.  Find out if it's really a rat, and if it is, deal with it, even if you get your hands dirty to do so.

Sources:  John Carreyrou's Bad Blood:  Secrets and Lies in a Silicon Valley Startup was published in 2018 by A. A. Knopf.   

Monday, April 16, 2018

Engineers and Corporate Leaks


A recent Bloomberg News item describes how Apple is going to great lengths to keep its engineers from leaking secrets to the media.  Historically, Apple has kept the public in the dark about its plans unless and until the company wants to reveal them, usually at a trade show where CEO Tim Cook or another leader gets to present the new product or feature amid ballyhoo and drama.  Leaks spoil the surprise, and so it's understandable that the corporation wants to suppress them.  But it hasn't been able to do that completely, and a recently published memo (also leaked, presumably) gives us some insight into the thinking that goes on at one of the world's largest tech companies about secrecy and leaks.

The memo, which was posted on the company's internal blog, says that in March a leaker who told outsiders about plans for Apple's software roadmap was caught and fired.  He didn't think he'd be caught, but the memo claims that in 2017, Apple caught 29 leakers who were either Apple employees, contractors, or suppliers, and 12 were arrested.  The memo points out that while a person may not start out intending to be a leaker, media people befriending you on Facebook probably have only one thing in mind—to find out what secrets you know.  If you're caught, you will not only lose your job at Apple and possibly face arrest, but you'll find it hard to get work in the industry anywhere else. 

The overall tone of the memo reminds me of those World War II propaganda posters that showed Hitler and Mussolini with huge ears leaning next to a sauced-looking GI at a bar who is obviously spilling military secrets to a good-looking gal who's writing them down under the table on a notebook strapped to her leg.  Maybe I'm combining a couple of posters there, but the point is that large organizations with secrets to keep have to convince their workers that it's a serious moral failing to tell confidential information to outsiders. 

The negative consequence of talking to spies in wartime is pretty obvious:  the enemy is out there to kill you and your fellow soldiers, and so why would you do anything that would make the enemy's job easier?  In the case of corporate secrets, the worst negative consequences of blabbing are not so clear.  I'm not aware that anyone outside of Apple has succeeded in marketing a look-alike knockoff iPad or iPhone, because such an achievement would require more than just a few random leaks to do. 

But the real issue is control:  control of information that Apple wants to release only when it suits its plans to do so.  As the article points out, the huge public investment in Apple stock creates a powerful incentive for reporters to find out what the company is up to in advance of Apple's planned announcements, because anything that affects the firm's stock price is of interest to its investors.  Hence the steady flow of leaks about product releases, features, and the timing of new products, despite Apple's stern memos about the despicability of leaking on the part of its engineers.

If Apple is like most tech corporations, every engineer (and maybe every employee down to the janitors who clean the floors at 1 Infinite Loop, for all I know) is made to sign a hiring agreement which, among other things, binds them to keep secret information secret.  So at a minimum, if an engineer leaks information to a reporter, the engineer is violating that agreement. 

There are situations in which such an action can be justified, but they are rare.  It's called whistleblowing.  If an engineer knows of a really bad situation that threatens public safety, for example, and supervisors refuse to do anything about it, sometimes the engineer is justified in going outside the company altogether to a reporter or government official in order to remedy the situation.  But none of the leaks that Apple is ticked off about seem to fit in that category. 

Software-intensive businesses like Apple can't rely only on patents to keep themselves ahead of the competition.  That is why trade secrecy plays such an important role in highly competitive businesses like consumer technology, and why Apple gets so upset when one of its engineers leaks confidential information.  Especially in the phone market, Apple is not the only player in town, and its concerns that important innovations it has expended a lot of effort on will be stolen by Samsung or another firm are real ones.

This is another example of a general rule about professional ethics:  with specialized knowledge comes specialized responsibilities.  Engineers whose work involves secret information that would harm the company's interests if conveyed to outsiders have an obligation to keep that information confidential.  Leakers have all sorts of motivations, ranging from the temptation to yield to the flattery of a reporter, to a desire for revenge for alleged mistreatment at work.  But working for a company, as the memo points out, is a relationship of trust.  And trust violated is no longer trust.

I'm not saying that Apple's secrecy policies are always justified.  In previous blogs, I have discussed some things that Apple does that do not appear to be in the best interest of its consumers.  And depending on the circumstances, it might be serving a higher morality for an engineer to let the public know that Apple is dealing unfairly with them. 

But whatever the reason for a leak, any engineer who deliberately leaks information should be prepared for the consequences.  Even whistleblowers whose actions appear to be completely justified in retrospect usually end up getting fired and becoming a pariah, not only in the company they blow the whistle on, but often in their entire industry.  It's not fair when that happens, but it happens. 

Secrecy is a strain on those who keep secrets, and now and then secrecy is used to cover up wrongdoing.  But most of the time, tech companies have good reasons for their secrets, and any engineer who presumes to ignore those reasons and talk to outsiders is taking a career-threatening risk.

Sources:  The article "Apple warns employees to stop leaking information, talks of arrests" by Mark Gurman of the Bloomberg News service appeared on Apr. 13, 2018 on the San Jose Mercury-News website at
https://www.mercurynews.com/2018/04/13/apple-warns-employees-to-stop-leaking-information-talks-of-arrests/.