The business needs a proof-of-concept in 48 hours for a feature that normally takes months. How do you architect that so it’s fast but doesn't become a permanent technical debt nightmare?

General expectation: Engineers tie technical debt directly to Revenue, Risk, or Latency. They speak like a business owner (e.g., "If we don't fix this Kafka lag, we lose 5% of our transaction volume during peak hours") or share a business justification