🎯 Mα»₯c TiΓͺu BΓ i ViαΊΏt

Delegation lΓ  kα»Ή nΔƒng quan trọng nhαΊ₯t khi chuyển tα»« Senior β†’ Tech Lead. Thay vΓ¬ tα»± lΓ m tαΊ₯t cαΊ£, Tech Lead phαΊ£i phΓ’n cΓ΄ng Δ‘ΓΊng người, Δ‘ΓΊng việc để team deliver nhanh hΖ‘n. BΓ i nΓ y Δ‘i sΓ’u vΓ o Delegation Model, workflow thα»±c tαΊΏ, anti-patterns, vΓ  3 model nΓ’ng cao mΓ  Tech Lead dΓΉng mα»—i ngΓ y.

Senior Engineer = Problem Solver. Tech Lead = Team Multiplier.

Series Navigation

BΓ i 1 β†’ How to Become a Tech Lead (Career Path & Mindset)
BΓ i 2 β†’ Engineering Manager (Technical Skill & Leadership)
BΓ i 3 β†’ Tech Lead Time Management
BΓ i 4 β†’ (bΓ i nΓ y) Tech Lead Delegation Model

🧩 1. Delegation Model Tα»•ng Quan

Tech Lead LΓ  Trung TΓ’m PhΓ’n Phα»‘i CΓ΄ng Việc

                    TASKS / WORKLOAD
                           β”‚
                           β–Ό
                    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                    β”‚   Tech Lead   β”‚
                    β”‚   Evaluate    β”‚
                    β”‚   Prioritize  β”‚
                    β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜
                            β”‚
                            β–Ό
               β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
               β”‚  Decide who should do itβ”‚
               β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                           β”‚
          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
          β–Ό                β–Ό                 β–Ό
     Junior Dev        Mid-level Dev      Senior Dev
   (learning tasks)    (feature tasks)   (complex tasks)

Key insight: Tech Lead khΓ΄ng phαΊ£i người code nhiều nhαΊ₯t β€” mΓ  lΓ  người phΓ’n bα»• cΓ΄ng việc thΓ΄ng minh nhαΊ₯t.


πŸ”„ 2. Delegation Workflow

Quy Trình 6 Bước

              Task Appears
                   β”‚
                   β–Ό
          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
          β”‚ 1. Tech Lead    β”‚
          β”‚    evaluates    β”‚
          β”‚    (complexity, β”‚
          β”‚     urgency,    β”‚
          β”‚     risk)       β”‚
          β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                   β”‚
                   β–Ό
          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
          β”‚ 2. Break into   β”‚
          β”‚    sub-tasks    β”‚
          β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                   β”‚
                   β–Ό
          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
          β”‚ 3. Match task   β”‚
          β”‚    β†’ developer  β”‚
          β”‚    (skill fit)  β”‚
          β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                   β”‚
                   β–Ό
          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
          β”‚ 4. Provide      β”‚
          β”‚    context &    β”‚
          β”‚    expectations β”‚
          β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                   β”‚
                   β–Ό
          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
          β”‚ 5. Monitor      β”‚
          β”‚    progress     β”‚
          β”‚    (not micro-  β”‚
          β”‚     manage)     β”‚
          β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                   β”‚
                   β–Ό
          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
          β”‚ 6. Review       β”‚
          β”‚    result &     β”‚
          β”‚    feedback     β”‚
          β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Mα»—i BΖ°α»›c Cα»₯ Thể

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚          Delegation Workflow Details          β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                                              β”‚
β”‚  Step 1: Evaluate                            β”‚
β”‚  β”œβ”€ Task nΓ y critical hay routine?           β”‚
β”‚  β”œβ”€ Độ phα»©c tαΊ‘p: Low / Medium / High?       β”‚
β”‚  └─ Deadline: Urgent hay cΓ³ buffer?          β”‚
β”‚                                              β”‚
β”‚  Step 2: Break down                          β”‚
β”‚  β”œβ”€ 1 feature lα»›n β†’ nhiều task nhỏ          β”‚
β”‚  β”œβ”€ Mα»—i task cΓ³ scope rΓ΅ rΓ ng               β”‚
β”‚  └─ Define done criteria cho tα»«ng task       β”‚
β”‚                                              β”‚
β”‚  Step 3: Match developer                     β”‚
β”‚  β”œβ”€ Skill level phΓΉ hợp?                    β”‚
β”‚  β”œβ”€ Task nΓ y giΓΊp họ grow khΓ΄ng?             β”‚
β”‚  └─ Workload hiện tαΊ‘i thαΊΏ nΓ o?              β”‚
β”‚                                              β”‚
β”‚  Step 4: Provide context                     β”‚
β”‚  β”œβ”€ WHY chΓΊng ta lΓ m task nΓ y               β”‚
β”‚  β”œβ”€ Expected output / acceptance criteria    β”‚
β”‚  └─ Resources & references                   β”‚
β”‚                                              β”‚
β”‚  Step 5: Monitor                             β”‚
β”‚  β”œβ”€ Check-in ở milestones                    β”‚
β”‚  β”œβ”€ SαΊ΅n sΓ ng unblock khi cαΊ§n               β”‚
β”‚  └─ KHΓ”NG hover mα»—i 30 phΓΊt                β”‚
β”‚                                              β”‚
β”‚  Step 6: Review & Feedback                   β”‚
β”‚  β”œβ”€ PR review chαΊ₯t lượng                     β”‚
β”‚  β”œβ”€ Constructive feedback                    β”‚
β”‚  └─ Celebrate wins                           β”‚
β”‚                                              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ‘₯ 3. Delegation Strategy β€” Match Task Vα»›i Skill Level

Ma TrαΊ­n PhΓ’n CΓ΄ng

                TASK DIFFICULTY

       Easy           Medium           Hard
        β”‚               β”‚               β”‚
        β–Ό               β–Ό               β–Ό
    Junior Dev       Mid Dev        Senior Dev
   (learning task)  (feature work)  (complex logic)

                         β”‚
                         β–Ό
                    Tech Lead
              handles architecture
              + critical decisions

Chi TiαΊΏt Theo Level

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  Developer     β”‚  Được giao loαΊ‘i task gΓ¬?           β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                β”‚                                    β”‚
β”‚  Junior Dev    β”‚  β”œβ”€ CRUD features                  β”‚
β”‚  (0-2 nΔƒm)    β”‚  β”œβ”€ UI components                  β”‚
β”‚                β”‚  β”œβ”€ Bug fixes Δ‘Ζ‘n giαΊ£n             β”‚
β”‚                β”‚  β”œβ”€ Unit tests                     β”‚
β”‚                β”‚  └─ Documentation                  β”‚
│                │  → Kèm hướng dẫn chi tiết         │
β”‚                β”‚                                    β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                β”‚                                    β”‚
β”‚  Mid Dev       β”‚  β”œβ”€ Feature development            β”‚
β”‚  (2-4 nΔƒm)    β”‚  β”œβ”€ API integration                β”‚
β”‚                β”‚  β”œβ”€ Performance optimization        β”‚
β”‚                β”‚  β”œβ”€ Code refactoring               β”‚
β”‚                β”‚  └─ Technical investigation         β”‚
β”‚                β”‚  β†’ Giao context, để tα»± implement   β”‚
β”‚                β”‚                                    β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                β”‚                                    β”‚
β”‚  Senior Dev    β”‚  β”œβ”€ Complex business logic         β”‚
β”‚  (4+ nΔƒm)     β”‚  β”œβ”€ System design cho module       β”‚
β”‚                β”‚  β”œβ”€ Security review                β”‚
β”‚                β”‚  β”œβ”€ Cross-team integration          β”‚
β”‚                β”‚  └─ Mentor junior/mid              β”‚
β”‚                β”‚  β†’ Giao outcome, để tα»± quyαΊΏt cΓ‘ch β”‚
β”‚                β”‚                                    β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                β”‚                                    β”‚
β”‚  Tech Lead     β”‚  β”œβ”€ Architecture design            β”‚
β”‚                β”‚  β”œβ”€ Critical path decisions         β”‚
β”‚                β”‚  β”œβ”€ PoC / Technical spikes          β”‚
β”‚                β”‚  β”œβ”€ Cross-system integration        β”‚
β”‚                β”‚  └─ Production crisis               β”‚
β”‚                β”‚                                    β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

🧠 4. Smart Delegation Logic

Decision Tree

                  NEW TASK
                     β”‚
                     β–Ό
          Is it critical architecture?
                     β”‚
            β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”
            β–Ό                 β–Ό
           YES               NO
            β”‚                 β”‚
            β–Ό                 β–Ό
     Tech Lead         Can a Senior Dev
     handles it        handle it?
                              β”‚
                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β–Ό                 β–Ό
                    YES               NO
                     β”‚                 β”‚
                     β–Ό                 β–Ό
              Assign to          Can a Mid Dev
              Senior Dev         handle it?
                                       β”‚
                                β”Œβ”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”
                                β–Ό              β–Ό
                               YES            NO
                                β”‚              β”‚
                                β–Ό              β–Ό
                          Assign to      Break down
                          Mid Dev        into smaller
                                         tasks
                                           β”‚
                                           β–Ό
                                    Assign sub-tasks
                                    to Junior + Mid

Quick Decision Framework

Hỏi 3 cΓ’u trΖ°α»›c khi tα»± lΓ m:

  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚                                      β”‚
  │  1. "Phải chính mình làm không?"     │
  β”‚     β†’ Chỉ YES nαΊΏu architecture/     β”‚
  β”‚       critical                       β”‚
  β”‚                                      β”‚
  β”‚  2. "Ai phΓΉ hợp nhαΊ₯t?"              β”‚
  β”‚     β†’ Match skill + growth           β”‚
  β”‚       opportunity                    β”‚
  β”‚                                      β”‚
  │  3. "Cần support gì?"               │
  β”‚     β†’ Context, pair session,         β”‚
  β”‚       hay chỉ cαΊ§n review cuα»‘i?      β”‚
  β”‚                                      β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ“Š 5. Before vs After Delegation

❌ Senior Engineer Mindset

Task A ──► I do it
Task B ──► I do it
Task C ──► I do it
Task D ──► I do it

  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚         Results             β”‚
  β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
  β”‚  Developer: overloaded πŸ”₯   β”‚
  β”‚  Team growth: slow 🐌       β”‚
  β”‚  Delivery: slow ⏰          β”‚
  β”‚  Bus factor: 1 ☠️           β”‚
  β”‚  Burnout risk: HIGH πŸ’€      β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

βœ… Tech Lead Mindset

Task A ──► Dev 1 (Junior β€” learning opportunity)
Task B ──► Dev 2 (Mid β€” feature ownership)
Task C ──► Dev 3 (Senior β€” complex logic)
Task D ──► Tech Lead (architecture decision)

  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚         Results             β”‚
  β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
  β”‚  Team productivity: ↑↑ πŸš€   β”‚
  β”‚  Team growth: ↑↑ πŸ“ˆ         β”‚
  β”‚  Delivery speed: ↑↑ ⚑      β”‚
  β”‚  Bus factor: 4+ βœ…          β”‚
  β”‚  Burnout risk: LOW 😊       β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ§‘β€πŸ’» 6. VΓ­ Dα»₯ Thα»±c TαΊΏ β€” Payment System Feature

Tech Lead PhΓ’n CΓ΄ng ThαΊΏ NΓ o

Feature: Payment System
         β”‚
         β–Ό
    Tech Lead evaluates
         β”‚
         β–Ό
    Break into 4 tasks
         β”‚
         β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                                             β”‚
β”‚  Architecture Design ──► Tech Lead          β”‚
β”‚  β”œβ”€ Payment flow design                     β”‚
β”‚  β”œβ”€ Error handling strategy                 β”‚
β”‚  β”œβ”€ Integration pattern selection           β”‚
β”‚  └─ Security architecture                   β”‚
β”‚                                             β”‚
β”‚  API Integration ──► Mid Dev                β”‚
β”‚  β”œβ”€ Payment gateway API                     β”‚
β”‚  β”œβ”€ Request/response mapping                β”‚
β”‚  β”œβ”€ Retry logic                             β”‚
β”‚  └─ Error handling implementation           β”‚
β”‚                                             β”‚
β”‚  UI Implementation ──► Junior Dev           β”‚
β”‚  β”œβ”€ Payment form components                 β”‚
β”‚  β”œβ”€ Form validation                         β”‚
β”‚  β”œβ”€ Loading states                          β”‚
β”‚  └─ Success/error screens                   β”‚
β”‚                                             β”‚
β”‚  Security Review ──► Senior Dev             β”‚
β”‚  β”œβ”€ Input sanitization                      β”‚
β”‚  β”œβ”€ PCI compliance check                    β”‚
β”‚  β”œβ”€ Penetration test scenarios              β”‚
β”‚  └─ Code security audit                     β”‚
β”‚                                             β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Timeline & Dependencies

Week 1:
  Tech Lead: Architecture design β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ
  Junior:    UI components (mock data) β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ
  Mid:       Study payment API docs β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ

Week 2:
  Tech Lead: Review + unblock β–ˆβ–ˆβ–ˆβ–ˆ
  Junior:    UI integration β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ
  Mid:       API integration β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ
  Senior:    Security review starts β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ

Week 3:
  Tech Lead: Final review + deploy β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ
  Junior:    Bug fixes + polish β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ
  Mid:       Testing + edge cases β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ
  Senior:    Security audit complete β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ

⚠️ 7. Delegation Anti-Patterns

❌ Anti-Pattern 1: Micromanagement

Tech Lead assigns task
        β”‚
        β–Ό
Constantly checking every detail
  "Xong chΖ°a? LΓ m tα»›i Δ‘Γ’u rα»“i?"
  "Sao khΓ΄ng dΓΉng cΓ‘ch nΓ y?"
  "Để anh review tα»«ng dΓ²ng code..."
        β”‚
        β–Ό
Developer mαΊ₯t autonomy
        β”‚
        β–Ό
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  HαΊ­u quαΊ£:               β”‚
  β”‚  β”œβ”€ Dev khΓ΄ng tα»± tin     β”‚
  β”‚  β”œβ”€ Dev khΓ΄ng grow       β”‚
  β”‚  β”œβ”€ Tech Lead burnout    β”‚
  β”‚  └─ Team morale giαΊ£m    β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

❌ Anti-Pattern 2: Dump & Disappear

Tech Lead overloaded
        β”‚
        β–Ό
Randomly assigns tasks
  "Em lΓ m cΓ‘i nΓ y nhΓ©"
  (khΓ΄ng context, khΓ΄ng guidance)
        β”‚
        β–Ό
Wrong person for the job
        β”‚
        β–Ό
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  HαΊ­u quαΊ£:               β”‚
  β”‚  β”œβ”€ Task bα»‹ stuck       β”‚
  β”‚  β”œβ”€ Quality thαΊ₯p        β”‚
  β”‚  β”œβ”€ Dev frustrated      β”‚
  β”‚  └─ Rework nhiều        β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

❌ Anti-Pattern 3: Γ”m HαΊΏt Mọi Thα»©

Tech Lead khΓ΄ng delegate:

  Review TαΊ€T CαΊ’ PR        β†’ burnout
  Attend TαΊ€T CαΊ’ meeting   β†’ no deep work
  Fix TαΊ€T CαΊ’ bugs         β†’ team khΓ΄ng learn
  Make TαΊ€T CαΊ’ decisions   β†’ team khΓ΄ng grow
  Code TαΊ€T CαΊ’ features    β†’ bottleneck

       β”‚
       β–Ό
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  Tech Lead = BOTTLENECK  β”‚
  β”‚                          β”‚
  β”‚  Team chờ Tech Lead      β”‚
  β”‚  để lΓ m MỌI THỨ         β”‚
  β”‚                          β”‚
  β”‚  Single point of failure β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

βœ… Healthy Delegation

     Right Task
          β”‚
          β–Ό
     Right Person
          β”‚
          β–Ό
     Clear Context
     (WHY + WHAT + HOW much freedom)
          β”‚
          β–Ό
     Trust + Support
     (Check milestones, not every line)
          β”‚
          β–Ό
     Review + Feedback
     (Celebrate wins, coach improvements)

🧠 8. Delegation Mindset Shift

Sα»± Thay Đổi TΖ° Duy

Senior Engineer                  Tech Lead

"I will solve                    "Who is the best
 the problem."                    person to solve this?"

"Let me code this."              "Let me break this down
                                  and assign effectively."

"I need to know                  "I need to enable
 everything."                     everyone."

"Quality = my code"              "Quality = team's code
                                  through good review"

Delegation Formula

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                                          β”‚
β”‚     Effective Delegation =               β”‚
β”‚                                          β”‚
β”‚         Task Ownership                   β”‚
β”‚              +                           β”‚
β”‚         Clear Expectations               β”‚
β”‚              +                           β”‚
β”‚         Trust                            β”‚
β”‚              +                           β”‚
β”‚         Review & Feedback                β”‚
β”‚                                          β”‚
β”‚  ThiαΊΏu 1 yαΊΏu tα»‘ β†’ delegation thαΊ₯t bαΊ‘i  β”‚
β”‚                                          β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

ThiαΊΏu Ownership     β†’ Dev khΓ΄ng commit
ThiαΊΏu Expectations  β†’ Output sai hΖ°α»›ng
ThiαΊΏu Trust         β†’ Micromanagement
ThiαΊΏu Review        β†’ Quality giαΊ£m

πŸš€ 9. Ba TΓ¬nh Huα»‘ng Thα»±c TαΊΏ MΓ  Tech Lead GαΊ·p Mα»—i NgΓ y

TΓ¬nh huα»‘ng 1: Junior Dev Hỏi LiΓͺn Tα»₯c

VαΊ₯n đề:

  Junior: "Anh Ζ‘i, em khΓ΄ng biαΊΏt lΓ m thαΊΏ nΓ o..."
  (LαΊ·p lαΊ‘i 5-10 lαΊ§n/ngΓ y)
       β”‚
       β–Ό
  Tech Lead bα»‹ interrupt liΓͺn tα»₯c
       β”‚
       β–Ό
  KhΓ΄ng code được gΓ¬
GiαΊ£i phΓ‘p β€” Tech Lead Unblocking Model:

  Junior bα»‹ stuck
       β”‚
       β–Ό
  Tα»± research 30 phΓΊt
  (Google, docs, codebase)
       β”‚
       β–Ό
  VαΊ«n stuck? β†’ ViαΊΏt ra:
  β”œβ”€ Đã thα»­ gΓ¬?
  β”œβ”€ KαΊΏt quαΊ£ ra sao?
  └─ NghΔ© hΖ°α»›ng nΓ o?
       β”‚
       β–Ό
  Hỏi Tech Lead trong Office Hours
  (slot cα»‘ Δ‘α»‹nh: 15:00-16:00)
       β”‚
       β–Ό
  Tech Lead KHΓ”NG giαΊ£i hα»™:
  β”œβ”€ Hỏi cΓ’u dαΊ«n dαΊ―t
  β”‚  "Em Δ‘Γ£ xem module X chΖ°a?"
  β”‚  "Pattern nΓ o tΖ°Ζ‘ng tα»± em tα»«ng lΓ m?"
  β”œβ”€ Gợi Γ½ hΖ°α»›ng
  └─ Để junior tα»± implement
       β”‚
       β–Ό
  Junior tự giải quyết + HỌC ĐƯỒC
Quy tαΊ―c cho Junior:

  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  30-Minute Rule                       β”‚
  β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
  β”‚                                      β”‚
  β”‚  Stuck < 30 phΓΊt β†’ Tα»± tΓ¬m hiểu     β”‚
  β”‚  Stuck > 30 phΓΊt β†’ Document vαΊ₯n đề  β”‚
  β”‚  Stuck > 1 giờ   β†’ Hỏi Tech Lead    β”‚
  β”‚                    (vα»›i context)      β”‚
  β”‚                                      β”‚
  β”‚  Format khi hỏi:                     β”‚
  β”‚  β”œβ”€ "Em Δ‘ang lΓ m task X"            β”‚
  β”‚  β”œβ”€ "Em Δ‘Γ£ thα»­ A, B, C"            β”‚
  β”‚  β”œβ”€ "KαΊΏt quαΊ£ lΓ ..."               β”‚
  β”‚  └─ "Em nghΔ© hΖ°α»›ng D, anh thαΊ₯y    β”‚
  β”‚      thαΊΏ nΓ o?"                      β”‚
  β”‚                                      β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Tình huống 2: Mid Dev Làm Chậm

VαΊ₯n đề:

  Sprint estimate: 5 story points
  Thα»±c tαΊΏ: chΖ°a xong sau 2 tuαΊ§n
       β”‚
       β–Ό
  Sprint bα»‹ delay β†’ team bα»‹ αΊ£nh hưởng
GiαΊ£i phΓ‘p β€” Team Productivity Model:

  Mid Dev chαΊ­m deadline
       β”‚
       β–Ό
  Tech Lead diagnose nguyΓͺn nhΓ’n
       β”‚
       β”œβ”€β”€β–Ί Scope unclear?
       β”‚    β†’ Clarify acceptance criteria
       β”‚    β†’ Break task nhỏ hΖ‘n
       β”‚
       β”œβ”€β”€β–Ί Kα»Ή thuαΊ­t chΖ°a biαΊΏt?
       β”‚    β†’ Pair programming 1-2 giờ
       β”‚    β†’ Chỉ direction, khΓ΄ng code hα»™
       β”‚
       β”œβ”€β”€β–Ί Over-engineering?
       β”‚    β†’ "MVP trΖ°α»›c, refactor sau"
       β”‚    β†’ Define "good enough"
       β”‚
       β”œβ”€β”€β–Ί Bα»‹ block bởi dependency?
       β”‚    β†’ Tech Lead unblock
       β”‚    β†’ Escalate nαΊΏu cαΊ§n
       β”‚
       └──► Personal issues?
            β†’ 1-on-1 empathy
            β†’ Adjust workload
Productivity Check Framework:

  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  Khi dev chαΊ­m, hỏi 5 cΓ’u:          β”‚
  β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
  β”‚                                      β”‚
  β”‚  1. Task cΓ³ clear khΓ΄ng?             β”‚
  β”‚     (vague spec β†’ slow delivery)     β”‚
  β”‚                                      β”‚
  β”‚  2. Task cΓ³ quΓ‘ lα»›n khΓ΄ng?           β”‚
  β”‚     (> 3 ngΓ y β†’ cαΊ§n break down)     β”‚
  β”‚                                      β”‚
  β”‚  3. Dev cΓ³ bα»‹ block khΓ΄ng?           β”‚
  β”‚     (waiting for API, design, etc.)  β”‚
  β”‚                                      β”‚
  β”‚  4. Dev cΓ³ Δ‘ang over-engineer?       β”‚
  β”‚     (perfect lΓ  kαΊ» thΓΉ cα»§a done)    β”‚
  β”‚                                      β”‚
  β”‚  5. Dev cΓ³ overwhelmed khΓ΄ng?        β”‚
  β”‚     (quΓ‘ nhiều tasks song song)     β”‚
  β”‚                                      β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

TΓ¬nh huα»‘ng 3: Senior Dev BαΊ₯t Đồng Architecture

VαΊ₯n đề:

  Tech Lead: "DΓΉng Microservices"
  Senior Dev: "Monolith tα»‘t hΖ‘n cho scale nΓ y"
       β”‚
       β–Ό
  Tension trong team
GiαΊ£i phΓ‘p β€” Architecture Decision Model:

  BαΊ₯t Δ‘α»“ng architecture
       β”‚
       β–Ό
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  Step 1: LISTEN first                β”‚
  β”‚  β”œβ”€ Nghe hαΊΏt argument cα»§a Senior    β”‚
  β”‚  β”œβ”€ Hỏi clarifying questions        β”‚
  β”‚  └─ KhΓ΄ng dismiss ngay              β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                     β”‚
                     β–Ό
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  Step 2: EVALUATE together           β”‚
  β”‚  β”œβ”€ ViαΊΏt Trade-off Analysis          β”‚
  β”‚  β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”‚
  β”‚  β”‚  β”‚Criteriaβ”‚Option Aβ”‚Option B   β”‚  β”‚
  β”‚  β”‚  β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€  β”‚
  β”‚  β”‚  β”‚Scaling β”‚  +++   β”‚    ++     β”‚  β”‚
  β”‚  β”‚  β”‚Speed   β”‚   +    β”‚   +++     β”‚  β”‚
  β”‚  β”‚  β”‚Complex β”‚  ---   β”‚    -      β”‚  β”‚
  β”‚  β”‚  β”‚Team expβ”‚   +    β”‚   +++     β”‚  β”‚
  β”‚  β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β”‚
  β”‚  └─ DΓΉng data, khΓ΄ng dΓΉng ego       β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                     β”‚
                     β–Ό
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  Step 3: DECIDE transparently        β”‚
  β”‚  β”œβ”€ Explain reasoning                β”‚
  β”‚  β”œβ”€ Acknowledge trade-offs           β”‚
  β”‚  └─ Document decision (ADR)          β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                     β”‚
                     β–Ό
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  Step 4: COMMIT as a team            β”‚
  β”‚  β”œβ”€ "Disagree and commit"            β”‚
  β”‚  β”œβ”€ CαΊ£ team follow quyαΊΏt Δ‘α»‹nh       β”‚
  β”‚  └─ Review lαΊ‘i sau 1-2 sprints      β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Architecture Decision Record (ADR):

  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  ADR #001: Service Architecture      β”‚
  β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
  β”‚                                      β”‚
  β”‚  Status: Accepted                    β”‚
  β”‚  Date: 2025-07-02                    β”‚
  β”‚                                      β”‚
  β”‚  Context:                            β”‚
  β”‚  Team size = 5, MVP phase            β”‚
  β”‚                                      β”‚
  β”‚  Decision:                           β”‚
  β”‚  Monolith first, extract services    β”‚
  β”‚  when needed                         β”‚
  β”‚                                      β”‚
  β”‚  Reasoning:                          β”‚
  β”‚  β”œβ”€ Faster delivery for MVP          β”‚
  β”‚  β”œβ”€ Team familiar with monolith      β”‚
  β”‚  β”œβ”€ Easier debugging                 β”‚
  β”‚  └─ Can extract later               β”‚
  β”‚                                      β”‚
  β”‚  Trade-offs:                         β”‚
  β”‚  β”œβ”€ (-) Harder to scale later       β”‚
  β”‚  └─ (+) Ship 2x faster now          β”‚
  β”‚                                      β”‚
  β”‚  Review date: Sprint 10              β”‚
  β”‚                                      β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ’‘ 10. Bad Tech Lead vs Good Tech Lead

Bad Tech Lead = BOTTLENECK

  Mọi thứ phải qua Tech Lead
       β”‚
       β–Ό
  Team chờ β†’ Delivery chαΊ­m
       β”‚
       β–Ό
  Team khΓ΄ng grow
       β”‚
       β–Ό
  Tech Lead burnout

════════════════════════════════════════

Good Tech Lead = MULTIPLIER

  Tech Lead enable team
       β”‚
       β–Ό
  Team tα»± chα»§ β†’ Delivery nhanh
       β”‚
       β–Ό
  Team grow liΓͺn tα»₯c
       β”‚
       β–Ό
  Tech Lead focus strategy
CΓ‘ch Δ‘o:

  Bad Tech Lead:
  β”œβ”€ Team output giαΊ£m khi TL vαΊ―ng
  β”œβ”€ TL lΓ  bottleneck mọi decision
  └─ TL code > 60% thời gian

  Good Tech Lead:
  β”œβ”€ Team hoαΊ‘t Δ‘α»™ng tα»‘t khi TL vαΊ―ng 1 ngΓ y
  β”œβ”€ Team tα»± ra nhiều quyαΊΏt Δ‘α»‹nh
  └─ TL focus architecture + strategy

🎯 11. Checklist Delegation Hiệu QuαΊ£

TrΖ°α»›c khi giao task

  • Task cΓ³ clear scope vΓ  acceptance criteria?
  • Đã match Δ‘ΓΊng developer vα»›i Δ‘ΓΊng level?
  • Developer hiểu WHY task nΓ y quan trọng?
  • Resources vΓ  references Δ‘Γ£ cung cαΊ₯p?

Trong khi thα»±c hiện

  • Check-in tαΊ‘i milestones (khΓ΄ng micromanage)?
  • SαΊ΅n sΓ ng unblock khi dev cαΊ§n?
  • KhΓ΄ng nhαΊ£y vΓ o code hα»™ khi dev gαΊ·p khΓ³?

Sau khi hoΓ n thΓ nh

  • PR review kα»Ή lΖ°α»‘ng vα»›i constructive feedback?
  • Acknowledge effort cα»§a developer?
  • RΓΊt kinh nghiệm cho lαΊ§n delegate sau?

Self-check hΓ ng tuαΊ§n

  • CΓ³ task nΓ o mΓ¬nh tα»± lΓ m mΓ  nΓͺn delegate?
  • Junior cΓ³ Δ‘ang được mentor Δ‘α»§?
  • Team cΓ³ thể hoαΊ‘t Δ‘α»™ng nαΊΏu mΓ¬nh vαΊ―ng 1 ngΓ y?
  • CΓ³ ai trong team Δ‘ang overloaded / underloaded?

πŸ’‘ Tα»•ng KαΊΏt

Tech Lead Delegation Model:

 1️⃣  Evaluate    β†’ ĐÑnh giΓ‘ task (complexity, urgency, risk)
 2️⃣  Match       β†’ Đúng người cho Δ‘ΓΊng việc
 3️⃣  Context     β†’ Cung cαΊ₯p WHY + WHAT + expectations
 4️⃣  Trust       β†’ Để dev tα»± implement, khΓ΄ng micromanage
 5️⃣  Review      β†’ Feedback constructive, celebrate wins
3 NguyΓͺn TαΊ―c VΓ ng:

  1. Hỏi "Ai phΓΉ hợp nhαΊ₯t?" trΖ°α»›c khi tα»± lΓ m
     β†’ Default = delegate, exception = tα»± lΓ m

  2. Giao task = giao cαΊ£ ownership
     β†’ Dev own outcome, khΓ΄ng chỉ code

  3. Delegation β‰  Dump
     β†’ Cung cαΊ₯p context + support + review
3 Models Thα»±c TαΊΏ:

  1. Unblocking Model
     β†’ 30-min rule + Office Hours + guided questions

  2. Productivity Model
     β†’ Diagnose root cause + 5 cΓ’u hỏi framework

  3. Architecture Decision Model
     β†’ Listen β†’ Evaluate β†’ Decide β†’ Commit
The Fundamental Truth:

  Senior Engineer  β†’ "I solve problems"
  Tech Lead        β†’ "I enable the TEAM to solve problems"

  Your output β‰  Your code
  Your output = Team's delivery

β€œThe best Tech Leads don’t do the most work. They make sure the right people do the right work.”


πŸ“š TΓ i Liệu Tham KhαΊ£o


BΓ i liΓͺn quan: