Chris and Roberto tackle a challenge that every leader who rose through technical ranks eventually faces—the moment when your old skills have faded enough that holding onto that work actually hurts your team more than it helps. They share candid personal stories about making peace with that transition and doing it the right way. 🌱
Here's what we covered:
🧠 The Honest Self-Assessment: We discussed the critical first step—recognizing when your technical skills have become rusty enough that helping the team could actually create more work for them than doing it yourself. Self-awareness is the entry point to effective delegation. 🪞
💬 The Frank Conversation: Chris recommended sitting down with the team and openly explaining the transition—not pretending to still be the technical expert, but honestly saying "my skills in this area will fade, and I need you to step up here." Humane leaders never fear that conversation. 🗣️
⚠️ The Rusty Expert Problem: Chris illustrated the real danger—a manager who insists on staying involved in technical work they've grown out of touch with can cause three weekends of cleanup work for the team by breaking things they didn't realize had changed. Good intentions, bad outcomes. 📉
🛤️ Two Career Tracks: Roberto clearly laid out the engineering career reality—technical track (senior, staff, principal, VP of engineering staying hands-on with code) versus management track (engineering manager, head of engineering, VP focused on people and strategy). Neither is better. Both require deliberate commitment. 🎯
🔁 What Changes in Your Metrics: Roberto shared a powerful personal insight—as an IC he was measured by features shipped and lines of code written. As a manager, he's measured by his team's features, his team's code, his team's growth. The scoreboard changes completely when you change roles. 📊
🚪 Don't Fall Into the Trap: Chris admitted he fell into it himself early on—believing the technical skills that earned the promotion should keep being the focus. His director pulled him aside and said clearly: the next promotion requires letting those skills go. The door opened because of them, but staying in the doorway blocks your path forward. 🏆
🤖 AI and the Technical Bridge: Roberto shared how he now uses Claude Code for personal projects—not to stay sharp as a coder, but because understanding fundamentals lets him have meaningful architectural discussions with his team without pretending to be current on every new methodology. 💡
📚 Continuous Learning Never Stops: Both hosts emphasized that choosing the management track doesn't mean learning stops—it means learning shifts. Coaching for success, managing timelines, motivating people, and reading team dynamics become the new curriculum. Roberto continues actively training in management skills and finds it deeply fulfilling. 🌱
🤝 Addressing the Dumping Perception: Chris raised a key humane leadership move—proactively asking your team "does this feel like I'm dumping on you?" before they feel it but don't say it. Naming the discomfort removes it. 🧩
⚡ The IC-to-Manager Identity Shift: Roberto connected this episode to their interview with Vicente—the moment you get promoted, your relationships with former peers change whether you want them to or not. Accepting that shift, rather than resisting it, is what makes the transition clean and respectful for everyone. 🔄
Leadership means knowing not just what you're capable of, but what you're no longer the right person to do—and having the honesty and humility to hand it off well. This week, we celebrate the leaders who let go gracefully so their teams can grow fully.
🎧 Don't miss this deeply practical conversation! Download and listen through your favorite podcast platform.
