If a project is failing, what is a recommended first step?

• A. Dismiss the team and start over with a new crew.
• B. Secretly adjust milestones without informing stakeholders.
• C. Reassess root causes, pivot plan, reallocate resources, communicate honestly with stakeholders, implement corrective actions.
• D. Increase scope to compensate.

Answer: (C)

When a project is failing, the priority is to diagnose the problem and respond with coordinated, visible actions. The best approach is to reassess the root causes—gather data, analyze what isn’t working, and identify the real drivers of trouble rather than jumping to quick fixes. From there, pivot the plan as needed, reallocate resources to the areas with the greatest impact, and implement corrective actions. Central to this is communicating honestly with stakeholders: share what you’ve found, what you’ll change, and why, so everyone stays aligned and engaged in the recovery.

This approach is superior because it addresses the underlying issues directly instead of masking symptoms. Dismissing the team ignores potential internal problems and loses momentum. Secretly adjusting milestones bypasses governance and damages trust. Increasing scope while problems persist typically adds more complexity and risk. Transparent analysis and corrective action lay the groundwork for a real recovery.