What we learned at Scaling from Startup to Unicorn
summary
Ajey Gore discusses practical lessons from scaling GO-JEK’s product organization while the company grew rapidly (about 10% week-over-week). He focuses on engineering and product-org challenges encountered across a multi-product platform (transport, logistics, lifestyle, payments) and the organizational tweaks and course corrections used to address them.
AI-written summary · about
chapters (7)
- 0:00Start
- 10:46transitions in system architecture
- 11:28adding boxes without architecture to support them is pointless adding people without refactoring the org structure
- 17:11meetings, calls, emails, wikis infrastructure that people use to communicate protocols don't guarantee delivery semantics extremely hard to instrument and debug packet loss
- 18:55understand strengths & weaknesses of wetware
- 21:56anger, stress, fatigue & fear cause dropped packets and computation glitches
- 23:53if a machine does it better use a machine to do it people make mistakes doing repetitive tasks people get demotivated doing repetitive tasks
related talks
35mPanel Discussion: Product Challenges in a Fast Growing Company
28mScaling Engineering Teams: Lessons Learned from Startups to Global Enterprises
36mHypergrowth - lessons learned from tripling the size of a tech team
30mThe hidden art of scaling yourself and your app through 15million users
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups
31mScaling
33mScaling yourself during hypergrowth
34mWhen scalability becomes more than a buzzword, or how to saddle an unicorn