Skip to main content

Human Resource Risk Management - Strategic and Operational Failure of TESLA

To: Everybody
Subject: Some concerning news
June 17, 2018
11:57 p.m.
I was dismayed to learn this weekend about a Tesla employee who had conducted quite extensive and damaging sabotage to our operations. This included making direct code changes to the Tesla Manufacturing Operating System under false usernames and exporting large amounts of highly sensitive Tesla data to unknown third parties.
The full extent of his actions are not yet clear, but what he has admitted to so far is pretty bad. His stated motivation is that he wanted a promotion that he did not receive. In light of these actions, not promoting him was definitely the right move.
However, there may be considerably more to this situation than meets the eye, so the investigation will continue in depth this week. We need to figure out if he was acting alone or with others at Tesla and if he was working with any outside organizations.
As you know, there are a long list of organizations that want Tesla to die. These include Wall Street short-sellers, who have already lost billions of dollars and stand to lose a lot more. Then there are the oil & gas companies, the wealthiest industry in the world — they don't love the idea of Tesla advancing the progress of solar power & electric cars. Don't want to blow your mind, but rumor has it that those companies are sometimes not super nice. Then there are the multitude of big gas/diesel car company competitors. If they're willing to cheat so much about emissions, maybe they're willing to cheat in other ways?
Most of the time, when there is theft of goods, leaking of confidential information, dereliction of duty or outright sabotage, the reason really is something simple like wanting to get back at someone within the company or at the company as a whole. Occasionally, it is much more serious.
Please be extremely vigilant, particularly over the next few weeks as we ramp up the production rate to 5k/week. This is when outside forces have the strongest motivation to stop us.
If you know of, see or suspect anything suspicious, please send a note to [email address removed for privacy] with as much info as possible. This can be done in your name, which will be kept confidential, or completely anonymously.
Looking forward to having a great week with you as we charge up the super exciting ramp to 5000 Model 3 cars per week!
Will follow this up with emails every few days describing the progress and challenges of the Model 3 ramp.
Thanks for working so hard to make Tesla successful,
Elon

#human #resource #risk #ERM #TESLA #Breach #riskmanagement #HR #sabotage

Comments

Popular posts from this blog

How to benefit from a Fishbone or Ishikawa Diagram for Root Cause Analysis

What is root cause analysis?Root cause analysis is a structured process that helps healthcare, manufacturing and service sector managers and leaders in identifying contributing factors or causes of an accident, error, problem, event or occurrence. An accident, error, problem, event or occurrence are usually a result of a system rather than an individual mistakes. Understanding the system itself and contributing factors or causes of a system failure can help in preventing recurrences. Actions that are taken to address system failure helps in sustaining the improvements or corrective actions. What is a fishbone or ishikawa diagram? Each and every outcome or effect is an end result of actions taken/omitted or in general causes/ A cause and effect diagram representing this relationship between cause and effect is called a called a fishbone or ishikawa diagram. A fishbone diagram is a visual way to represent cause and effect. It is a more structured approach for brainstorming causes of a pro…

Operational Risk Management and Compliance Management in Emergency Department

Client Question Hi,
We recently underwent an Accreditation Canada visit and were cited for not using 2 patient identifiers. The nurse picked up the patient in the ED and she was familiar with the patient and neglected to check her name and DOB. Patient identifiers is something that we have been struggling with for the past two accreditations. We thought we had it all well in hand but it only takes one incident to get cited on failing the ROP. Does anyone have a process or audit tools that are used routinely to audit staff using 2 patient identifiers? Any help would be greatly appreciated. Thank you 
Response
In order to comply with the required organizational practices (ROPs), we first need to have a closer look at it. ROPs in this case are the standards that the organization is being held against and must meet. So lets understand what does the ROP actually require. Following is a statement from one of the ROPs that relate to the question at hand. On an average Accreditation Canada ha…

Essential elements of ERM

Essential elements of ERM

Create your own and tailored #ERM #framework with ease! We have worked hard to incorporate changes from #COSO and #ISO #31000 so that you can benefit without having to invest a lot of time and resources. 




Email us at info@ermgovernance.com for more details.