Skip to main content

The Art of CTO Technology Tree is an interactive AoE-style progression map that visualises maturity across engineering domains — from ad-hoc practices to elite capability — with actionable steps, effort estimates, and cross-domain dependencies.

Tech Tree · Engineering

Engineering Organisation Maturity

Progress your engineering organisation from ad-hoc practices to optimised, data-driven excellence. Each node represents a capability with concrete steps, effort estimates, and cross-domain dependencies.

Maturity tiers
  1. Ad-hoc

    Informal, inconsistent practices. Individual heroics over repeatable process.

  2. Repeatable

    Core practices documented and followed. Outcomes are predictable within a team.

  3. Measured

    Quantitative goals set and tracked. Decisions driven by data, not instinct.

  4. Optimised

    Continuous improvement embedded in culture. Feedback loops operating at every layer.

Tracks

  • Process

    How work is planned, executed, reviewed, and improved.

  • People

    How engineers are hired, grown, structured, and led.

  • Technology

    The tools, systems, and practices that deliver software.

  • Culture

    The shared values, behaviours, and psychological safety of the team.

All capabilities (18)

Ad-hoc

  • Defined Development Process

    A lightweight, written process for how work moves from idea to production. Includes ticket creation, code review, and release steps.

    process · agile · workflow

  • Psychological Safety

    Engineers feel safe to raise problems, admit mistakes, and challenge decisions without fear of punishment or ridicule.

    culture · safety · leadership

  • Team Structure

    Teams have clear ownership boundaries, reporting lines, and a stated purpose. Responsibilities do not overlap in ways that cause confusion.

    org-design · team-topology · ownership

  • Version Control

    All code lives in a shared version-control system. Branching conventions are agreed and followed consistently.

    git · source-control · foundation

Repeatable

  • Automated Testing

    A meaningful suite of automated tests covers critical paths. Test coverage is tracked and ownership is clear.

    testing · quality · coverage

  • CI Pipeline

    Every commit triggers an automated build and test run. Broken builds block merges and are fixed within the hour.

    ci · automation · devops

  • Engineering Ladder

    Clear, written levels and expectations for individual contributors and managers. Promotions are transparent and criteria-based.

    career · leveling · growth · people

  • Feedback Culture

    Constructive feedback flows in all directions — peer-to-peer, upward, and downward — on a regular cadence.

    feedback · 1:1 · communication

  • Sprint Cadence

    Teams work in consistent time-boxed iterations with planning, review, and retrospective ceremonies. Velocity is predictable.

    agile · scrum · cadence

Measured

  • Architecture Review

    Significant technical decisions go through a lightweight Architecture Decision Record (ADR) process with cross-team review.

    architecture · adr · governance

  • Continuous Deployment

    Every green main-branch commit is deployable. Most deploys are automated and happen multiple times per day without manual gates.

    cd · devops · automation · dora

  • DORA Metrics

    Deployment frequency, lead time for changes, change failure rate, and mean time to restore are tracked and reviewed regularly.

    dora · metrics · devops · measurement

  • Headcount Planning

    Engineering headcount requirements are modelled against roadmap commitments. Hiring plans are data-driven and submitted quarterly.

    hiring · planning · capacity · people

  • Tech Debt Tracking

    Technical debt is explicitly catalogued, prioritised, and allocated time within each sprint. Debt trends are visible to leadership.

    tech-debt · quality · sustainability

Optimised

  • Continuous Improvement System

    A formal improvement system (e.g., Kaizen events, OKR-linked experiments) ensures the engineering organisation learns and adapts faster than competitors.

    improvement · learning · okrs

  • Engineering Brand

    The engineering organisation has a strong external reputation that attracts top talent through open source, conference talks, and a compelling engineering blog.

    brand · open-source · community · recruiting

  • Platform Engineering

    An internal platform team provides self-service infrastructure, tooling, and golden paths that accelerate all product teams.

    platform · developer-experience · devops

  • Talent Density

    The organisation deliberately maintains high talent density through rigorous hiring, strong onboarding, and fast exits for poor fits.

    hiring · talent · performance

Interactive view

Other tech trees

Frequently Asked Questions

What is a technology tree?

A technology tree (tech tree) is a visual progression map inspired by strategy games like Age of Empires. It shows capabilities organised by domain (columns) and maturity level (rows), with dependency lines showing what must be achieved before advancing. Each node includes effort estimates, actionable steps, and links to relevant tools.

How do I use the tech tree for my organisation?

Select an organisational tree (like Engineering Org Maturity or Security & Compliance), then mark nodes as completed based on your current state. The tree automatically highlights what is available to work on next based on prerequisites. Click any available node to see the concrete steps required to achieve it.