Team Lead

They're the person who reviews pull requests *and* attends the resource planning meeting. Who mentors the junior designer *and* ships the hero section for the client deadline. Who the team goes to when they're stuck *and* the project manager goes to when they need a technical reality check.

The team lead sits in the uncomfortable space between doing and managing. They're not a full-time manager — they're still producing work. But they carry leadership responsibilities that eat into their billable hours, and most agencies don't account for that in their scheduling.

The Scheduling Blind Spot

Here's the problem. A senior developer's availability says 160 hours per month. If they're a team lead, realistically 20-30 of those hours go to leadership activities: code reviews, 1:1s, architecture decisions, mentoring, sprint planning, and being the escalation point when something breaks. Their actual bandwidth for project allocations is closer to 130 hours.

Most agencies don't reduce the team lead's schedulable capacity to reflect this. Result: they get allocated like any other senior, plus they carry leadership overhead, which means they're effectively overallocated every single month. It's systematic, invisible, and it's why team leads are often the first to burn out.

Team Lead vs. Project Manager vs. Resource Manager

Three different roles, sometimes confused:

• Project manager — owns the project delivery. Manages timeline, budget, client.
• Resource manager — owns the allocation of people across projects. Manages capacity.
• Team lead — owns the team's craft quality and growth. Manages people's skills and output.

In a small agency, one person might wear all three hats. As teams grow, these split. The team lead's unique value is that they're close enough to the work to catch quality issues early and close enough to the people to spot burnout before it shows up in delivery failures.

Making It Work in the Schedule

The fix is simple in concept: reduce the team lead's schedulable hours to account for their leadership duties. If they have 160h of capacity and you expect 25h of leadership work per month, set their project-available hours to 135. WrkSched's per-person capacity settings handle this — set the weekly hours to what's actually available for project work, and the utilization reports and workload balancing will reflect reality.

The harder fix is cultural. Agencies need to stop treating leadership overhead as invisible. Those 25 hours of mentoring, reviewing, and coordinating are an investment in team quality — and they should be valued, not hidden in someone's "spare time."

When to Formalize the Role

Teams of 3-4 people in a discipline (design, development, etc.) benefit from a team lead. Below that, the overhead isn't justified. Above 8-10, you might need a full-time manager instead — someone who stops producing project work entirely and focuses on people and process. The team lead role is the bridge between "everyone reports to the founder" and "we have proper management layers."