What is the role of team leads
Principles
- Team leads increase leverage; they do not add hierarchy.
- This is a player-coach role, not a management career ladder step.
- The role stays intentionally lightweight and execution-focused.
- Team leads are not managers.
Why team leads exist
As teams grow to around four people, priorities blur and founders can become bottlenecks.
Team leads create clarity, protect quality, and reduce escalation. They do not exist to control people or slow decisions.
Time allocation
At least 80% of time should remain in individual contribution. If a lead stops shipping or loses user proximity, role scope is too heavy.
How decisions are made
Teams keep autonomy by default. Team leads step in mainly for priority conflicts and quality disagreements.
What a team lead facilitates
Direction
Translate company goals into clear near-term priorities and explicit trade-offs.
Quality bar
Raise "good enough" standards for craft, usability, and correctness.
People care
Provide direct feedback and help teammates unblock quickly.
What team leads are not
- Do not approve every decision.
- Do not micromanage execution.
- Do not own compensation or promotions.
- Do not run performance reviews.
Founder relationship and cadence
Founders still skip-level and review work periodically, but are no longer default escalation paths.
Cadence stays minimal: quarterly lead/founder check-in, annual hiring planning, and no standing weekly status meetings.