Developing a Technical Strategy: First Key Questions

Clients often tell me they didn't know where to start when it came to building software. During our first few conversations, they often haven’t completed essential bits of thinking because they lacked guidance on what to consider. This is where a well-defined technical strategy becomes crucial.

A significant part of my role is to guide clients through the thinking process and ensure nothing is missed in developing their technical strategy. While the first call isn't the time to delve into a complete technical strategy, I have developed a list of the most useful questions to gain insight into their current status and determine the help they might need.

Here is the list of initial questions I cover in our first call to help shape a strong technical strategy:

  1. Is it clear why the software is being built?
  2. How advanced is the thinking about budget?
  3. Who will be using the software, and what do they need?
  4. Is there at least a rough end-to-end technical plan of what parts the software needs to have and who will build them?
  5. Who will own the task of looking after the software in the long term?

Is it clear why the software is being built?

Understanding the motivation behind building the software is fundamental. What event or condition prompted the need for this software? Typically, it is to solve a specific problem. Identifying this problem and how well it is understood helps define success and measure the project’s effectiveness.

How advanced is the thinking about budget?

Assessing the budget is a critical component of any technical strategy. Sometimes, clients have an idea of the project’s cost or their budget, while other times, they are still exploring these financial aspects.

Who will be using the software, and what do they need?

This question is crucial for understanding user requirements, which is a key part of a successful technical strategy. No software will succeed if it doesn’t meet the needs of its users.

Is there at least a rough end-to-end technical plan of what parts the software needs to have and who will build them?

It’s common for there to be no technical plan when I first engage with a project. However, having at least a rough plan can be beneficial. This includes understanding how teams will collaborate and how different parts of the system will interact, which are essential elements of a comprehensive technical strategy.

Who will own the task of looking after the software in the long term?

Long-term maintenance is a critical aspect of any technical strategy. This includes responsibilities like compliance and security updates. Understanding who will manage these tasks helps ensure the software remains effective and secure over time.

Conclusion: Establishing a Strong Technical Strategy

These initial questions are not exhaustive but are the ones I find most helpful during initial calls to guide a new client in the best direction. A well-crafted technical strategy is vital for the success of any software project. If you have a different set of questions that you believe should be included, please let me know.