liveBook · Manning

Cognitive bias

A cognitive bias is a systematic tendency in human perception, judgment, or reasoning that can distort how information is evaluated and decisions are made.

How 3 Manning books explain it

Collaborative Software Design: How to facilitate domain modeling decisions

A cognitive bias is a systematic tendency in human judgment or reasoning that can distort perception and decision-making.

How it is used
Guides facilitators in recognizing and managing judgment patterns during collaborative modeling and software design decisions.
How deep it goes
Defines bias as systematic mental shortcuts, then demonstrates anchoring, group effects, visualization, and optional nudges.
Examples
Uses driving decisions, pivotal-event selection, subgroup Example Mapping, and a cinema-seating template to expose bias.
What you can do after
Apply it by observing bias, visualizing discussion, and offering optional nudges that help groups reconsider decisions.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains cognitive bias →

Demand Forecasting Best Practices

A cognitive bias is a systematic deviation in judgment caused by mental shortcuts, assumptions, or other distortions in human reasoning.

How it is used
Improves judgmental demand forecasting by identifying distortions in forecast reviews and adjustments.
How deep it goes
Defines several biases and gives forecasting examples, then details process safeguards rather than psychological mechanisms.
Examples
Uses a wheel-of-fortune estimate, a 20% sales claim, product-launch optimism, and positive versus negative forecast adjustments.
What you can do after
Diagnose/debug with it by spotting biased adjustments and structuring independent, assumption-based forecast reviews.

Read how Demand Forecasting Best Practices explains cognitive bias →

Cyber Threat Hunting

A systematic pattern in which human judgment or perception deviates from rational evaluation because of mental shortcuts, experiences, or preferences.

How it is used
Guides threat hunters in designing and conducting hunts without letting experience or preferences distort hypothesis testing.
How deep it goes
Defines four biases and demonstrates confirmation-bias mitigation through an osquery pivot, but does not provide a broader debiasing framework.
Examples
Uses Dropbox connections, process listings, encoded PowerShell, command decoding, and genuine-file hash comparison as investigation artifacts.
What you can do after
Diagnose/debug with osquery by challenging initial hypotheses, pivoting from process names to sockets, and examining contradictory evidence.

Read how Cyber Threat Hunting explains cognitive bias →

Related concepts

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.