THE FALLBACK

I acknowledge the timeline constraint directly with stakeholders. Rather than arguing the deadline is unrealistic, I reframe the problem: What's the actual goal here? Often deadlines aren't about the date—they're about unblocking something downstream. I propose alternatives: a phased delivery where core functionality ships on time and refinements follow, or identifying which quality standards are truly non-negotiable versus nice-to-have. I might suggest parallel workstreams or external resources. If corners must be cut, I make that trade-off explicit—"We can hit Tuesday if we accept X risk"—so decision-makers choose consciously rather than discovering problems later. The obstacle wasn't really the deadline; it was misaligned expectations.

I acknowledge the impossible deadline and work backward from it. First, I identify what *can* realistically be delivered within the timeframe—a partial solution, a prototype, or a clearly scoped MVP. I communicate this gap transparently to stakeholders, explaining what's achievable versus what isn't. My second plan is ready: if the deadline is truly non-negotiable, I propose a phased approach—deliver the core 60% on time, then complete the remainder in the following phase. This gives leadership options rather than forcing a false choice between perfection and failure. I never pretend the impossible is possible.