This was also published as a Twitter thread here

Don’t Let Fear Hinder Your Growth: Staying Technical as a Tech Leader

You’ve been leading teams for a couple of years now, and your next role “seems” even less technical. You’re unsure and maybe even borderline afraid: “What if I lose my tech chops?” Don’t let that fear hold you back! Here are some thoughts and ideas to help you understand that technical skills are contextual, impact is key, and you can stay sharp as a leader. Let’s dive in. Understanding the Fear

It’s common for tech leaders to worry about losing their technical edge as they move into more strategic or operational roles. You might feel like you’re drifting away from the hands-on work you love—coding, debugging, or diving deep into systems. But here’s the truth: technical skills don’t disappear; they evolve. They become contextual, tied to the impact you create rather than the day-to-day execution.

Before we get into the “how,” make sure you read the PSHE framework thread I shared earlier. It’s crucial to understand what matters at each stage of your career—Problems, Solution, How, Execution (PSHE)—so you can see where you fit and where you’re headed. How to Stay Technical in an Operator Role

You don’t have to let go of your technical roots. Here’s a simple way to stay sharp:

Block 60–90 Minutes for Deep Dives: Set aside regular time—daily or weekly—to dive deep into specific technical areas. Don’t waste time on random blogs or passive videos; pick an area and go deep. You could:

• Read a research paper.
• Tinker with a simple example or prototype.
• Study documentation thoroughly.
• Pair up with a hands-on person to debug or explore a problem together.

This disciplined approach keeps you engaged with technology without overwhelming your leadership responsibilities.

Why This Works (and Why You Might Doubt It)

If you’re skeptical that this will work, look at Adrian Colyer’s example. As a venture capitalist, he spent over 1,000 days writing summaries of computer science papers every morning on his “Morning Paper” blog. He didn’t have to do it, but he chose to stay technically sharp. I believe most often, it’s not a lack of time or opportunity—it’s a lack of discipline that prevents us from staying technical.

Building a Routine for Continuous Learning

Without external pressure, a consistent routine is your best tool for staying focused on learning tech. Here’s the key: avoid passive consumption. Don’t spend more than 20% of your learning time on blogs or videos—they create an illusion of knowledge without depth. Instead, prioritize active learning:

• Read documentation or debug issues hands-on.
• Review code for your team or design critical systems.
• Tackle a production issue and dive into the root cause.

As you grow into higher roles, your learning hour should feel like acting as an “editor”:

• Review designs or code for quality and consistency.
• Tinker with new technologies or read computer science papers.
• Develop a viewpoint on a technical challenge—and write it up.

Why Writing Matters

Nothing clarifies your thinking like writing does. It’s hard work, but it pays off! If you’re in a senior role and your learning doesn’t involve writing, you’re probably not learning as deeply as you could. Writing forces you to process ideas, connect dots, and solidify your understanding. As I’ve shared before, writing is a mirror—it reveals what you truly know (or don’t).

Inspiration from Thought Leaders

For more on this topic, check out this insightful article by Gregor Hohpe, which inspired this post. It’s a great resource to apply these ideas in your context.

The Bottom Line

Don’t let the fear of losing your technical edge stop you from growing as a leader. Technical skills are still crucial—they’re just contextual, tied to the impact you create. By blocking time for deep dives, building a disciplined routine, and writing to clarify your thinking, you can stay technically sharp while leading effectively. You’ve got this!