Which outcome needs clarification?
Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: teams begin work with different definitions of completion.
Operations and internal services · Practical survey guide
Check whether a project starts with shared expectations.
Opens product registration. Example questions are not imported automatically.
BEFORE YOU INVITE PEOPLE
Local planning aid. No answers are submitted or saved.
A useful starting point
Check whether a project starts with shared expectations. 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.
Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: teams begin work with different definitions of completion.
A missing dependency identifies an input, decision or handoff not accounted for at kickoff. Record its responsible role and review condition, while distinguishing an agreed plan from proof that the dependency is achievable.
Turn the requested improvement into a testable next step. One illustrative action is: agree acceptance criteria at kickoff.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which outcome needs clarification? What dependency was missing? What should be agreed before work starts?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
| Question | Suggested format | What to preserve |
|---|---|---|
| Which outcome needs clarification? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| What dependency was missing? | Optional written explanation | Keep context that distinguishes different experiences. Agreement does not prove feasibility. |
| What should be agreed before work starts? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Agree acceptance criteria at kickoff. |
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
Would you agree that everything about project kickoff was clear and easy?
Which outcome needs clarification?
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.
Read the answers carefully
Agreement does not prove feasibility.
Teams begin work with different definitions of completion. This is a synthetic example, not a customer result. Agreement does not prove feasibility.
A worked interpretation example
Illustrative scenario. These are not customer results.
Teams begin work with different definitions of completion.
Agree acceptance criteria at kickoff.
After trying the change, repeat “Which outcome needs clarification?” with people who experienced it. Check whether they still describe the original issue: teams begin work with different definitions of completion. Compare explanations and sample context, rather than claiming the change caused an improvement.
From question to next step
Start with the decision: Check whether a project starts with shared expectations.
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which outcome needs clarification?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Agree acceptance criteria at kickoff.
Before you send it
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.
Ask after someone has encountered the situation described in “Which outcome needs clarification?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Teams begin work with different definitions of completion. This is an illustrative pattern to look for, not a claim about your respondents. Agreement does not prove feasibility.
Agree acceptance criteria at kickoff. After trying the change, repeat “Which outcome needs clarification?” with people who experienced it. Check whether they still describe the original issue: teams begin work with different definitions of completion. Compare explanations and sample context, rather than claiming the change caused an improvement.
A missing dependency identifies an input, decision or handoff not accounted for at kickoff. Record its responsible role and review condition, while distinguishing an agreed plan from proof that the dependency is achievable. Use an optional written explanation when predefined choices would hide relevant context.
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.
Build with SurveyTeams
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.
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Continue exploring