How to use the Hypothesis Generator.
A hypothesis needs measurable variables and a testable relationship. Separate the predicted outcome from the procedure used to investigate it.
Make the workflow fit your task.
Define measurable variables and the predicted relationship, separating the hypothesis from the study procedure. State the comparison and conditions clearly enough that evidence could challenge as well as support the prediction.
- What you provide
- Research question, variables and theoretical basis.
- What you get
- Testable hypotheses with operational definitions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Question: does an example file help users finish an import task?
Completed example
Hypothesis: users given the example complete the specified import task more often, measured under the same task conditions.
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.
Does a hypothesis become stronger by using more certain language?
Strength comes from clarity and testability, not confidence. The prediction remains something to investigate.
Why can the proposed hypothesis never be shown wrong?
Specify observable outcomes and a comparison that could fail to support it. Avoid vague terms that can fit any result.
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 ↑