Skip to main content

Elon Musk sent an email to the staff at Tesla with his 6 rules for productivity. Unsurprisingly, it leaked.

 Elon Musk sent an email to the staff at Tesla with his 6 rules for productivity. Unsurprisingly, it leaked.


Here they are:
1) Avoid large meetings
Large meetings waste valuable time and energy.
- They discourage debate
- People are more guarded than open
- There’s not enough time for everyone to contribute
Don’t schedule large meetings unless you’re certain they provide value to everyone.

2) Leave a meeting if you’re not contributing
If a meeting doesn’t require your:
- Input
- Value
- Decisions
Your presence is useless.
It’s not rude to leave a meeting.
But it’s rude to waste people’s time.

3) Forget the chain of command
Communicate with colleagues directly.
Not through supervisors or managers.
Fast communicators make fast decisions.
Fast decisions = competitive advantage.

4) Be clear, not clever
Avoid nonsense words and technical jargon.
It slows down communication.
Choose words that are:
- Concise
- To the point
- Easy to understand
Don’t sound smart. Be efficient.

5) Ditch frequent meetings
There’s no better way to waste everyone’s time.
Use meetings to:
- Collaborate
- Attack issues head-on
- Solve urgent problems
But once you resolve the issue, frequent meetings are no longer necessary.
You can resolve most issues without a meeting.
Instead of meetings:
- Send a text
- Send an email
- Communicate on a discord or slack channel
Don’t interrupt your team’s workflow if it’s unnecessary.

6) Use common sense
If a company rule doesn’t:
- Make sense
- Contribute to progress
- Apply to your specific situation
Avoid following the rule with your eyes closed.
Don’t follow rules. Follow principles.

Comments

Popular posts from this blog

Technical Writer interview questions and answers

  Technical Writer interview questions and answers 1.     Can you describe your experience with technical writing and the types of documents you have created? Answer: "I have experience with various types of technical writing, including user manuals, online help, release notes, and technical specifications. I understand the importance of clear and concise technical writing in communicating complex information to users and stakeholders." 2.     Can you describe your experience with documentation tools and the ones you have worked with? Answer: "I have experience with various documentation tools such as Microsoft Word, Google Docs, Confluence, and MadCap Flare. I understand the importance of selecting the right tool for the job, depending on the document type and audience." 3.     Can you describe your experience with version control systems and the ones you have worked with? Answer: "I have experience with version control sy...

Job Title: Quality Assurance Engineer

  Job Title: Quality Assurance Engineer: Job Description: A Quality Assurance (QA) Engineer is responsible for ensuring that software products and systems meet quality standards and customer requirements. They work with software developers, project managers, and other stakeholders to create and implement test plans, test cases, and quality assurance processes. The job typically involves working in a team environment to identify and resolve software defects and to ensure that software products are delivered on time and with high quality. Responsibilities: 1.     Test Planning: Creating test plans and strategies that align with project goals and requirements, and identifying test cases and scenarios to validate software functionality and performance. 2.     Test Execution: Executing test cases and scenarios, and documenting test results, defects, and issues using testing tools such as JIRA, Selenium, or Appium. 3.     Test Aut...