Classification Applications › Limitations and Practical Considerations

Text classification systems, despite their maturity as a technology, carry persistent limitations that shape their real-world reliability.

Distribution shift between training and deployment is the central challenge. A sentiment classifier trained on Amazon product reviews degrades when deployed to Twitter, where sentence fragments, slang, and sarcasm are far more common. An intent classifier trained on synthetic data generated by developers degrades when deployed to real users who phrase requests in ways the training set never anticipated. No amount of in-distribution performance optimization prepares a model for out-of-distribution queries. The only reliable mitigation is to collect real deployment data, monitor for performance drops, and retrain or adapt regularly.

The monitoring infrastructure for distribution shift is often underinvested. Many teams deploy a model, measure its performance on a test set at launch, and then consider the evaluation done. In practice, the query distribution shifts continuously as user behavior evolves, new topics emerge, and the product changes. Setting up a pipeline that samples a fraction of production traffic for human labeling, then running weekly or monthly model evaluations against those labeled samples, is the operational practice that turns a point-in-time evaluation into a continuous quality signal.

Label quality limits ceiling performance. The theoretical upper bound for a classifier is the agreement rate among human annotators on the same task. For fine-grained categories, that rate can be surprisingly low: inter-annotator agreement on fine-grained emotion classification often falls below 0.5 kappa. A model trained on such data cannot exceed human agreement in any meaningful sense. Investing in annotation quality, including clear label definitions, annotator training, and adjudication processes for disagreements, often produces larger gains than switching to a larger model.

Clear label definitions are particularly important and often neglected. "What distinguishes a Neutral tweet from a Positive one?" is a question that annotators will answer differently without explicit guidance. A two-page annotation guide with ten examples per category boundary, explaining common edge cases and how to handle them, can increase inter-annotator kappa from 0.55 to 0.75 for the same annotators and task. That improvement in label quality translates directly into a better model.

Zero-shot capabilities do not eliminate the need for evaluation. It is tempting to deploy a zero-shot classifier without evaluation because it requires no labeled data. But zero-shot performance varies dramatically across tasks, label sets, and domains. A zero-shot classifier that works well on news topics may fail badly on specialized medical categories. Before any deployment, you should construct at least a small evaluation set (100-200 examples covering all categories, including edge cases and OOS examples) and measure actual performance rather than relying on benchmark reports from different task configurations.

Multilingual classification presents distinct challenges. Most high-performing classifiers are trained primarily on English text. Cross-lingual transfer via multilingual models (mBERT, XLM-RoBERTa) has improved significantly, but performance for low-resource languages remains substantially below English performance, and the gap widens for fine-grained categories not well-represented in the pre-training corpus. Applications serving multilingual audiences should explicitly evaluate across all supported languages and plan for language-specific fine-tuning where accuracy gaps are unacceptable.

Temporal drift deserves particular attention in applications like social media monitoring and news classification. Topics evolve: "AI" in 2015 referred primarily to academic research; by 2023 it was a central business and political topic. Slang evolves: terms that express strong positive sentiment in one year can become ironic or neutral in the next. A classifier deployed without retraining will gradually drift away from the current distribution of language use, and the drift may be slow enough that no single evaluation catches the degradation. Periodic re-evaluation on fresh data, even a small amount, is the primary defense against temporal drift.

As we will see in the upcoming chapter on Conversational AI, intent detection is just one component of a conversational system. Handling multi-turn context, managing dialogue state, and generating appropriate responses introduce additional layers of complexity beyond the classification task itself.