Math and other good things useful for building a new engineering office
summary
A practical case of launching a new engineering branch: builds a Vilnius office, hired 4 teams in 9 months, and establishes an engineering management process that relies on data-based decision making and Google Oxygen metrics. Claims math is useful not for formulas but for a mindset borrowed from Polya’s four-step puzzle-solving method: precisely define problems, plan solutions, execute while checking steps, then review and reuse results. Applies the method to hiring, project selection, operations, and rapid scaling.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:37Why I built this story
- 1:49Context
- 2:33Story
- 2:52Short answer
- 5:43Management
- 7:15Teal
- 9:29Hierarchy
- 10:27Hierarchy vs Network
- 11:47Heroes Theory
- 12:44Machine Learning
- 13:16Why math is important
- 14:36Mindset
- 18:07Growing Organization
- 18:45Centralized vs Decentralized
- 19:25Mass mindset
- 20:15Process of puzzle solving
- 21:22Understand the problem
- 21:59Stop creating the planet
- 22:22Build the plan
- 24:23Conclusion
- 24:48Challenges
related talks
42mHow engineering managers can lead with visibility
47m‘Engineering' for Software - How to Amplify Creativity
46mHow to scale a unicorn-building engineering team (and stay sane)
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
16mEnlarge your team!
38mEngineering Engineering: More than the sum of our parts
39mProject Management for Engineers
22mWhat the Best Engineering Leaders Do Differently