HighLoad++ · May 18, 2021
What a CTO is, from startup to IPO
The organizational lifecycle and the role of the technical director
/ What is a CTO from Startup to IPO · HighLoad++ Spring 2021
The organizational lifecycle and the role of the technical director
The organizational lifecycle and the role of the technical director
Who this talk is for
What does a career in IT actually look like?
Is it worth growing into a team lead and beyond?
How do you do it right?
What we'll cover
The characteristics of each lifecycle stage
The CTO's role at every stage
Examples from real life
CTO levels and what each transition takes
Startup → Growth → Maturity → Decline
With turning points between them
Startup — the startup stage
Growth — the collegiality stage
Maturity — formalization, then growing complexity
Decline — the decline stage
The startup stage
Unclear goals and high creative freedom
The steps: idea → MVP → funding
At every step business and engineering move together
Characteristics: unclear goals
And high creative freedom
The collegiality stage
Scaling, done right
The loop: idea → requirements → design
…development → deploy → operations
A cross-functional team closes it
Plus a product manager at the entry and a lead inside
The collegiality stage
Defining the mission and the growth strategy
Informal communication and structure
High commitment
Roughly fifty people by scale
Process Orientation, Technical Capabilities and Scale
Process Orientation — how much the role is about process
Technical Capabilities — how much it is about depth
Scale — how many people are below: ~10, ~50, ~150
Delivery manager and Architect are the axis extremes
Formalization, then growing complexity
Formalizing structure and management
Growth stabilizes
Roles and rules get formalized
The structure stabilizes
The emphasis shifts to efficiency
An example from banking
From a monoline bank to an ecosystem — per the «Bank 4.0» book
2007–2020: Tinkoff Black, mobile bank, investments, a mobile operator
Business verticals: retail, business, investments, insurance, travel
And platforms on top of the infrastructure
The structural complexity stage
Growth slows and the structure changes
Markets diversify
Management decentralizes
All-in-one CTO → CIO, CTO, VP of Engineering
The decline stage
The talk assigns no new CTO role here
Revenue falls
Employee turnover rises
Conflicts build up
Management centralizes
CTO levels and the transitions between them
And what to pull up before the next transition
What to take with you
Every stage has its own CTO role
The unit of scaling is a team, not a person
Delivery manager and Architect are axes, not rungs
Every transition means pulling up the weaker axis
The sources from the talk's closing slide
«Team Topologies» and «Technology Strategy Patterns»
«The Art of Leadership: Small Things, Done Well»
«Digital Transformation Game Plan» and «Bank 4.0»
Articles on the org lifecycle and the CIO/CTO/VP roles
polomodov.tech
All slides and links are in the Telegram channel
Alexander Polomodov, Technical Director & Fellow, T-Technologies
@book_cube