An interview question about optimizing a 5-minute report generation process reveals a fundamental shift in thinking: the solution isn't making the code faster, but redesigning the system to be asynchronous. Instead of blocking users with synchronous requests, the better approach uses background workers, job queues, and notifications to keep the UI responsive while processing happens independently. This architectural change improves user experience, enables fault tolerance with automatic retries, and allows the system to scale under load without holding open connections or locking up resources.