liveBook · Manning

Vision pillar

As explained in Think Like a CTO

A major foundational capability or technology component on which an organization's vision and execution depend.

A vision pillar is a major capability or technology component that supports executing an organizational vision. Strong pillars provide a stable foundation while allowing individual components to be replaced without destabilizing the whole system. section 3.4.2

Identify pillars by focusing on foundational services rather than implementation details:

  • Name the large capability the vision depends on, such as secure, scalable API access or high-volume data storage. section 3.4.2
  • Describe the method broadly enough to preserve implementation choice; HTTP REST with JWT narrows the approach without prescribing a language or framework. section 3.4.2
  • Prefer areas that can be outsourced or consumed through frameworks, libraries, or managed services, reducing operational housekeeping. section 3.4.2
  • Watch each pillar’s evolution and investigate major shifts with a small, focused splinter team before changing direction. section 3.4.3
  • Treat changes to foundational pieces differently from routine framework or language changes, which may be disruptive without being pillars. section 3.4.3

API and data foundations

An API-driven vision may depend on a secure, scalable endpoint mechanism, such as HTTP REST with JWT. A data-intensive vision may depend on a data lake that accepts varied data and postpones transformation decisions; AWS S3 is offered as a starting point. section 3.4.2

Figure 3.7 Pillars of your vision

Use the figure to map the foundational components supporting a vision and inspect how they function together. section 3.4.2

How Think Like a CTO covers it

How deep it goes
Defines pillars, gives API and data examples, and adds monitoring guidance while stopping short of implementation detail.
Examples
Uses REST endpoints with JWT, data lakes, AWS S3, databases-as-a-service, and cloud infrastructure as concrete illustrations.
What it assumes
Assumes an organizational vision and introduces how to identify the capabilities required to execute it.
What you can do after
Evaluate foundational dependencies, monitor their maturity, and investigate major shifts before pivoting.
How it connects
Connects vision pillars with API architecture, data lakes, cloud computing, commoditization, managed services, and organizational change.

Related concepts

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.