De colaborador individual a gerente de ingeniería

// ❌ The manager who is still an IC
// (This is metaphorical — the real anti-pattern)
class NewManager {
  // Still measures self-worth by personal output
  dailyRoutine() {
    reviewPRs(6); // You do ALL the reviews
    fixCriticalBug(); // Jump in to "save" the team
    writeArchDoc(); // Write it yourself because it's faster
    skipOneOnOnes(); // "Too busy shipping"
    attendStandUp(5); // minutes, barely listening
  }
  // Result: Team doesn't grow, you're a bottleneck,
  // you burn out doing two jobs
}

// ✅ The manager who multiplies
class EffectiveManager {
  dailyRoutine() {
    oneOnOne(teamMember); // 30 min, focused listening
    unblockTeam(); // Remove obstacles, not solve problems
    reviewArchDecision(); // Ask questions, don't dictate
    coachJunior(); // Pair, teach, then let go
    planCapacity(); // Think about next quarter
  }
  // Result: Team ships more than you ever could alone,
  // individuals grow, you build leverage
}

## One-on-One Framework
 
### Structure (30 minutes, weekly)
1. **Their agenda first** (15 min)
   - "What's on your mind this week?"
   - Listen. Don't solve. Ask clarifying questions.
   - Take notes on commitments you make.
 
2. **Your observations** (10 min)
   - Share specific feedback (positive and constructive)
   - "I noticed X in the PR review — here's why that matters"
   - Connect their work to larger team/company goals
 
3. **Growth and forward-looking** (5 min)
   - Progress on career goals
   - Upcoming opportunities to stretch
   - "Is there anything blocking you that I can help with?"
 
### Questions that unlock conversation:
- "What's the most frustrating part of your work right now?"
- "If you could change one thing about how we work, what would it be?"
- "What's something you want to learn in the next quarter?"
- "Is there a project or responsibility you'd like to take on?"
- "What feedback do you have for me?"

## Delegation Levels
 
### Level 1: Do exactly this
- New team member, unfamiliar domain
- "Implement the API endpoint following this spec exactly"
- Check in frequently, review carefully
 
### Level 2: Research and recommend
- Growing team member, building judgment
- "We need to improve query performance — investigate
   options and recommend an approach"
- Discuss their recommendation, coach the decision
 
### Level 3: Decide and inform
- Trusted team member, strong in the domain
- "The caching layer needs redesigning — make the call
   and let me know what you decide"
- Available if they want to discuss, but don't gate
 
### Level 4: Own it completely
- Senior/staff level, proven judgment
- "You own the authentication system — I trust your
   decisions on architecture and implementation"
- Check in on outcomes, not decisions
 
## Matching delegation level to the person:
- Under-delegating → micromanagement, team atrophy
- Over-delegating → setup for failure, anxiety
- Right-delegating → growth, trust, leverage

## The SBI Framework (Situation-Behavior-Impact)
 
### ❌ Vague feedback
"Your code quality needs improvement."
→ What code? What quality? Improvement how?
 
### ✅ Specific feedback using SBI
"In yesterday's PR for the payment service
(Situation), the error handling caught all exceptions
with a generic handler instead of handling each failure
mode specifically (Behavior). This means production
errors will be harder to diagnose because the stacktrace
context gets lost (Impact)."
 
### ❌ Character judgment
"You're not a team player."
→ Defensive response guaranteed
 
### ✅ Behavior-focused observation
"In the last two architecture discussions (Situation),
you presented your approach without acknowledging
the tradeoffs or asking for alternative viewpoints
(Behavior). This made other team members feel their
input wasn't valued, and we missed potential issues
that came up later (Impact)."
 
### Following up:
- Ask how they see the situation
- Listen to their perspective — you might be wrong
- Agree on specific next steps together
- Follow up in the next 1:1 to acknowledge improvement

## Performance Tracking System
 
### Weekly observations (private notes)
- What did each team member ship?
- Where did they struggle?
- What skills are developing?
- Any concerning patterns?
 
### Monthly synthesis
- Review weekly notes for patterns
- Compare actual vs expected performance
- Identify coaching opportunities
- Prepare for any necessary conversations
 
### Quarterly career conversations
- Where are you now vs. where do you want to be?
- What specific skills need development?
- What projects would stretch those skills?
- What does the next level look like for you?
 
### The performance conversation spectrum:
  ┌──────────────────────────────────────────┐
  │ Positive  → Coaching → Concern → PIP     │
  │ "Great    "Here's     "This    "Formal   │
  │  work on   how to      needs   improve-  │
  │  X"        level up"   to      ment      │
  │                        change" plan"     │
  └──────────────────────────────────────────┘
  Most feedback should live on the left side.
  If you're jumping to the right, you waited too long.

## Meeting Audit Checklist
 
For every recurring meeting involving your team, ask:
1. Does this meeting have a clear purpose?
2. Does my team member need to attend, or can I represent?
3. Could this be an async update instead?
4. Is the attendee list the minimum necessary?
 
## Shield patterns:
- Attend cross-team syncs yourself → relay relevant info in standup
- Batch interruptions → "I'll check with the team and get back to you today"
- Protect maker schedule → no-meeting blocks on the team calendar
- Filter context → not every leadership concern needs to reach your team