Limitations of Basic Importance Methods
You'll learn when simple feature importance measures break down and mislead your interpretability efforts.
When Basic Importance Fails
While feature importance methods like MDI and linear coefficients are widely used, they carry critical blind spots that can produce misleading or incomplete interpretations.
The Core Problems
Interactions Go Undetected
Basic importance methods typically measure each feature's marginal contribution in isolation. When two features work together multiplicatively (e.g., temperature and humidity predicting storm risk), simple methods may show both as low-importance when individually weak, missing their powerful combined effect.
Non-Monotonic Relationships
Tree-based importance captures splits but obscures how a feature matters. A U-shaped relationship (where both very low and very high values increase the target) might show high importance without revealing this non-linear pattern. You know the feature matters, but not why or when.
Distribution Shifts Break Everything
Importance scores are computed on your training or validation distribution. If deployment data has different feature ranges or correlations, the rankings become unreliable. A feature ranked low because it rarely varied in training might become critical when encountering new ranges in production.
The Correlation Trap Revisited
Even with normalization, correlated features arbitrarily split importance. Worse, removing a "low importance" correlated feature can crash performance because it was redundant during training but provides crucial backup information when its partner is noisy.
Static Snapshots, Not Causal Stories
Basic importance tells you what the model uses, not what causes outcomes. High importance for "hospital visits" in a health model doesn't mean hospitals harm patients—it reflects correlation, not mechanism.
Key Takeaway:
Basic feature importance methods fail to capture interactions, hide non-linear patterns, break under distribution shift, and confuse correlation with causation—always validate with multiple interpretability approaches.