One revelation was more fascinating to me than all of the gossip combined.
It's what the book calls The Algorithm. Elon's simple 5 step recipe for success. Read on to learn all about the algorithm and what it implies for the future of Twitter.
The Algorithm
The five steps of the algorithm are:
1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Then make the requirements less dumb.
2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough.
3. Simplify and optimize. This should come after step two. You should avoid doing this for parts and processes that should not exist.
4. Accelerate. Every process can be sped up. But only do this after you have followed the first three steps. Again, you should avoid doing this for parts and processes that should not exist.
5. Automate. This comes last. Wait until all requirements have been questioned, parts and processes deleted, and bugs removed.
1 comment
[ 0.25 ms ] story [ 141 ms ] threadOne revelation was more fascinating to me than all of the gossip combined.
It's what the book calls The Algorithm. Elon's simple 5 step recipe for success. Read on to learn all about the algorithm and what it implies for the future of Twitter.
The Algorithm
The five steps of the algorithm are:
1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Then make the requirements less dumb.
2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough.
3. Simplify and optimize. This should come after step two. You should avoid doing this for parts and processes that should not exist.
4. Accelerate. Every process can be sped up. But only do this after you have followed the first three steps. Again, you should avoid doing this for parts and processes that should not exist.
5. Automate. This comes last. Wait until all requirements have been questioned, parts and processes deleted, and bugs removed.
...