Why seeing patterns in random events can backfire

The pigeon turns left. Food arrives. A management methodology is born. Random rewards are brilliant at manufacturing confident stories. Demand rises after the new campaign, so the creative receives a trophy; seasonality is unavailable for comment. Revenue recovers after a reporting ritual appears, so the ritual gains permanent residency. A salesperson uses a peculiar opening on one exceptional call and spends the next year forcing it upon innocent prospects.

Coincidence rarely has a narrator. The ritual does.

We need patterns to learn. The expensive mistake is promoting sequence directly to cause because the success was vivid and arrived wearing our name badge.

Try to kill the story before building a department around it. What would the result look like if the intervention did nothing? Compare a baseline. Repeat the test. Find occasions when the action happened without the reward and the reward arrived without the action. Keep the failed versions in the family album; winners are shameless editors of their childhood. Some rituals remain useful because they create confidence, rhythm or attention. Keep them on those honest terms. A lucky tie is cheap. A quarterly transformation programme based on three good Tuesdays is another matter.

When the feeder runs on a timer, more sophisticated pecking will not improve dinner. Refuse coincidence the budget. You do not have to refuse it the laugh.

Behavioural principles

Behavioural ideas at play in this post

Short, plain-English explanations of the principles behind this post, with links to related books and examples in the archive.