4 ms·
Great excerpts. Reposting them as more hn-mobile friendly. "Btw, here are a few productivity recommendations:" – Excessive meetings are the blight of big comp
by tyingq 9y ago
Great excerpts. Reposting them as more hn-mobile friendly.
"Btw, here are a few productivity recommendations:"
– Excessive meetings are the blight of big companies and almost always get worse over
time. Please get of all large meetings, unless you’re certain they are providing value to
the whole audience, in which case keep them very short.
– Also get rid of frequent meetings, unless you are dealing with an extremely urgent
matter. Meeting frequency should drop rapidly once the urgent matter is resolved.
– Walk out of a meeting or drop off a call as soon as it is obvious you aren’t adding
value. It is not rude to leave, it is rude to make someone stay and waste their time.
– Don’t use acronyms or nonsense words for objects, software or processes at Tesla.
In general, anything that requires an explanation inhibits communication. We don’t want
people to have to memorize a glossary just to function at Tesla.
– Communication should travel via the shortest path necessary to get the job done,
not through the “chain of command”. Any manager who attempts to enforce chain of command
communication will soon find themselves working elsewhere.
– A major source of issues is poor communication between depts. The way to solve this
is allow free flow of information between all levels. If, in order to get something done
between depts, an individual contributor has to talk to their manager, who talks to a
director, who talks to a VP, who talks to another VP, who talks to a director, who talks
to a manager, who talks to someone doing the actual work, then super dumb things will
happen. It must be ok for people to talk directly and just make the right thing happen.
– In general, always pick common sense as your guide. If following a “company rule”
is obviously ridiculous in a particular situation, such that it would make for a great
Dilbert cartoon, then the rule should change.
reply
- allthenews 9y agoI worry that many of these well meaning deregulations may not scale indefinitely, both as the company grows and the working population evolves. I understand the premise, but many of the processes and red tape, while admittedly frustrating, probably did not arise out of desire for limitation. You have to put a lot of faith into your workforce to allow so much freedom in their operation.
- matte_black 9y agoAgreed, the benefit of having some bureaucratic processes is that it makes them way more tolerant of low competency individuals within the system. There’s filters at many levels that prevent someone from fucking things up too badly. If your company is running with scissors you need every individual to be a top performer who knows exactly what they are doing at all times. That is hard to guarantee when you start scaling up your headcount.
- colordrops 9y agoHeavy bureaucracy also drives away creative highly talented individuals and also creates pockets for non-productive employees to thrive, so it's questionable whether the positives outweighs the negatives. Depends on the level of fault tolerance that a corporation must achieve for their goals.
- keenerd 9y agoOn the other hand... if you wanted to quickly identify incompetent individuals, give them rope and let them cause damage.
- stevefan1999 9y agoMany would disagree, but having bureaucratic makes it easier to blame someone when things have gone wild.
- harrisi 9y agoThis is a genuine question: is Tesla not a company that has already "scaled"? I don't know their employment numbers but in terms of product that is both used and known by the general population, they seem big enough to have already have these points tested in a scaled environment.
- themodelplumber 9y agoExactly. Just in order to maintain order at scale, the organization will need to stabilize. Stabilization necessarily involves many if not most of the things he warns against, because the mindset has to shift to cover many more details and potential friction points. Otherwise you get an organization that will never stabilize, and the little details that pile up will kill it. Hopefully Musk's own non-stabilizer blind spots don't become his company's.
- dingaling 9y ago" Don’t use acronyms or nonsense words for objects, software or processes at Tesla. ” Autopilot, Supercharger, or even name of Tesla Inc. itself. Your number-one choice for AC electrical coils? And what do they say when discussing LIDAR sensors, for example? "We need to select a vendor for the laser-imaging-detection-and-ranging sensor". "Well Bob I propose the Bosch laser-imaging-detection-and-ranging sensor which runs on 28 volt direct-current". Not conducive to more efficient meetings. Acronyms and codewords serve a purpose in any context that involves repetition. If I were Mr Musk I'd be less concerned about the mental burden of acronyms and more worried about the physical strain and injury on the shop floor. But the latter can't be 'fixed' with an e-mail missive.
- cdancette 9y ago- Autopilot and supercharger are pretty easy to me (they do pretty much what they say) - they didn't invent the LIDAR, and it is the widely used name for this device so if course they must use it. This recomandation just advise not creating new acronyms inside the company. (A better example would be the BFR but that's kind of a joke) Better to choose a small name than an acronym
- falcolas 9y agoLaser is an acronym as well... > "light amplification by stimulated emission of radiation" Acronyms have their place, and can be more descriptive than, say, project Glorfindel.
- tyingq 9y agoA bit pedantic, but Telsa isn't using Lidar.
- eric24234 9y agoThanks. The entire text is also not completely visible in a resized browser, you have to horizontally scroll to read the entire text.