False Analogy
Applying a pattern learned in one context to a superficially similar situation whose relevant properties differ.
Pattern recognition is what makes experience valuable — and it is also how experienced practitioners make their most confident mistakes.
The failure has a specific shape: the surface features match and the causal properties do not. A team that succeeded with microservices at a company with mature platform engineering and capability-aligned teams recommends microservices at a company with neither. The problem looks the same; the conditions that made the solution work are absent.
The habits that guard against it:
Name the conditions that made the pattern work, not just the pattern. "Event-driven decoupled our teams" is incomplete without "because they had genuinely different rates of change and a platform team owning the broker".
Look for the disanalogy deliberately. Ask what is different about this situation rather than what is similar, since the mind supplies similarity unprompted.
Weight recent and personal experience down. Availability bias means the last incident and the last company dominate, and neither is a representative sample.
Ask what would have to be true for the pattern to apply here, then check whether it is.
The productive form of pattern matching is therefore hypothesis rather than conclusion: "this resembles X, which suggests looking for Y" — a direction for investigation rather than an answer.