Ways of Working at Tesla Talk by Joe Justice with Q&A

(Reposted with permission)
Joe Justice shares the 4am to 7pm schedule Joe worked at Tesla, and what happens during that time!
Feb 14, 2023 #Agility #FutureOfWork #Tesla
Join Joe Justice as he discusses the unique ways of working at Tesla in this informative talk. Learn about the company's innovative approach to design, engineering, and manufacturing and get insights into what makes Tesla's work culture so special. You'll also hear about the advantages and trade-offs that come with operating at a high level of agility. This video is a must-watch for anyone interested in learning about one of the most groundbreaking companies of our time.
Organized by Rodriguez Pardo & Assocs.
#Tesla #Innovation #WorkCulture #Agility #JoeJustice #RodriguezPardo&Assocs #Technology #Sustainability #FutureOfWork #Entrepreneurship #DisruptiveTechnology

[@MongoosePreservationSociety]

Thanks for another great upload!

[@Berretotube]

You’re awesome JJ! 🎉

[@tropicice2010]

Thank you for the video!

[@gcauldwell]

Practically 100% of Joe’s material is unique - I hear nowhere else. Further, even if i’d already learned everything he’s ever produced - impossible - there are ALWAYS brand new revelations. Today’s favorite is TDD (Test Driven Development) WOW! Thank you SOOO much!

[@tropicice2010]

Hey Joe, you made my day 😎

[@TheDingsBoms]

Fascinating, thank you so much for the insight.. would be a dream to get that kind of experience

[@andreasv9472]

The Borg-vibes anyone? I'm a pm who just joined a consultant oriented it company. They didn't even have automated testing before. Moving towards automated tests, de-coupled components with the goal of incorporating some of these open forum principles and mob programming. Thanks for an insightful video!

[@ThomasButryn]

Joe, you need to write a book on Musk company ways of working! Please

[@Martinit0]

Only a Doing column, this is madness LOL

[@JoeJustice0]

This is Sparta!

[@Martinit0]

@@JoeJustice0 Well, the funny thing is, I am trying to add Kanban to a software that only has Backlog and Done, no Doing. I think no Backlog is only feasible if you have so much manpower that you can complete all tasks more or less immediately. My personal observation is that most value from a (personal) Kanban comes from distinguishing Doing and Backlog - this gives you the ability to focus on Doing but still keeping track of issues using Backlog without excessive task switching.