Executives rarely lack information about their projects. They lack the right information. Status reports are written by people with every incentive to show progress, and dashboards measure what is easy to count rather than what matters.
You do not need to dig through every artifact to know whether an initiative is in trouble. You need to ask better questions. These five consistently cut through optimistic reporting and reveal the real picture.
1. "What has actually been delivered and accepted?"
Not what is in progress. Not what is 80 percent complete. What has been finished, tested, and formally accepted by the business?
Percent-complete figures are notoriously unreliable because the last 20 percent of any task often takes as long as the first 80. Accepted deliverables are facts.
Listen for: Vague answers, heavy reliance on percentages, or confusion about who has authority to accept work.
2. "What decision do you need from me, and by when?"
Many troubled projects are not failing because of the team. They are waiting on leadership — for a policy call, a funding decision, a resource commitment, or a resolution between two departments.
This question shifts the conversation from reporting to action, and it signals that you are there to remove obstacles.
Listen for: A long backlog of unresolved decisions, or a team that hesitates because it has learned escalation is not welcome.
3. "What would have to be true for us to hit the current date?"
This is a gentler, more revealing version of "Are we on schedule?" It invites the team to name the assumptions holding the plan together.
If the answer is a list of things that all need to go perfectly — no defects, no staff turnover, every vendor on time — the date is not a plan. It is a hope.
Listen for: Dependencies outside the team's control and assumptions no one has validated.
4. "What are you most worried about that is not on the report?"
Every project team knows things that never make it into the formal status. Asking directly, privately, and without judgment gives people permission to share them.
This question works best one-on-one and is most powerful when asked below the project manager level as well — with workstream leads, testers, and business subject matter experts.
Listen for: Hesitation, long pauses, and the phrase "I probably should not say this, but…"
5. "If we stopped today, what would we keep?"
This question reframes the project around value instead of activity. It helps you understand what has been built that the organization would actually use and whether the remaining investment is still justified.
It is also the first question to ask before deciding between a reset and a restart.
Listen for: Whether the team can tie completed work to business outcomes — or only to the project plan.
How to use these questions
Ask them consistently, not only when a crisis is visible. Ask them in a tone of curiosity rather than accusation. Teams tell the truth to leaders who have shown they can hear it without punishing the messenger. Over time, these questions shape a culture where problems surface early, while they are still inexpensive to fix.