The project deadline was announced before feasibility work. How do I respond?

Unvalidated deadline

Treat the announced date as a constraint to test, not a reliable forecast. Develop a minimum feasible scope and show the trade-offs necessary to meet it.

What to do now

  1. Identify the reason for the date
  2. Estimate the essential delivery path
  3. Identify scope and capacity options
  4. Ask the sponsor to select a feasible commitment
Recommended action flow for unvalidated deadline: Identify the reason for the date then Estimate the essential delivery path then Identify scope and capacity options then Ask the sponsor to select a feasible commitment. Escalate when no combination of safe scope and available capacity meets the date.

When to escalate

Escalate when

No combination of safe scope and available capacity meets the date.

Who decides

The accountable sponsor

Example

A conference website launches registration first while less urgent content moves to a later release.

Mistake to avoid

Making the schedule look feasible by deleting testing.

Prevent a repeat

At each stage decision, check that the expected outcome, owner and justification remain valid.

Suggested ApprovedFlow setup

  • Projects
  • Documents
  • Approvals

Keep the decision brief with the project and request a recorded sponsor decision before the next commitment. See the platform

Related cases

Practice references