Case Study

Resolving Strategy Disagreements in a New Anti-Spam Project

Case context: Your team is starting a new email anti-spam project. The team has several competing ideas: building a custom spelling checker, implementing a sender reputation system, or using complex word-frequency analysis. The team does not have deep domain expertise in spam filtering and is arguing over which direction to design first.

Question: Based on the principles of rapid prototyping, what should the team do first to resolve this disagreement and identify the most promising direction?

Sample answer: The team should not spend time trying to design the perfect system at the outset. Instead, they should build and train a basic anti-spam system as quickly as possible, perhaps in just a few days. Even though this basic system will be far from the best system, they can examine how it functions and perform error analysis on its mistakes. This will quickly provide clues showing which direction is actually the most promising to invest their time in.

Key points:

  • Avoid trying to design the perfect system or argue over directions without data
  • Build and train a basic anti-spam system quickly (in a few days)
  • Use error analysis on the basic system to find clues identifying the most promising direction

Rubric: The answer should recommend building a basic, suboptimal system quickly (in a few days) instead of designing the perfect system first, and specify that error analysis on this basic system will provide the clues needed to choose the most promising direction.

0

1

Updated 2026-05-26

Contributors are:

Who are from:

Tags

Machine Learning

Deep Learning

Supervised Learning

Dive into Deep Learning @ D2L

Data Science

Machine Learning Strategy

Related