Leading Without a Title

I Was Asked to Lead Without the Title

My team lead went on parental leave, and I was asked to serve as "tech lead" for 6 months. Not an official title — just a "hey, take the lead on technical decisions for the team." I was a 4-year mid-level developer, not even a senior. I still don't know why they picked me.

For the first two weeks I couldn't do anything. Paralyzed by "am I really allowed to make these decisions?" I postponed everything — tech stack choices, code review standards, sprint priorities. Every time a teammate asked, I just said "let me think about it more."

(I could feel the team getting frustrated. When a leader delays decisions, the whole team grinds to a halt.)

First Mistake: I Tried to Do Everything Myself

Taking on the lead role created this pressure that "I need to know everything." When team members had technical questions, I felt obligated to have the answer. But some areas were beyond my expertise. When infrastructure questions came up, I'd study all night to have an answer by morning.

After about a month, I was running on empty. Coding, leading, and studying everything I didn't know. This wasn't sustainable.

The breakthrough was simple. I asked a teammate "I'm not strong in this area — could you research it and share with the team?" A leader doesn't need to know everything. Admitting what you don't know and delegating to the right person is leadership too.

I Learned How to Make Decisions

With technical decisions, you almost never have 100% confidence. But not deciding means nothing moves. I adopted a principle: "if I'm 70% sure, decide. Validate the remaining 30% during execution."

When choosing a state management library for a new project, I spent a week going back and forth between Zustand and Jotai. Compared pros and cons, got team input, built a small POC. Still only about 80% sure. "Let's go with Zustand. If we hit issues in 2 weeks, we'll revisit." It turned out to be a good call.

The Challenge of Leading Without Authority

Without official authority, you can't give directives. It's "what if we did it this way?" instead of "do it this way." But this actually builds better leadership habits. Since you have to move people through persuasion, you learn to prepare logical arguments.

Once I proposed stricter code review standards, and one team member pushed back hard. "Reviews that are too strict slow us down." If I'd had the title, I might have just pushed it through. Without it, I had to work it out through dialogue. We ended up with a compromise that the whole team was happy with.

Six Months Later

The team lead came back and I returned to my regular role. My title hadn't changed at all. But how I work changed. I developed a wider view of the team, and the anxiety around making decisions decreased. I gained confidence that "I'm allowed to make decisions."

What the team lead said when they returned stuck with me: "The team would have been really shaky without you. Thank you." That one sentence made 6 months of struggle feel worth it.

Leadership isn't given by a title — it's built by action. That sounds nice, but in reality, leading without authority is draining. Responsibility without power is honestly tough. Still, going through it once is guaranteed growth.