Engineer
After five years as an individual contributor, I took a tech lead role on a team of seven. I had never run a planning meeting or written a roadmap. The first month was rough. I tried to lead by being the best engineer in the room, and the team started routing decisions through me as a bottleneck. I asked another tech lead at the company for a weekly thirty-minute mentoring slot. He told me bluntly that my job was no longer to be right; my job was to make the team right. I started running planning by asking each engineer what they thought the priority should be before I spoke. Velocity in the next quarter went up about thirty percent. I shipped less code personally and felt unproductive for two months. The thing that changed in me was learning to feel productive based on what the team produced instead of what I personally typed.