Developing a Technology Strategy

Regardless of a company’s size, the CTO is expected to outline a long-term technology strategy. This involves predicting and implementing the appropriate technology for the company’s long-term direction. It requires accurately anticipating future technology trends and understanding the company’s future requirements.

As you can see, it’s already a complex equation.

The biggest challenge often arises from the mismatch between current realities and long-term requirements. As the most experienced technical person in the company, you are responsible for finding the appropriate balance between these two demands.

Let’s consider an example.

The popularity of microservices architectures is indisputable today. This architecture is useful in domains where there are complex and distributed systems that require different levels of scalability on different modules, as well as overall flexibility and agility. Examples of such domains include e-commerce, finance, gaming, healthcare, and logistics.

However, it is important to note that microservice architecture is not a one-size-fits-all solution. It should be carefully evaluated based on the specific needs and requirements of the organization. It may not be a good fit for domains where there are simple and centralized systems that do not require as much scalability and agility.

Let’s look at another example.

Imagine that the average response time of an API endpoint is 400 milliseconds, which is not ideal but also not terrible considering the diverse data sources that the API retrieves from the backend. While it may be tempting to reduce this number to below 100 milliseconds, is this really the company’s top priority? It’s important to first understand the company’s real problems before making such a decision, as no company has unlimited resources. There may be other areas to focus on before addressing this technical debt.

On the other hand, there may be situations where financial or resource constraints are not significant concerns. For example, if the company has recently secured funding and certain services are expected to scale rapidly, investing in container orchestration architectures such as Serverless or Kubernetes immediately could be a plausible choice.

There is no one-size-fits-all answer, but the most important thing is to understand the company’s current realities and requirements and be able to silence the perfectionist engineer within you when necessary. Sometimes, it may be best to stick with a system that takes only an hour to fix rather than expending scarce resources on transitioning to a perfect microservice architecture that demands significant commitment for a small startup, risking financial strain. It’s an art that combines technical skills with business acumen, and you are the artist.

Resistance may come from team members who want to utilize the latest cutting edge technology. It’s also important to motivate these teams and appropriately update technologies that need to be replaced at the right time. Balancing these factors is another challenge that falls to you.

That being said, let’s briefly touch on cloud computing as it can provide a certain level of flexibility for experimentation.

Cloud computing can be an invaluable toolkit for developing a technology strategy that aligns with business goals. Its flexible pricing models can help companies manage costs and optimize resources, while enabling them to rapidly and efficiently scale their infrastructure in response to changing business needs. Additionally, it provides access to a wide range of tools and services that can foster innovation and enhance competitiveness.

Overall, I extensively rely on cloud computing when developing a strategy during times of significant uncertainty. While there may be instances where I don’t achieve optimal optimization of cloud services, the gained flexibility outweighs this trade-off.