Which decision did the update support?
Optional short textRetain the specific point or condition described; avoid replacing it with an unexplained rating.Operations and internal services / Survey guide
Operations and internal services · Practical survey guide
Project status update survey
Improve the usefulness of progress reporting.
Opens product registration. Example questions are not imported automatically.
DESIGN THE ANSWER SPACE
What risk explanation was missing?
Optional written explanationKeep context that distinguishes different experiences. Do not treat a status label as delivery evidence.What should the next update change?
Optional improvement suggestionKeep the suggested change separate from whether it has been tested. Add risks, owners, and decisions required.Suggested formats to adapt, not preconfigured product fields.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Reports list activity without explaining blocked decisions.
Choose an action to test
Add risks, owners, and decisions required.
Check the experience again
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.
Read the answers carefully
Keep the conclusion within the evidence.
Do not treat a status label as delivery evidence.
Reports list activity without explaining blocked decisions. This is a synthetic example, not a customer result. Do not treat a status label as delivery evidence.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Improve the usefulness of progress reporting.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which decision did the update support?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Choose an action
Add risks, owners, and decisions required.
A useful starting point
Questions to understand the actual experience.
Improve the usefulness of progress reporting. Use the prompts relevant to your audience and allow people to skip situations they did not encounter. Keep response handling consistent with what you explain in the invitation.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
Which decision did the update support?
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.
What risk explanation was missing?
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.
What should the next update change?
Turn the requested improvement into a testable next step. One illustrative action is: add risks, owners, and decisions required.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which decision did the update support? What risk explanation was missing? What should the next update change?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which decision did the update support? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| What risk explanation was missing? | Optional written explanation | Keep context that distinguishes different experiences. Do not treat a status label as delivery evidence. |
| What should the next update change? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Add risks, owners, and decisions required. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Before you send it
Check what your wording assumes.
Would you agree that everything about project status update was clear and easy?
Which decision did the update support?
The first wording combines an assumed positive outcome with two different judgments. The revised prompt asks about a specific experience and permits an inconvenient or uncertain answer.
Build with SurveyTeams
Draft your own project status update questionnaire.
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Before you send it
Questions, answered.
Who should receive this questionnaire?
Colleagues who used or delivered the described internal process. Ask only about steps each person encountered; do not treat a voluntary response sample as representative.
When should I ask these questions?
Ask after someone has encountered the situation described in “Which decision did the update support?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
What should I investigate in the answers?
Reports list activity without explaining blocked decisions. This is an illustrative pattern to look for, not a claim about your respondents. Do not treat a status label as delivery evidence.
What would a practical follow-up look like?
Add risks, owners, and decisions required. 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.
How should I ask “What risk explanation was missing?”?
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. Use an optional written explanation when predefined choices would hide relevant context.
Can I use the questions in SurveyTeams?
Copy the prompts or download TXT, CSV, JSON, or a Markdown worksheet, then adapt them in your own survey. The CTA opens registration; it does not import this example automatically. Verify available features in your account.
Continue exploring