Why a CTO Translates Business Goals for Developers: Tech Leadership Demystified

About this episode

Tech leadership is more than just writing code and building systems. In the latest episode of Scaling Technology, Stephan Schulze (A11) and Andreas Stryz (FINN) share their experiences from the reality of tech scaling – without marketing fluff, but with practical insights.

Technology must serve business, not the other way around

The biggest mistake tech teams can make? "Engineering for the sake of engineering." Both experts agree: technology is not an end in itself, but must always serve business objectives. The art lies in translating these business goals for developers so they understand why certain technical decisions are made.

Finding the right balance between speed and quality is one of the most critical tasks for CTOs. It's not about always building the perfect solution, but the right solution at the right time.

Monolith vs. Microservices: Timing is everything

A particularly interesting point of discussion: When should you use microservices and when is a monolith the better choice? The answer is less technical than expected – it heavily depends on the company's maturity and specific requirements.

Premature optimization is identified as a real "startup killer." Many teams build complex architectures for problems they don't even have yet. The deployment pipeline is mentioned as an important metric – it shows how quickly teams can respond to changes.

Mastering critical growth phases

Particularly insightful are the findings about different growth phases. The transition from 20 to 40 employees is identified as a particularly critical phase. This is often where it's decided whether a startup reaches the next level or fails.

"10x thinking" plays an important role here: tech teams must not only plan for the current state but prepare for explosive growth. At the same time, this preparation must not lead to overengineering.

The right hiring strategy for tech teams

Experience is crucial – especially in rapidly growing teams. Both experts emphasize how important it is to find experienced developers who have already mastered similar scaling challenges. The "death of the startup" threatens when techies without business understanding make important decisions.

Make or Buy: "We buy commodities, we build assets"

A practical guide for one of the most common decisions in tech teams: Should you develop a solution yourself or buy it? The rule of thumb "We buy commodities, we build assets" provides clear guidance. At the same time, the importance of negotiation skills for techies is emphasized – an often overlooked aspect.

Tech debt: Not always bad

The discussion about tech debt is also interesting. Contrary to widespread opinion, debt is not inherently bad – it can be a conscious instrument to move forward faster. The art lies in consciously taking it on and strategically paying it down.

Feature sales and sales promises

Another important point: dealing with sales promises. When sales teams sell features that don't exist yet, tensions often arise between sales and development. This requires clear processes and communication.

Vision, strategy, and org chart

The discussion about vision and strategy shows: without clear direction, even the best tech teams cannot be successful. The organizational structure must follow strategy, not the other way around.

The most important insight after five years of scaling experience: tech leadership means translating business goals into technical decisions while always keeping sight of the big picture.