01
Establish the facts
Separate verified signals, stakeholder claims, assumptions, missing evidence and unresolved questions.
PROJECT RECOVERY
Project Rescue
A structured recovery workflow for struggling software and SaaS projects.
Project Rescue helps turn a messy, at-risk initiative into an evidence-based diagnosis, a prioritized recovery plan, and clear decision points—without forcing one delivery methodology.
What it does
What it is built to solve
When a project is slipping, the visible symptom—missed dates, bugs, stakeholder conflict, scope churn—may not be the real cause. Project Rescue separates facts from assumptions, identifies the strongest risk drivers, and converts uncertainty into a practical recovery path.
Workflow
From ambiguity to the next move.
02
Diagnose the risk system
Look across delivery, scope, dependencies, ownership, communication, quality, process and customer-demand evidence.
03
Prioritize root causes
Distinguish primary drivers from secondary symptoms and rank issues by impact, urgency and reversibility.
04
Choose a recovery mode
Stabilize, re-scope, re-plan, validate demand, pause investment or establish a different execution path based on the evidence.
05
Build the rescue plan
Turn the diagnosis into owners, actions, decision gates, checkpoints and evidence needed for the next review.
Typical outputs
Turn analysis into usable outputs
- Executive project diagnosis
- Risk map and root-cause hypotheses
- Facts / assumptions / evidence gaps
- Prioritized recovery actions
- Decision gates and review cadence
- Clear ownership and next-step checkpoints
Designed for
Who can use it
- Technical Program Managers
- Product & Engineering leaders
- Founders and delivery leads
- Cross-functional teams inheriting an at-risk initiative
Principles
Design principles & boundaries
- Built primarily for software, SaaS and technology projects.
- Methodology-neutral: adapts to Scrum, Kanban, Waterfall or hybrid delivery.
- Can surface weak customer urgency or weak demand evidence when execution is not the core problem.
- Focuses on observable behavior, incentives, ownership and communication—not personality judgments.
- Supports project and investment decisions; it is not a tool for deciding which specific employees should be terminated.
Public release
Browse my published AI Skills
You can browse my publicly released AI Skills through my Agensi creator and Capafy publisher profiles.