But I'm sure it serves a purpose in giving his employees an aggressive target to aim at. Even if they miss it, at least they probably got there sooner.
But I'm sure it serves a purpose in giving his employees an aggressive target to aim at. Even if they miss it, at least they probably got there sooner.
I'm looking for his most ambitious and oldest targets and so far, most of them have been reached/exceeded. The most important one being the 500,000 production vehicles run rate for 2020 and 35 GWh battery production for Gigafactory Nevaga. Multiplying that duration by 2 or 3 would bring us to 2027 or 2034... If you can find an even bigger and older target, please share so we can re-evaluate.
[0] https://qz.com/1268647/elon-musk-says-a-fluff-bot-showed-him...
That only works until the employees quickly realize the estimates are impossible bullshit, and stop taking them seriously.
That's the kind of management that would go whip the sea for disobedience.
https://en.wikipedia.org/wiki/Xerxes_I#Invasion_of_the_Greek...
> According to the Greek historian Herodotus, Xerxes's first attempt to bridge the Hellespont ended in failure when a storm destroyed the flax and papyrus cables of the bridges. In retaliation, Xerxes ordered the Hellespont (the strait itself) whipped three hundred times, and had fetters thrown into the water.
I hope they have real plans for the real work, while the CEO throws out PR bombs.
Seems to have worked
Though, I guess in this case it's to put some pressure on Texan government burocracy to hurry up with permits etc.
Over here at Giga Berlin, the local government issued temporary permits extremely quickly (for German standards) but it takes still longer to get all the paperwork done than it took to actually built Giga Shanghai.
That would require an executive board entirely detached from both reality and what their own experts have to say regarding the feasibility of those plans.
I think he tries to just publicise the unpadded, best-case-scenario estimates rather than the best-guess estimates to push people to eliminate any slack in the project.
If we can realize the goal is ridiculous, surely the engineers who work on this full time will realize it's ridiculous.
The flip side to doing things that don’t scale is that once those practices become a standard part of your operations you are forced to figure out how to scale them. This causes you to find the scalability hell or high water whereas if you didn’t do the thing in the first place you never would have invented the scalability.
What about all the promises that have been made that never came to fruition? Do we just exclude those from this formula?