Abraham Maslow, 1966

“I suppose it is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail.”

Abraham Maslow wrote this warning in The Psychology of Science in 1966. It describes the tendency to let a familiar method define the problem, especially when professional training, incentives, or confidence are concentrated in one kind of tool. Tools shape attention. A sales team may see an awareness problem, engineers a feature problem, finance a cost problem, and data scientists a prediction problem. Each view may contain truth while still obscuring the system that produces the outcome. The business value of the line appears when it changes a real decision. It directs attention toward assumptions that routine can hide and invites a team to examine the system behind an outcome instead of treating the visible result as a complete explanation.

Before selecting a solution, teams can frame the problem from several stakeholder perspectives, list assumptions, and compare at least three intervention types. Inviting people with different expertise reduces the chance that convenience masquerades as diagnosis. Application therefore requires an explicit mechanism: what should people do differently, what signal should move, and when will the team examine the result? Writing those elements down turns general agreement into a testable management practice.

Using many tools is not automatically wise; unnecessary variety can create delay and incoherence. The goal is fit. A proven method should be reused when evidence supports it, but its limits and the conditions for switching approaches should be explicit. Context matters because an idea that improves one situation can create harm in another. Leaders need boundaries, dissent, representative evidence, and a way to correct course. Accountability cannot be delegated to the quotation or the tool used to implement it.

Generative AI is a remarkably flexible hammer. Organizations may apply it to tasks better solved by clearer policy, simpler forms, adequate staffing, direct conversation, or removal of the work. Starting with the human need prevents technology from becoming the definition of progress. A pre-project review can ask what evidence would show this is not a technology problem and which nontechnical option deserves a fair comparison before investment is approved. The review should preserve what was known when the choice was made, document what changed, and share the learning beyond one team. Repeated with discipline, that cycle converts a memorable sentence into better judgment rather than another short-lived management theme. It also makes the cost of assumptions visible, allowing future teams to reuse proven knowledge while recognizing the point at which a different customer, risk, or operating environment requires fresh testing.