MISSION™ Stress Test

Standard status reports hide risk. This 2-minute diagnostic exposes it. Answer binary (Pass/Fail) to calculate your Project Risk Score.

SECTION 1: The Trust Test (The "Gut Check")
Would you go into a potentially career-threatening battle with the people sitting at this table? (Fatal Flaw Question)
SECTION 2: The Governance Gate (OSSICPOET™)

Assess the "Vital Few". There is no Amber. It is True or False.

Outcome: Can the team articulate specific business value in 30 seconds?
View Evidence Requirements (Must have all 3 to Pass)
  • Quantifiable Metric: A documented, financially or operationally quantifiable business value metric exists (e.g., "$4M OPEX reduction").
  • Team Alignment: Any core team member selected at random can state this primary value metric in under 30 seconds without referencing a slide deck.
  • Strategic Traceability: The project's targeted outcome maps directly and explicitly to one of the enterprise's top-level strategic priorities for the current fiscal year.
Sponsor: Does the Sponsor have "skin in the game" and make timely decisions?
View Evidence Requirements (Must have all 3 to Pass)
  • Skin in the Game: The Sponsor’s personal performance review or compensation is directly tied to the realization of the project's business case.
  • Decision Velocity: The Sponsor demonstrates a track record of making binding, unreversed decisions on escalated issues within 48 hours.
  • Active Roadblocking: The Sponsor actively clears political or resource bottlenecks across the organization rather than acting solely as a passive receiver of status updates.
Solution: Is the scope focused on the "Vital Few" (no complexity/bloat)?
View Evidence Requirements (Must have all 3 to Pass)
  • The "Do Not Do" List: A formally documented and enforced "out-of-scope" list exists, demonstrating a ruthless defense against scope creep and complexity bloat.
  • Vital Few Alignment: The architecture or process design directly satisfies the core requirements, with all non-critical "nice-to-haves" formally deferred to future, separate funding cycles.
  • Market Reality Check: End-users or target customers have physically validated the proposed solution via a prototype or pilot, not just via theoretical requirements sign-off.
Investment: Does the business case meet the mandatory ROI threshold?
View Evidence Requirements (Must have all 3 to Pass)
  • Hard ROI Proof: An approved, detailed business case exists that outlines hard ROI (verifiable revenue generation or hard cost elimination).
  • Fact-Based Contingency: The financial model includes a contingency budget calculated from historical organizational variance data, not an arbitrary percentage guess.
  • Realization Mechanism: An audit process and owner are already assigned to track and measure the actual financial benefits post-deployment.
Communication: Is bad news reported instantly? (Safe Haven culture)
View Evidence Requirements (Must have all 3 to Pass)
  • Demonstrated Safe Haven: There is a recent, verifiable instance where a team member raised a critical risk or bad news without facing blame or retaliation.
  • Unvarnished Risk Register: The risk log contains active, uncomfortable truths (e.g., "Vendor X is failing delivery," "Sponsor is disengaged") rather than sanitized, generic risks.
  • Red-First Reporting: Executive dashboards and status reports place "Red" and failing items at the very top of the agenda, rather than burying them in appendix slides.
Plan: Is the roadmap fact-based, with releases under 3 months?
View Evidence Requirements (Must have all 3 to Pass)
  • Data-Driven Scheduling: The master schedule and estimates are built upon historical team velocity or actual capacity data, not reverse-engineered from an arbitrary management deadline.
  • Short Time-to-Value: The project roadmap guarantees that the first usable deliverable or capability will be in the hands of the business within 90 days or less.
  • Signed Dependencies: All critical path dependencies (both internal teams and external vendors) are explicitly mapped, agreed upon, and physically signed off by the dependency owners.
Organization: Do we have the talent and bandwidth to execute?
View Evidence Requirements (Must have all 3 to Pass)
  • Dedicated Bandwidth: Key leadership and execution roles are filled by named individuals allocated at least 80% to this project, not fragmented across multiple competing initiatives.
  • Generalizing Specialists: The core team structure explicitly includes versatile "agile thinkers" capable of bridging the gap between business strategy and technical execution, avoiding the "specialist-only" silo trap.
  • Contingency Talent: Backfill plans or cross-trained contingency resources are actively identified for all single points of failure (key personnel risk).
Execution: Are Estimates to Complete (ETCs) rigorous and realistic?
View Evidence Requirements (Must have all 3 to Pass)
  • Dynamic ETCs: Estimates to Complete (ETC) are recalculated at the end of every reporting cycle based on actual performance and remaining work, not just subtracting hours burned from the original budget.
  • Objective "Done" Criteria: A clear, uncompromising definition of "Done" is enforced for every task, preventing the illusion of tasks being "90% complete" indefinitely.
  • Continuous Quality Assurance: Testing, QA, and business validation are integrated continuously into the execution cycles, rather than pushed to a massive, high-risk phase at the end of the project.
Technology: Does it meet standards to minimize Total Cost of Ownership?
View Evidence Requirements (Must have all 3 to Pass)
  • Architecture Alignment: The technology choice explicitly aligns with the enterprise architecture roadmap, preventing isolated "shadow IT" or the accumulation of new technical debt.
  • Vital Few Vetting: Vendor contracts and software selections were competitively scored against this project's specific "Vital Few" requirements, not generic feature lists or vendor hype.
  • Comprehensive TCO: The financial model accounts for Total Cost of Ownership (TCO), including long-term licensing, operational support, integration maintenance, and upgrade paths, not just initial implementation costs.

Your Project Risk Score

0
Verdict

User Documentation: Scoring & Methodology

Design Philosophy: Standard project reporting uses a Traffic Light system (Green, Amber, Red). This tool utilizes a Binary Constraint (Pass/Fail) to eliminate the "Amber" hiding place and expose the "Watermelon" effect (projects that look green on paper but are failing in reality).

Evidence Requirements: To "Pass" a pillar, all 3 specific evidentiary requirements documented within the dropdown must be demonstrably met. There is no partial credit.

The Scoring System (0-100 Points): The tool uses a Penalty System. A perfectly healthy project scores 0. Points are added based on the severity of the failed pillar:

Interpreting Your Verdict:
© 2026, Prosultant.com, Inc.