I still remember the day my manager told me I was being promoted to tech lead. I felt proud, sure, but also a little terrified. Mostly I thought it meant I'd finally get to write more code. I was wrong about that, and it nearly sank my team.
The first month was brutal. I treated the role like being a senior developer with a fancier title. I reviewed every pull request line by line, sometimes rewriting things myself because it was faster than explaining the change. I volunteered for the hardest tickets and stayed late to finish features the team was struggling with. It felt productive, but the team was slowing down. People stopped making decisions without asking me. I became a bottleneck and didn't even realize it.
The wake-up call came during a sprint where everything slipped. We missed a deadline by a week, not because the work was too hard, but because everyone was waiting on me. One of the quieter developers, a guy named Marcus, finally pulled me aside and said, "You're not letting us help you lead." That stung, but he was right. I had confused being useful with being essential, and I was making myself essential in the worst possible way.
So I started changing how I worked. Instead of fixing a bug myself, I'd pair with someone and talk through the investigation. Instead of giving a direct answer to "what should I use here?", I'd ask what they'd already considered and why. I scheduled fifteen-minute one-on-ones every week, not to check status, but to find out what was blocking people and quietly remove those blocks. It was uncomfortable at first. I felt like I wasn't doing real work. But then the team's velocity picked up, and I noticed people were bringing me problems I hadn't seen, with solutions already half-formed.
The hardest lesson was that my value stopped being measured by lines of code or clever fixes. It became measured by how well the team could operate without me. One morning I looked at the sprint board and realized I hadn't written a single line of production code in two weeks, and nothing had caught fire. That was the first time I felt like a real tech lead.
These days, I still miss the keyboard sometimes. I'll grab a small bug or write a quick script just to stay grounded. But I no longer confuse that with my actual job. The job is creating an environment where other developers can do their best work. That took me longer to learn than any framework or design pattern, and it's the part nobody tells you about when they hand you the title.