What is an Antipattern?

An antipattern is a common solution to a problem that appears to be effective but actually creates more problems than it solves. It is essentially the opposite of a best practice or a design pattern.

Antipatterns can occur in various areas, including software development, business, management, and even personal life.

The term "antipattern" was first used in the 1990s as part of a movement to identify common software development practices that were counterproductive. The goal was to help developers avoid common mistakes and improve the quality of their code. Since then, the concept has been extended to other fields as well, and antipatterns are now recognized as a useful tool for identifying and addressing common problems.

Why it matters

Recognizing a recurring pattern helps teams address its causes instead of repeating an attractive but ineffective response.

Example

Imagine a manager responding to every missed deadline by requiring more detailed status reports. The reports initially make work feel more controlled, but preparing them takes time from delivery and people become reluctant to disclose uncertainty. Deadlines still slip, prompting yet more reporting. The team examines that recurring loop and discovers that overloaded specialists and competing priorities drive much of the delay. It replaces duplicate reports with a shared view of blocked work and reduces simultaneous commitments. Reporting is not inherently harmful; the antipattern is repeatedly applying this apparently reassuring response when it worsens the problem it is meant to solve.

Common misunderstanding

An antipattern is not simply a practice someone dislikes or a method that failed once. The same response can help under one set of conditions and cause harm under another. Labeling it too quickly can replace investigation with a debate about preferred methods.

Look for the recurring problem, the attractive response, and the counterproductive consequences. Explain why people keep choosing it and what a better response would require. Without understanding the conditions that sustain the pattern, removing the visible practice may leave the underlying problem intact.

Related terms

Organizational Heuristics · Retrospective · Systems Thinking

Explore questions like this with other practitioners through the Agile Community Network, nuAgility's free live community event and podcast.