How to use the 360 Feedback Question Generator.
Multi-rater questions should concern behavior respondents can observe. Give an appropriate way to indicate insufficient experience rather than forcing a rating.
Make the workflow fit your task.
Translate each competency into behavior respondents could actually observe. Use a clear response scale and an insufficient-observation option, keeping separate concepts in separate questions so the feedback can be interpreted.
- What you provide
- Role competencies and review purpose.
- What you get
- Behavior-based multi-rater questions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Create one observable 360-feedback question about communicating project risks. Include a frequency scale and an unable-to-observe choice.
Completed example
Question: When a project risk became apparent, how consistently did this person raise it with enough context for others to act? Choices: never; rarely; sometimes; often; consistently; unable to observe. Optional example: Describe a situation that informed your answer, without including unnecessary confidential details.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should every rater be required to score every competency?
Allow an unable-to-observe response when appropriate. Forced ratings can create apparent evidence where the respondent lacks experience.
Why do the questions produce vague praise or criticism?
Ask about a specific behavior in a defined context. Broad traits are harder to observe consistently across different working relationships.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑