# Project status update survey

Improve the usefulness of progress reporting.

If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.

## 1. Which decision did the update support?

Answer: ____________________

## 2. What risk explanation was missing?

Answer: ____________________

## 3. What should the next update change?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Identify the decision a progress update helped its reader make and the information used. Preserve that useful context while distinguishing it from blocked decisions and delivery evidence.
2. A missing risk explanation reveals whether status reporting omits the condition affecting progress. Describe the known constraint and relevant next review, without treating a color or label as evidence of delivery certainty.
3. Turn the requested improvement into a testable next step. One illustrative action is: add risks, owners, and decisions required.

Interpretation caution: Do not treat a status label as delivery evidence.


## Illustrative finding and follow-up

Observation: Reports list activity without explaining blocked decisions.

Action to test: Add risks, owners, and decisions required.

Follow-up: After trying the change, repeat “Which decision did the update support?” with people who experienced it. Check whether they still describe the original issue: reports list activity without explaining blocked decisions. Compare explanations and sample context, rather than claiming the change caused an improvement.