Intersection of Leadership and Technology
summary
Panelists name Anton Kazakov Grzegorz Sztandera James Bowkett Muhammad Ahsan Ayaz Max Körbächer Tomasz Manugiewicz and they argue that leadership decisions must be concrete: reserve team capacity for proof-of-concept microservice trials, record architectural choices with architecture decision records, run a tech radar, and treat hiring as curiosity learning relationships. Practical notes: test Kafka before replacing RabbitMQ, use CoPilot and other AI tools experimentally, track cycle time lead time availability incidents and user growth, and connect those metrics to revenue so teams know if they’re profitable.
AI-written summary · about
chapters (8)
- 0:00Leadership and tech panel
- 8:00High performance teams
- 12:36Emerging tech impact
- 19:43Innovation vs team performance
- 24:45Engineering culture strategies
- 30:05Engineering talent retention
- 36:35Team profitability metrics
- 42:58Closing remarks
related talks
20mStrategies for engineering leaders to stay current and effective
42mPanel Discussion: Increasing Team's Performance Through Leadership
40mLayers of Leadership
01h 16mCTO Panel
38mPanel discussion - Selecting the right technology for the right challenge
42mPanel: Becoming an engineering leader
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion
16mThe secret to technical leadership