There's a role most engineering orgs depend on and few describe well. You're accountable for a team delivering something. You run the standup. You track the risks. You answer when leadership asks, "Where are we?"
But nobody reports to you. You don't write reviews, approve time off or set pay.
Call it tech lead, squad lead or delivery lead. Will Larson's short version: the tech lead "guides the approach and execution of a particular team." [1] The title varies. The tension doesn't.
You're responsible for outcomes without authority over the people producing them.
I do this job now. Here's what I've learned about doing it without burning out or turning into the team's unpaid project administrator.
The Trap: Becoming the Team's Janitor
The most common failure I see, and one I've committed myself, is confusing ownership with cleanup.
You own the feature, so when tickets go stale, you update them. When status is unclear, you chase it down and write it up yourself. When a task has no owner, you take it. When the tracker drifts from reality, you fix it on Sunday night so Monday's review looks right.
Tanya Reilly named this years ago in her talk "Being Glue": the essential, invisible work that holds a team together, and that rarely counts when it's time for promotions. [2] It's corrosive for three reasons:
- It hides the real state of the team. If you're quietly patching every gap, nobody, including leadership, can see where the system is breaking.
- It takes ownership away from engineers. If the lead keeps everyone's work current, why would anyone else?
- It doesn't scale. Your time goes to maintenance instead of the things only a lead can do.
Lesson: If you fix every gap quietly, the gaps never get fixed. They just get hidden.
What a Lead Actually Owns
The model I've landed on is simple to say and hard to stick to.
Each engineer owns keeping their own work visible, current and reviewable. Their tasks reflect reality, blockers are written down, and anyone could look at their items and understand where things stand. That's not bureaucracy. It's basic professional courtesy to the rest of the team.
The lead owns coordination and escalation. That means agreeing on what "done" means for the current goal, spotting dependencies and collisions before they become problems, escalating blockers the team can't clear on its own, saying "no" or "not yet" to work that doesn't serve the goal, and telling the truth upward about status, even when it's bad.
Each engineer owns
- Tasks that reflect reality
- Blockers written down
- Work anyone can read and understand
The lead owns
- A shared definition of done
- Dependencies and collisions
- Fast, specific escalation
- "No" or "not yet"
- The truth, upward
Not on the lead's list
- Rewriting other people's tickets
- Maintaining every child task
- Carrying status in your head
Notice what's not on the list.
Influence Without Authority
If you can't direct people, what do you have? More than you'd think.
Clarity. The most underrated leadership tool is a clear, written statement of what we're doing and why. When the goal is fuzzy, people fill the gap with their own priorities. When it's pointed, most coordination problems disappear. Google's research on effective teams found the same thing: "structure and clarity," meaning clear roles, goals and plans, was one of five dynamics that set its best teams apart. [3]
Visibility. I use visibility, not pressure. A short weekly summary of where each piece stands, pulled from what people recorded themselves, does more than any number of reminders. People respond to seeing their work in the context of the whole.
Escalation as a service. Engineers often don't escalate because it feels like complaining. A good lead makes escalation cheap: "Tell me what's blocking you, and I'll take it to the right person." That turns you from a status collector into someone who removes obstacles. People notice the difference.
Credibility from doing the work. Leads who still ship, even small things, have a standing that pure coordinators don't. You don't need to be the strongest engineer in the room. You do need to understand the work well enough to know when an estimate is fiction.
Pointed, Not Fuzzy
The habit I work hardest at is keeping every meeting and message pointed instead of fuzzy.
In meetings, that means:
- Start with the decision or question, not the background. If there's nothing to decide, it might be a message, not a meeting.
- Every topic ends with an owner and a next step, or it's explicitly parked.
- Separate facts from opinions. "It's late" is a fact. "I think it'll slip again" is a judgment. Both are useful. Mixing them isn't.
In writing, it means signal over noise. A status update isn't proof of how busy the team was. It's the few things the reader needs to know or do. If an update has ten bullets and one of them matters, the one that matters gets lost.
Lesson: A team used to pointed communication escalates sooner, argues less and spends less time in meetings.
Nudges, Not Nagging
Every lead eventually has to deal with stale work. The question is how.
Nagging is personal, repetitive and scattered: individual pings, follow-ups to follow-ups, the same reminder in three channels.
A nudge is predictable, consistent and impersonal: the same short message, at the same time each week, showing everyone the same view. It doesn't single anyone out.
If you automate a nudge, roll it out like code. Send it only to yourself first and ask whether it's helpful or annoying. Then try a small pilot. Then go wide.
Saying the Hard Thing Upward
The part of this role that matters most to leadership is also the part people avoid: reporting bad news early.
A lead who says "we're at risk on this date, here's why, here's what would fix it" two weeks out is worth far more than one who reports green until the day before. Without managerial authority, your credibility is most of what you have. Spend it on honesty.
My format for a hard status update is three lines: what's true, what it means, and what I need.
- What's true
- Integration testing found two blockers. One needs a fix from another team.
- What it means
- The release date is at risk by about a week.
- What I need
- A decision by Thursday: cut the reporting feature, or move the date.
What I'd Tell a New Lead
- Write down what each person owns and what you own. Share it. Revisit it when it drifts.
- Don't fix what the team should fix. Point at it, offer help and let the gap be seen.
- Protect a few hours a week for work only you can do: the next goal, the risks no one is watching and the people who need unblocking.
- Keep meetings and messages pointed. Signal over noise.
- Make escalation easy, and use it fast.
- Tell the truth upward. Early.
Leading without managing is a real skill, and it's increasingly how good engineering work gets done.
The goal isn't control. It's a team where the state of the work is obvious, blockers get removed and nobody has to clean up after anyone.
References
- Will Larson, Staff archetypes, StaffEng.
- Tanya Reilly, Being Glue (2019).
- Google, Five dynamics of effective teams.