Tech Lead Handbook
About
  • πŸ‘‹Introduction
  • People
    • Space for Growth
    • One on Ones
    • Manage Conflicts
    • Deal with Passive Aggressive
    • Give Feedback
    • Performance Management
    • Manage Up
    • Talent Matrix
  • Engineering
    • Pair Programming
    • DCI Framework
    • Code Ownership
    • ADR
  • Leadership
    • Leadership Competencies
    • The Communication Pyramid
    • Anti Patterns
  • Prioritisation
    • Types of Decisions
    • Pros and Cons
    • Decision Matrix
  • Hiring
    • Hiring Process
    • Prepare a Hiring
    • Position Description
    • Shortlisting
    • Case Study
  • Product
    • Working with Product Managers
    • Assumptions Mapping
    • Decision Making
    • Practice vs Process
    • Nemawashi
    • OKRs
    • Consensus vs Consent
  • Project
    • The Triple Constraint
  • Strategy
    • Tech Strategy
  • Communication
    • Use Positive Language
  • Shortlist
  • ...
Powered by GitBook
On this page
  • The What
  • The How
  • Domains
  • Horizontal growth
  • Vertical growth
  • Exceptions
  • Red Flags
  • Tips
  • πŸ•³ Pitfalls
  1. People

Space for Growth

How to create space for your team to grow

The What

The biggest mindset change from an Individual Contributor role to a Leader role β€” How to grow your team.

The How

You should put growth into 2 dimensions, vertical growth is awesome, however, horizontal growth is critical for team happiness and retention.

Domains

  • Front end & BFF: web framework, user experience, browser support, JS/TS, etc

  • Backend: database, microservice, architecture, cache, search, etc

  • Data: data engineering, data wrangling, data science, data analysing, A/B testing, etc

  • DevOps: security, CI/CD, network, etc

  • Practice: dev experience, best practice, code quality, code review, delivery process, etc

  • …there are more…

Horizontal growth

  • Learn from others within / outside your domain

  • Better collaboration among domains make a smooth delivery pipeline

  • Knowledge sharing help build up a good team culture and avoid the single point of failure

  • Informal mentorship is very helpful

Vertical growth

  • Be clear about Engineering Levels: Associate, Mid-level, Senior, Staff, Senior Staff, etc

  • Delegated chat about career development

  • Always help your team grow

  • Separate the team into support & Innovation // It always falls over

  • A player leaves if there is no space to grow

  • Be inclusive. We are one team.

  • Semi durable squads & swap // trade short-term productivity to long-term growth

πŸ•³ Pitfalls

  • You as a Tech Lead is always on the critical path

  • You as a Tech Lead is always on the critical path

PreviousPeopleNextOne on Ones

Last updated 3 years ago

Exceptions

Red Flags

Tips

βœ…
πŸ”΄
πŸ“œ