liveBook · Manning

Cause analysis

Cause analysis is a systematic investigation of the underlying factors that produced a problem, failure, incident, or other outcome.

How 4 Manning books explain it

Build High Value Software Systems

A systematic process for identifying the underlying causes of a problem or failure rather than addressing only its symptoms.

How it is used
Investigates recurring or costly software failures before choosing changes that address their causes rather than their symptoms.
How deep it goes
Works through scoping, cause chains, blind-spot checks, prioritization, and fix-prevent-detect countermeasures rather than stopping at a diagnosis.
Examples
Uses an EU notification migration, an undersized monetary column, and a flaky test masked by retries.
What you can do after
Practice/perform a cause investigation, test whether a proposed fix prevents recurrence, and document countermeasures for implementation.

Read how Build High Value Software Systems explains cause analysis →

Think Like a Software Engineering Manager

Root-cause analysis is a systematic method for identifying the underlying factors that produced a problem or failure.

How it is used
Supports decisions about employee underperformance and learning from production incidents by investigating what produced the visible problem.
How deep it goes
Provides performance indicators and possible causes, plus an iterative 5 Whys incident example; stops short of a formal investigation protocol.
Examples
Uses a disengaged engineer missing deadlines and a system crash traced through database disk exhaustion to accumulating backup logs.
What you can do after
Practice/perform it by checking plausible causes without bias, asking successive why questions, and turning findings into feedback or preventive actions.

Read how Think Like a Software Engineering Manager explains cause analysis →

Data-Driven Cybersecurity

A systematic technique for identifying the underlying reasons an adverse event occurred so that its problems can be addressed and recurrence prevented.

How it is used
Identifies underlying reasons for adverse events so incident teams can correct weaknesses and prevent recurrence.
How deep it goes
Outlines data collection, pattern analysis, the Five Whys, cause identification, and corrective action without prescribing a specific investigation tool.
Examples
Traces a financial institution’s breach from phishing and stolen credentials to missing multifactor authentication and targeted fixes.
What you can do after
Diagnose/debug with it by identifying an incident’s primary cause and choosing corrective actions aimed at preventing recurrence.

Read how Data-Driven Cybersecurity explains cause analysis →

Automating API Delivery

Root-cause analysis is a systematic examination of underlying causes that explains the relationship between an observed effect and its cause.

How it is used
Uses underlying-cause analysis to prevent recurring APIOps workflow problems and guide improvement work.
How deep it goes
Explains iterative questioning, causal hypotheses, validation, and testing, but defers detailed Ishikawa-diagram treatment.
Examples
Uses an Acme API design-change delay, a root-cause tree, and an A3 improvement report as concrete artifacts.
What you can do after
Diagnose recurring process problems, formulate causal theories, and select countermeasures for small-scale testing.

Read how Automating API Delivery explains cause analysis →

Also covered in

What to know first

Related concepts

Questions about cause analysis

What is cause analysis?

Cause analysis is a systematic investigation of the underlying factors that produced a problem, failure, incident, or other outcome.

Which Manning books explain cause analysis?

Build High Value Software Systems, Think Like a Software Engineering Manager, Data-Driven Cybersecurity and Automating API Delivery.

What should I know before learning cause analysis?

Manning books that teach cause analysis usually introduce log, A3 report, causation and fishbone diagram first.

What is the difference between cause analysis and attribution?

Cause analysis is a systematic investigation of the underlying factors that produced a problem, failure, incident, or other outcome. Attribution is the association of content, contributions, decisions, or outcomes with their sources, creators, or causes.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.