How the Project Diagnostic works
The Project Diagnostic gathers anonymous input from project stakeholders, compares confidence across role groups, scores 15 key delivery dimensions, and produces a structured diagnostic report showing delivery health, risk signals, role confidence gaps and recommended management focus. This is not a survey tool and not an AI summary — it is a structured diagnostic designed to surface what status reports often miss.
Reports are strongest when responses include sponsor, PM / PMO and delivery team perspectives.
Acme Corporation — Technology Transformation Program
Project Diagnostic — 7 June 2026
Verdict
This project is recoverable, but not low-risk. The main concern is not budget or sponsorship — it is the gap between leadership confidence and what those closest to delivery are reporting, particularly around risk control, decision flow and delivery confidence.
Executive summary
This project does not present as failing, but the response pattern indicates a delivery environment where confidence is uneven and several control mechanisms are under pressure. The strongest signals appear across the operating system of the project — decision flow, risk control, delivery confidence and role accountability — suggesting a project that still has enough structure and sponsorship to recover, but where day-to-day delivery pressure may be building faster than governance is responding.
Role confidence gaps
Leadership responses are consistently more confident than those reported by people closest to day-to-day delivery, with gaps of 29–33 points across three dimensions. This pattern suggests governance decisions may be relying on a more optimistic view of delivery conditions than the delivery team is reporting.
Delivery risk signals
Three dimensions sit in the At Risk band — risk control, governance and decision flow, and delivery confidence — indicating fundamental weaknesses in delivery oversight. Nine dimensions register at Watch level or worse, suggesting this is not a set of isolated issues but a pattern of systemic delivery control pressure.
Delivery strengths
Sponsor and leadership engagement scores in the Sound range, suggesting the project has visible senior attention and has not been abandoned or left to drift. Budget, vendor control and commercial arrangements are also relatively stable, which indicates that financial and external risk is not the primary source of delivery pressure.
Overall delivery health
WatchThe recommended actions are designed to close the information gap between leadership and delivery team experience, establish clearer ownership of decisions and risks, and create the conditions for honest escalation before delivery pressure becomes visible failure.
Run a direct leadership-to-delivery conversation — not a status report. The 29–33 point gaps on delivery confidence, risk control and governance indicate leadership is working from an incomplete picture. Convene a focused session where the delivery team speaks directly to leadership about where things are stalling, what risks are unresolved, and where decisions are not landing. Do not filter this through the PM or project reporting.
Rebuild the risk register with named owners and honest treatment assessments. Risk control is the weakest signal in this diagnostic. Review every significant risk with the person accountable for it, confirm the treatment is active and not theoretical, and set clear escalation thresholds. Leadership and the delivery team should walk away from this exercise with the same list.
Clarify decision rights across scope, budget and escalation — in writing. Governance and decision flow scores indicate decisions are taking too long or not translating into action. Map the decision types the project faces, confirm who has authority for each, and identify where decisions are stalling. Ambiguity here is a compounding risk given the weak delivery confidence scores.
Compare what executive reporting says with what the delivery team is experiencing. The leadership optimism gap suggests reporting may be softening delivery pressure before it reaches governance. Put the delivery team's diagnostic responses alongside the last three executive reports and identify where the picture diverges. This is not about blame — it is about calibration.
Hold a structured delivery reset with sponsor, PM, PMO and workstream leads. Use the findings from the above actions to agree a short list of corrective priorities, assign clear owners, and set a reporting cadence that surfaces delivery reality rather than smoothing it. Set a diagnostic rerun date within 30–45 days to confirm the reset is holding.
After receiving a report
Review the executive summary with the project sponsor and project lead.
Discuss the top confidence gaps — particularly where role groups diverge.
Agree the first corrective actions and who owns each one.
Run a follow-up check in 30–45 days if the project remains under pressure.
The Project Diagnostic is designed for repeat use. Running a follow-up diagnostic after 30–45 days shows whether confidence gaps are closing and whether corrective actions are taking effect.
The overall health score of 61/100 places this project in the Watch band. The project does not present as failing, but the response pattern indicates a delivery environment where confidence is uneven and several control mechanisms are under pressure.
The strongest signals are not in a single failing area. They appear across the operating system of the project: decision flow, risk control, delivery confidence, communication and role accountability. This suggests a project that still has enough structure and sponsorship to recover, but where day-to-day delivery pressure may be building faster than governance is responding.
The most important pattern is the gap between leadership confidence and delivery team confidence. Leadership responses are more confident than those reported by the people closest to day-to-day execution, particularly in delivery confidence, risk control and governance and decision flow. This does not mean leadership is disengaged. It may mean the information reaching leadership is too filtered, too late, or too focused on progress reporting rather than delivery experience.
This is a common pattern in ambiguous projects. The project can look broadly under control from the top while the delivery team is already compensating for unclear ownership, slow decisions, unresolved risks or changing priorities.
Risk control is the weakest signal. This suggests that risks may be known informally but are not being consistently captured, owned, escalated or acted upon. In practical terms, the project may be relying too heavily on individual effort, informal conversations or late-stage intervention rather than a disciplined risk rhythm.
Governance and decision flow also scores poorly. This indicates that decisions may be taking too long, being made without the right information, or failing to translate into clear action. When governance is weak and risk control is also weak, delivery teams can become trapped between recognising problems and not having an effective path to resolve them.
The project has some useful foundations. Sponsor and leadership engagement scores in the Sound range, suggesting the project has visible senior attention and has not been abandoned or left to drift. Budget and commercial control also appear relatively stable, which indicates that financial oversight is not currently the primary source of delivery risk.
This project appears recoverable, but it is not currently in a low-risk delivery state. The main issue is not lack of sponsorship, lack of budget or supplier failure. The main issue appears to be a gap between executive confidence and what those closest to delivery are reporting, combined with weak risk control and decision flow. The project would benefit from a short, structured reset focused on clarifying decision rights, tightening risk ownership, surfacing delivery constraints honestly, and aligning leadership reporting with the delivery team's experience.
Leadership responses are consistently more confident than those reported by people closest to day-to-day delivery, with gaps of 29–33 points across three dimensions. This pattern suggests governance decisions may be relying on a more optimistic view of delivery conditions than the delivery team is reporting.
Delivery confidence
Executive optimism gap
Sponsor / leadership: 76 · Delivery team: 43 · Gap: 33 points
Risk control
Executive optimism gap
Sponsor / leadership: 70 · Delivery team: 38 · Gap: 32 points
Governance and Decision Flow
Executive optimism gap
Sponsor / leadership: 73 · Delivery team: 44 · Gap: 29 points
Role Clarity and Accountability
Sponsor / leadership: 72 · Delivery team: 49 · Gap: 23 points
Scope and Change Control
Sponsor / leadership: 69 · Delivery team: 47 · Gap: 22 points
Thresholds: Watch ≥18 pts · Strong ≥25 pts · Critical ≥37 pts
Three dimensions sit in the At Risk band — risk control, governance and decision flow, and delivery confidence — indicating fundamental weaknesses in delivery oversight. Nine dimensions register at Watch level or worse, suggesting this is not a set of isolated issues but a pattern of systemic delivery control pressure.
Sponsor and leadership engagement scores in the Sound range, suggesting the project has visible senior attention and has not been abandoned or left to drift. Budget, vendor control and commercial arrangements are also relatively stable, which indicates that financial and external risk is not the primary source of delivery pressure.
Leadership scores are consistently higher than delivery team scores across every dimension in this diagnostic — in no case does the delivery team rate a dimension above the sponsor and leadership group. The divergence is widest on the dimensions that matter most for delivery control: risk control, governance and decision flow, and delivery confidence all show gaps of 29 points or more. The delivery team is operating with a materially different read of project health than the people making governance decisions.
| Dimension | Sponsor / leadership | Delivery team | Gap |
|---|---|---|---|
| Risk control | 70 | 38 | +32 |
| Governance and Decision Flow | 73 | 44 | +29 |
| Delivery confidence | 76 | 43 | +33 |
| Communication and Truth Flow | 64 | 51 | +13 |
| Role Clarity and Accountability | 72 | 49 | +23 |
| Scope and Change Control | 69 | 47 | +22 |
| Issue control | 65 | 56 | +9 |
| Benefits and Outcome Tracking | 66 | 57 | +9 |
| Stakeholder alignment | 68 | 58 | +10 |
| Planning and Dependency Maturity | 70 | 60 | +10 |
| Team Readiness and Psychological Safety | 71 | 63 | +8 |
| Strategic clarity | 75 | 63 | +12 |
| Vendor, Tooling and External Dependency Control | 77 | 71 | +6 |
| Budget and Commercial Control | 78 | 72 | +6 |
| Sponsor and Leadership Engagement | 90 | 76 | +14 |
Gap thresholds: Watch ≥18 pts · Strong signal ≥25 pts · Critical ≥37 pts
Start your own check
The Project Diagnostic finds the delivery risks and confidence gaps that status reports often miss.
Run a fast, anonymous Project Diagnostic. Invite your team. Get a scored diagnostic report before small risks become visible failures.
This is a sample report with synthetic data. It illustrates the structure and diagnostic output of a Project Diagnostic. Real reports are generated from anonymous stakeholder responses and are confidential to the project owner.