The founding CTO of a 30-engineer startup still writes code full-time. Architecture decisions pile up in his queue, seniors stop proposing changes because the review takes days, and the organization stops evolving because nobody with a mandate to run architecture is running it.
Signals that the bottleneck is you
- Your pull requests sit while the rest of the team waits for an answer
- Seniors already say "Marc will review it later" and move on with the work half done
- A weighty technical decision becomes a meeting because you hold the whole context
- No engineer on the team can explain the full architecture to a new hire
The four signals point to one cause: the CTO role changed and you kept the old job. Melvin Conway described in "How Do Committees Invent?" (Datamation, 1967) that the design of a system mirrors the communication of the people who build it. With one person at the center of every decision, every design passes through her and ages at her pace.
The work that sits with the CTO
Three fronts go without an owner while you are in the editor: the technical direction for the next 18 months, with the trade-offs that make the cut and the ones that do not; the development of technical people who can take decisions that currently come to you; and the fit between engineering strategy and product goals.
Andrew Grove measures a manager's work by what the organization sustains without them, in High Output Management (Vintage, 1985). Code you keep for yourself is the smallest of the levers in your hand. Marty Cagan describes product teams that decide close to the work when leadership sets direction and limits in Empowered (Wiley, 2020). Without that move, the team waits for you in code and in direction at once.
A 90-day transition
Days 1 to 30. Transfer one domain at a time, starting with the one that depends on you least. Remove the critical dependencies from your path: who approves deploys, who runs on-call, who reviews the payment module.
Days 31 to 60. Cut code review down to changes that alter contracts between modules. Keep two days a week for technical contribution and reduce the frequency every two weeks.
Days 61 to 90. Stop when the organization answers without you in the code. If one decision comes back to you twice in the same week, that domain still sits with you.
What you are afraid of
Losing relevance, watching someone fail where you would not, drifting away from the tooling. Every founding CTO crosses those three. The cost of staying shows up in weeks of stalled decisions and in a team that trained nobody to take your place.
What comes back
Within three to six months, decisions that waited on you move without a meeting, two engineers run design reviews alone, and you get full days back for direction. Two weeks of vacation later, the pull requests keep getting approved and the on-call rotation has an owner.
