CTO Lifecycle
Startup Coder → Engineering Manager → All-in-one → role split
Leadership
When to use
Use when aligning which CTO profile the company needs at its current growth stage.
The source model has five organizational stages. The CTO is a Startup Coder at the beginning, an Engineering Manager during growth, and an All-in-one CTO during formalization. As the structure becomes more complex, that role splits into CIO, CTO, and VP Engineering. The talk assigns no new CTO profile to decline.
Channel → Product → Platform
Three-step evolution of a large fintech
PlatformArchitecture
When to use
Use when product and platform strategies start to conflict because they are in different phases.
The case timeline starts with the company founding in 2006 and internet banking in 2008. Mobile banking appears as an additional channel in 2011, becomes a product in its own right in 2015, turns into a platform in 2019, and reaches the question of what comes next in 2022.
Senior+ Fork
Management track vs IC track
Leadership
When to use
Use when an engineer chooses the next step after Senior and the company designs a dual ladder.
After Senior, a career may split into management and IC tracks. In the source diagram, Leadership marks the transition into management rather than a separate grade. The exact steps—Engineering Manager or Director, Staff or Principal—depend on organizational design and do not form a universal ladder.
Engineering Productivity
DORA + DevEx + SPACE — three lenses, one picture
ProductivityLeadership
When to use
Use when engineering productivity needs a metric system rather than a single counter.
DORA, DevEx, and SPACE are complementary lenses rather than interchangeable metric sets or literal overlapping sets. DORA reads delivery through the current five metrics: change lead time, deployment frequency, failed deployment recovery time, change fail rate, and deployment rework rate.
Agent Stack Map
Three independent decisions → eight reference patterns → a portfolio
AI-nativePlatformArchitecture
When to use
Use when deciding which agent stack to allow and how to end the build-versus-buy argument.
The argument 'our own client on our own model versus a vendor agent over an API' conflates independent decisions. Harness, model and tools are chosen separately: each axis carries its own data path, cost, failure point and vendor lock-in.
Replayable Episode
Start state → contract → hidden judge → trace → release gate
AI-nativeProductivity
When to use
Use when turning real work into an agent evaluation robust enough to support a release decision.
The smallest unit of agent evaluation is not a benchmark question but a replayable episode: a small copy of real work. For code the start state is the commit before the pull request, for an incident the system at T0, for data a snapshot of the data, catalog and lineage.
Stack Ownership Boundary
Change rate × uniqueness → rent · adapt · own
AI-nativePlatformLeadership
When to use
Use when deciding what to rent in your AI stack, what to adapt, and what to keep owned.
For a technology leader the question is not which logo to pick but where to draw the ownership boundary. Two axes give the answer: how fast a component changes and how unique it is to your environment.
Architecture Memory Graph
6 nodes · 7 link fields · one change, both directions
ArchitectureAI-native
When to use
Use when checking whether the organization is ready for an architect AI assistant and where the decision chain breaks.
The artifacts usually exist: requirements, ADRs, models, code, SLOs and runtime signals. What is missing is the chain between them — documents sit in six different systems while people provide the continuity.
The CTO Transition
−30 → 00 → 30 → 90: the transition starts before day one
Leadership
When to use
Use when entering an executive role or hiring a leader and you want the transition milestones up front.
A transition is usually counted from the first working day. For a CTO that is late: by then the company, the task and the people are already chosen. The four phases are linked — weak research weakens the contract, a weak contract hampers diagnosis, and rushed diagnosis leads to the wrong changes.