What is behavioral change?

Example: A software engineer notices that every time she receives critical feedback on a pull request, she spends 45 minutes crafting a defensive response, then deletes it, then rewrites a neutral reply, then feels drained for the rest of the afternoon. She has named this pattern (Name your patterns): 'the defense-rewrite-crash cycle.' But naming it did not stop it. The next critical review arrives. She notices the familiar activation — the heat in her chest, the mental rehearsal of counterarguments. And this time, because she has recognized the pattern before it completes, she has a choice she did not have when the pattern was invisible: she can follow the cycle, or she can do something else. She sets a five-minute timer, writes three factual questions about the review, posts them, and moves to her next task. The cycle did not run. Not because it disappeared — the urge was still there — but because recognition created a decision point that automaticity had previously overridden.

This concept is part of Pattern Recognition in the How to Think curriculum.