How deeply does Think Like a CTO cover technical strategy?

Defines responsibility boundaries and organizational variations, but does not develop detailed planning methods or technical implementation.

Technical strategy

As explained in Think Like a CTO

A set of technology choices, priorities, and plans that guides a company's technical development and execution.

Technical strategy guides a company’s product-focused technology choices, priorities, and execution. The CTO commonly owns this responsibility, serving client needs through the core platform, enterprise, or product line rather than back-office IT. section 1.1

Define the responsibility in relation to organizational context:

Separate front-office product technology from back-office systems such as desktop computers, mail servers, phones, and printers. section 1.1
Expect reporting lines to vary: the CTO usually reports to the CEO, but may report to the CFO, COO, or CIO. section 1.1
Adapt the scope to company size; startups may combine strategic leadership with operational tasks, while established companies may lack holistic technical ownership. section 1.1

A missing strategic owner

An established small or medium-sized company may have development, support, and systems teams without anyone managing technical strategy as a holistic initiative. Recognizing this gap can support a case for filling the role. section 1.1

How Think Like a CTO covers it

liveBook manning.com

Read Think Like a CTO on liveBook Get the book at manning.com

Related concepts

guardrailconfigures · A guardrail is a constraint, safeguard, or control that limits actions or behavior to reduce risk and keep a system or process within acceptable bounds.
decision makingconfigures · Decision making is the process of selecting an action, outcome, or judgment from available alternatives based on information, objectives, or constraints.
model architectureconfigures · The structural organization of a computational system’s components, relationships, and operations that determines how it processes information or behaves.

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.