Have you ever been on a chaotic team? I have. Plenty of times. Each time — it sucked…a lot. It caused me to act on my flight response, jumping from job to job early in my career and stunted my career growth as a result.

If only I had a proper team lead at the time…

Team Leads are extremely important to any engineering organization because they enable teams to be their best. In this series, I explore what it means to be a Team Lead. I’ll share my experiences — the good and the bad. And I’ll share my own personal hopes to be the best team lead I can possibly be.

Some topics I’m thinking about include

  • Following Up

  • Responsibility

  • Empathy

  • Mentorship

  • Goal Setting

  • Technical Debt

  • Task Management

  • Core Values

  • Letting Go

  • Scheduling

  • Communication

  • Work / Life Balance

  • Prioritization

  • People Management

  • Leadership

Over the last 10+ years, having worked at startups, agencies, and corporations — I’ve experienced a variety of leadership styles. Some worked extremely well and others were terrifying. My hope is to share my theory and strategies with you — all inspired by my original hopes as a Software Engineer.

There are so many topics I want to share, the above being only a smidgen of what comes to mind. If you don’t see something that you want to learn more about, let me know in the comments below.

Hope you enjoy!