A team of six names its most experienced developer tech lead and nobody writes the job down. He keeps coding most of the week and coordinates the rest in the gaps. No architecture decision has an owner, every sprint tries another stack, and onboarding a new engineer takes weeks because no standard exists to follow.
The designated tech lead spends the week coding
The title came out of a Slack label. With no written scope, the senior engineer picks up two extra jobs: reviewing everything and putting out fires. Long-term decisions lose their owner and each person reaches for the tool they already know. Seven engineers end up with four frameworks solving one problem.
Hiring a full-time CTO for six people changes the problem. His calendar fills with administrative meetings while Tuesday's technical decision keeps waiting. You need someone who reads the repository every week.
The technical lead's work in a small team
Architecture decisions with an expiry date. The lead sets a standard for the next 6 to 12 months and writes down why it holds until then. He reviews it when the team grows; nobody inherits a permanent obligation.
Review against a written standard. Review keeps purposeless code out of the repository and keeps the standard visible. CI catches the bug; review catches the debt.
Mentoring inside the work. In a small team, mentoring is pair programming on Friday and a discussion in the middle of a review. A weekly mentoring meeting is surplus in a team of three.
Scope defense. The lead turns down the feature that breaks the architecture, writes the reason, and proposes the cheapest cut.
The team pays later
With nobody holding a system view, technical debt grows with no report. Onboarding takes weeks, bugs return because the review changes with the reviewer, and the team spends sprints refactoring code one person picked in 2024.
Three routes without a full-time role
- A consulting Staff Engineer, 20 to 30 hours a month. He sets architecture, writes standards, and reviews real code. The fee lands at a fraction of a full-time hire and shows up in the first sprint.
- A fractional CTO, once or twice a week. He comes in for strategy, technical governance, and the conversation with the business. The repository keeps its daily owner.
- Leadership spread across two or three seniors. One takes architecture, another infrastructure. Each signs for a domain and both review each other.
Will Larson lays out a role measured by decision reach in Staff Engineer (O'Reilly, 2021): in a small team, the person signing architecture already lives in the code. Martin Fowler describes the small-team architect who codes and leads at once in "Who Needs an Architect?" (IEEE Software, 2003).
A small team needs leadership attached to the repository: someone who signs decisions, holds the standard, and turns down scope the team cannot pay for. Hire it when the team reaches five, before rework becomes habit.
