Technical leadership without a CTO

Nobody steers the technical decisions

In a company without a CTO, an architecture decision gets postponed, then made by whoever is at the keyboard that day. The system grows by accumulation, and the next decision is harder, because the cost isn’t translated into terms the business understands. So decisions land on the CEO’s desk, and the CEO settles them without the tools to do so, while those in the team who could steer them work alone.

Book a call

Does this sound familiar?

  • Architecture decisions are put off, or taken case by case by the people working on that part.
  • The CEO or founder ends up settling technical arguments they have no way to assess.
  • Each project has picked its own tools and libraries, and the reasons have been lost.
  • The team’s senior people make good decisions about the code, but without knowing which business goals those choices should serve.
  • The state of the system is unclear, and so is what it would cost to change it.

Why do technical decisions go without direction?

While the team is small, technical decisions get made in conversation. As the company grows, choices taken case by case pile up in the system, the system becomes hard to explain to the business, and the next decisions are again taken case by case.

  1. Decisions are made case by case

    Without shared criteria, every architecture choice depends on who faces it and when, and the reasoning isn’t written down. Senior developers working inside the team support the people who are deciding and make the criteria for choosing explicit.

  2. The system has grown by accumulation

    Different tools for every project, debt nobody has measured, parts people touch with trepidation. Without an overall view, the system spreads with no direction. A map of the critical areas, ranked by how much each one slows the changes that matter to the business, is the place to start from.

  3. Business and engineering have no common language

    When technical choices aren’t translated into costs and timelines, management decides on whichever opinion is argued best and the team decides without knowing the priorities. A page for each choice, with the options, the cost of each and what is given up, gives management and the team the same starting point.

  4. The future tech lead grows alone

    Often there is already someone in the team who could become the technical reference point, but nobody has ever supported them in that role. Working with a tech lead on the technical practices they need to bring to their group, on everyday code, grows a leader who stays in the company.

What changes when technical decisions have direction

Architecture decisions are made in time, using criteria the team knows and shares. The system grows with a sense of direction, because each new choice is measured against those already made.

For every architecture choice, the CEO receives the options from the team with their costs and timelines, and decides on those. Inside the team, the tech lead we work alongside takes on a growing share of these decisions.

Bring us your pending technical decisions

It helps if both the business decision-maker and someone who knows the code join the call. We start with the pending decisions, and with embedding senior people in the team through Embedded Teams, as one possible source of direction.

We use your data to respond to your request. Read our Privacy Policy.