How deeply does Think Like a CTO cover autonomy?

Defines autonomy through three decision buckets and communication expectations, but stops short of universal thresholds.

Autonomy

As explained in Think Like a CTO

Autonomy is the authority of a person or team to make decisions and handle work independently within defined boundaries.

Autonomy gives teams authority to handle work independently while preserving coordination, visibility, and clear boundaries for management involvement. section 6.4 section 6.4.1

Define autonomy with three practical decision categories:

Handle internally: routine execution, internal processes, one-on-ones, time off, and ordinary project work. section 6.4.1
Keep management informed: client problems, production issues, security concerns, team-member problems, timelines, and updates. section 6.4.1
Require a decision: senior hiring interviews, termination considerations, tool purchases, cross-team changes, and technology changes. section 6.4.1

Apply common rules across teams, then adjust the detail for each team’s role and manager experience. Visibility matters most for high-impact problems: report client disaffection and security concerns immediately, and acknowledge messages so serious issues are not discovered elsewhere. section 6.4.1

The no-update update

When a highly visible problem has no resolution yet, send a status message explaining that work continues. Repeating this update every 30 or 60 minutes, depending on urgency, prevents silence from becoming a second problem. section 6.4.1

Table 6.2 Rules of engagement (view table figure)

No reporting required	Keeping you informed	Decision required
Interviewing potential candidates	Any problem or issue concerning a client	Final interview of top candidates under review
Internal processes pertinent to the team execution	Any production problem	HR consultation or termination considerations
Team one-on-one meetings; PTO management	Security concerns or issues	Purchase or licensing of tools
Project execution	Changes in how the team interacts with other teams Any problems with individual team members Timelines; updates	Change of technology or tools

Use the rules-of-engagement table to classify team activities by internal handling, management awareness, or required decision. section 6.4.1

How Think Like a CTO covers it

liveBook manning.com

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

Also explained in

liveBook manning.com

Effective Platform EngineeringAutonomy is the ability of developers or teams to work and make decisions independently within their responsibilities.
liveBook manning.com

AI Agents in Action, Second EditionAutonomy is the capacity of a system to select and perform actions without requiring a separate user decision for each step.
liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureThe ability of a product, team, or organizational unit to make decisions and operate independently.
liveBook manning.com

Think Like a Software Engineering ManagerAutonomy is the capacity of an individual or team to make decisions and act without continuous direction from a leader.
liveBook manning.com

Build an AI Agent (From Scratch)Autonomy is the capacity of a system to determine and continue its own actions without a predetermined sequence controlling every step.
liveBook manning.com

Lead Developer Career GuideThe ability and authority to act, make decisions, and solve problems independently.
liveBook manning.com

Collaborative Software Design: How to facilitate domain modeling decisionsAutonomy is the ability of a team to make decisions and progress independently without requiring continual alignment or approval from other teams.
liveBook manning.com

Software Testing with Generative AIThe capacity of a software system to select and perform actions toward a goal without an explicitly ordered sequence being prescribed for every action.

Compare how 9 books explain autonomy →

Related concepts

microservice architectureproduced by · Microservice architecture is a software architectural style that organizes an application as independently deployable services with focused responsibilities that communicate through defined interfaces.
intrinsic motivationpart of · Intrinsic motivation is motivation arising from interest, enjoyment, satisfaction, or challenge inherent in an activity rather than from external rewards or pressures.
human-in-the-loopcontrasts with · Human-in-the-loop is a system pattern in which people provide input, judgment, review, or intervention within an automated process.
stream-aligned teamused by · A stream-aligned team is a long-lived team organized around a continuous flow of customer or business value, with responsibility for delivering and maintaining its product or service.

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.