liveBook · Manning

Discovery

As explained in Think Like a CTO

A discovery phase is a structured period of investigation in which systems, capabilities, problems, and improvement opportunities are examined before major execution begins.

Discovery is a structured investigation of systems, projects, team capability, and client experience before committing to major initiatives. It combines organizational orientation with direct inspection of how work and technology actually operate. section 1.4.1

A practical discovery phase typically involves:

  • Reviewing planned and active projects to understand priorities, ownership, decision-making, and appetite for initiative size. section 1.4.1
  • Inspecting source code, data stores, servers, and infrastructure to compare perceived capability with execution reality. section 1.4.1
  • Recording capability gaps, missing expertise, absent support contracts, easy wins, and quick fixes. section 1.4.1
  • Seeking outside perspectives from established clients before shaping short-term plans and longer-term direction. section 1.4.1

From inspection to adjustment

A technology leader may inspect source code, data stores, and infrastructure, discover that a critical system lacks in-house expertise or contractual support, record quick fixes, and adjust project scope accordingly. section 1.4.1

How Think Like a CTO covers it

How deep it goes
Descends from project review to direct inspection of code, data, servers, and infrastructure, then stops short of major execution.
Examples
Uses source-code reviews, data-store reviews, infrastructure checks, client visits, quick-fix lists, and project-scope adjustments.
What it assumes
Assumes access to projects, systems, infrastructure, and clients while teaching investigation through progressively deeper organizational inquiry.
What you can do after
Diagnose capability and operational gaps, identify quick wins, formulate plans, and adjust initiatives using observed evidence.
How it connects
Connects projects, systems, infrastructure, data stores, team capability, clients, support contracts, and execution.

Also explained in

Compare how 4 books explain discovery →

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.