社区

马斯克五步工作法（顺序严格不可调换，为特斯拉、SpaceX内部强制执行准则）

\#### 1. 质疑每一项需求（Make your requirements less dumb）

\- 所有需求\*\*必须追溯至实际提报者\*\*，不接受「法务／安控／某部门」这类模糊来源；就算是马斯克本人提出的需求，团队也有权全面质疑。

\- 预设多数需求本就不合理，聪明人、权威人士提出的需求风险反而更高——众人容易盲从而不敢验证；核心是以\*\*第一性原理\*\*追根究底：这件事真的有存在的必要吗？

\#### 2. 大刀阔斧删除多余环节／零件／流程

\- 宁可误删，绝不保守；马斯克的判断标准：\*\*事后需要恢复的内容不到一成，代表删减力道不足\*\*。

\- 扭转人们「多留步骤以防万一」的本能，砍除所有非核心、可替换、旧制遗留的多余设计与流程。

\#### 3. 简化与最佳化（仅可于删减完成后执行）

\- 工程师最常犯的致命错误：\*\*去最佳化一个原本就不该存在的事物\*\*。

\- 仅保留必要项目后，再进行架构精简、参数调校、方案取舍，让留存的内容达到最精简合理的状态。

\#### 4. 提升运作速度、缩短时程

\- 流程精简、方案确认无误后，全力加快作业流转速度、压缩交付时程；先以人工跑出最快节奏，再考量机械化提速。

\#### 5. 自动化（永远放在最后一步）

\- 马斯克在特斯拉工厂曾蒙受重大损失：早年贸然全面导入自动化，耗资数百万美元的机器人最后全数拆除重做。

\- 自动化会将错误流程永久定型；唯有人工运作顺畅、流程极简、速度达标之后，自动化才具实质价值。

\### 核心底层逻辑

一般人往往跳过前两步，直接进行最佳化、提速与自动化；这套五步骤强制先行\*\*评估必要性、执行减法\*\*，才著手提升效率，八成的效益都来自前两步的质疑与删减作业。[**Musk's 5 Step Design Process**]

How do you design, build and launch a rocket into space in a radically different way from past attempts? That’s the question that faced Elon Musk’s SpaceX, and he recently revealed the process he has embedded into the organisation to make it possible.

**Musk’s 5 Step Design Process consists of making the requirements less dumb; delete the part or process; simplify and optimise the design; accelerate cycle time; and automate.**

**THE 5 STEPS.**

This model was revealed by Musk in an interview after he was asked whether the grid fins of his latest rocket design fold in (see the Origins below for the full interview with **Everyday Astronaut**).

Musk explained that they didn’t, but then expanded by outlining the 5 step process SpaceX was aiming to “apply rigorously”, and which led to the grid fin decision. See the Origins tab below for the original video interview and view the following points for each step in more detail:

- **Make the requirements less dumb.**

Musk notes that **“your requirements are definitely dumb, it does not matter who gave them to you.”** Similar to [**Framestorming**](https://modelthinkers.com/mental-model/framestorming) and its reminder to ‘question the question’, Musk uses this step to test assumptions, pointing out that requirements from a ‘smart person’ are often the most dangerous since you might not question them enough.

- **Delete the part or process.**

**“If you’re not adding things back in at least 10% of the time, you’re clearly not deleting enough.”** Musk suggests starting lean and building up when and if required, but warns that the bias will be to add things ‘in case’, **“but you can make ‘in case’ arguments for so many things.”** He goes further, arguing that each requirement or constraint must be accountable to a person, not a department, because you can ask that person about its relevance and purpose, rather than having a requirement that nobody owns and persists for years despite being redundant.

- **Simplify or optimise the design.**

**“Possibly the most common error of a smart engineer is to optimise a thing that should not exist,”** Musk explains, emphasising the importance of working through the first two steps before trying to optimise. To do this effectively, Musk argues that each engineer needs to take a holistic view of the project, pointing to previous mistakes where engineers had invested enormous resources into reducing the weight of the rocket’s engine but hadn’t adequately addressed the equivalent problem of reducing payload weight.

- **Accelerate cycle time.**

Musk embraces the drive to go faster but warns against pointing your efforts in the wrong direction, saying **“if you’re digging your grave, don’t dig faster.”** He seems to recommend an accelerated [**Agile approach**](https://modelthinkers.com/mental-model/agile-methodology), but only after the first three steps of his process are satisfied to ensure that you’re moving faster in the right direction.

- **Automate.**

Musk warns against automating before the earlier points are addressed. He relates the story of streamlining a robotic process to build battery mats in the Tesla Model 3. He describes investing massive time and effort to automate and streamline that problematic process before he finally asked what the mat was for. He discovered that it had been created to reduce sound but was no longer required.

**IN YOUR LATTICEWORK.**

Musk’s design process stems from an engineering perspective to streamline and rethink rocket design but can be applied to almost any design project from UX, a marketing campaign, or product design more broadly.

：老虎社区 - 优质内容创作

查看本周热门主题，发帖即有机会赢取奖励