Here’s a short, engaging story that captures the essence of (as in the spirit of Cook, Campbell, and Shadish’s work, often summarized in guides like Quasi-Experimentation: A Guide to Design and Analysis ). Title: The Principal’s Predicament Dr. Lena Torres, a research consultant, faced a familiar problem. The school principal, Mr. Hartley, had just spent $50,000 on a new "MindGrow" reading software. He needed to know if it worked.

Hartley nodded. "So we keep the software, but we train Mr. Abel on it too."

"Exactly," Lena said. "And next time, if you can’t randomize, use a — give half the classes the software in Phase 1, the other half in Phase 2. Compare each against itself over time."

Hartley frowned. "So I should flip a coin? Randomly assign kids to software or no software?"

"Lena, look," Hartley said, tapping his desk. "I installed it in Ms. Chen’s third-grade class. She’s our best teacher. The other third-grade class, Mr. Abel’s, is using the old curriculum. After three months, I’ll compare their test scores. Simple, right?"

But to be rigorous, she added a and used Huber-White robust standard errors (because monthly scores from the same class aren’t independent — a key point from quasi-experimental guides).

Hartley laughed. "You quasi-people have a workaround for everything."