CTO has a few (up to three) developers; most of their time is spent on programming, but they’re already giving some direction and following up on developers.

The CTO spends their time on the same aspects as in Level 1, although Team alignment and follow-up starts to become part of their live.

• Programming This still takes up most of their time.
• Architecture Still not much time is spent here. Instead of a napkin, a whiteboard might be used, because now four people have to be able to look at it.
• Team alignment This is often done ad-hoc and operational. The CTO often defines tasks and assigns them to individual developers.
• C-level alignment Takes up a bit more time, because the CTO will have to keep the C-level team updated on the progress of the product.
• Time horizon A bit further in time. The CTO is not only looking at the current work that is being done, but is also preparing the next batch of work.
• Size of tech team Around three to four.
• Typical phase of the company The first idea has been tested and the company might have a few customers. The company is still looking for a problem-solution fit.

Main focus of a Level 2 CTO

• Building further on what was built as a Level 1 CTO. The general direction should be clear by now; the level 2 CTO is mainly expanding the existing product. Experiments still happen, but there’s also ‘known work’ that has to be done now.

Secondary attention points of a Level 2 CTO

• Start building a tech team. Be aware of motivation, team spirit, team culture.
• The Level 2 CTO is often the linchpin between C-suite alignment and tech team alignment.

The superpower of a Level 2 CTO

• A Level 2 CTO is able to switch between deep tech work, team work, and strategic work.

Back to the CTO Readiness Levels

Level 1