Why do deployers apply the same tool to every problem?

Because knowing a tool shapes what you look at. Even experts keep looking at the answer they already have while they say they are searching for a better one. So the safeguard cannot be the deployer’s attitude. It has to be a rule, set before anything is configured.

How it works

Whoever masters a tool sees problems shaped like it: the next module, the standard configuration, one more dashboard. The habit is old, and it is not vanity. A smith without a hammer is a tourist. Abraham Kaplan called it the law of the instrument in 1964, picturing a small boy with a hammer; two years later Abraham Maslow added the nail.

That is why a promise to keep an open mind does not help much. A deployer who means it still sees the floor through the tool, because that is what knowing a tool means. I carry three hammers myself: floor experience, the incentive model and the guardrail.

Two questions work better than a promise. Before kickoff: what will you measure before you cut? And when every fix is the next module: what would you do if you could not use your tool?

Evidence

In a laboratory study by Merim Bilalić, Peter McLeod and Fernand Gobet, chess players who had found one solution said they were looking for a better one, while their eyes kept going back to the one they had.

What this does not prove

Sources

From the field notes The Smith and the Tailor · PDF, 10 pages