No Title Required: How Leadership Can Come From Anywhere
summary
Claims a junior, remote, non-manager role can co-lead an engineering effort and gives examples: a half-day test outage caused by MySQL exclusive table locks interacting with the database_cleaner gem that gets diagnosed by reading source and building a local repro; a move to Denver for three months to ramp a team; a concrete cadence called a monthly introspective with manager; and measurable goals (example OKR: 40% of stories contain front end work in Q4), plus techniques used and which ones actually yielded results.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:17No Title Required
- 2:27It's a personal journey
- 3:01It's about people, not code
- 4:03It's about the how, not just the what
- 6:29Microsoft
- 10:34Observations
- 12:29Incentives and Values
- 15:24Someone will notice my good work
- 16:29Busy work
- 18:11Don't talk, listen
- 20:17Self-assessment
- 23:08Feedback
- 25:46Dive deep, aka not
- 33:29Measure
- 34:08Mentorship
- 35:19Don't ignore physical and mental health
- 37:33Accountable organizations
- 40:15Thank you, and lead on!
related talks
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion
59mTaking Lead
11mTips on scaling your leadership outside of your comfort zone
33mAn Engineering Team Where Everyone is a Leader
23mTech leadership for everyone
50mDistributed Leadership
34mAn Engineering Team Where Everyone is a Leader
41mJesper Ottosen: Learning to Lead Testing Activities