How to use the OKR Generator.
Objectives describe a meaningful direction; key results describe measurable outcomes. Avoid treating a task list as evidence that the outcome occurred.
Make the workflow fit your task.
Write an objective that states meaningful progress, then define measurable key results with baselines, targets and consistent measures. Keep initiatives separate from outcomes so completing tasks is not mistaken for achieving the objective.
- What you provide
- Team goals and measurable business outcomes.
- What you get
- Objectives and measurable key-result proposals.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Draft an illustrative quarterly OKR for easier imports. Supplied baseline: 20% failed attempts and 40% successful first imports. Proposed targets: 10% and 60%, using unchanged event definitions.
Completed example
Objective: Make the first import easier to complete correctly. KR1: Reduce the failed-attempt rate from 20% to 10% during the quarter, using the same failure definition. KR2: Increase the successful-first-import rate from 40% to 60%, using the same eligible-user definition. Review requirements: confirm the baseline period, data source and target feasibility before adopting these proposed commitments.
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.
Can a key result simply be launch a feature?
That measures delivery rather than the resulting effect. Use it only when delivery itself is the intended outcome and label it accordingly.
Why are key results impossible to evaluate at the end of the period?
Establish the baseline, measure and data source before starting. Undefined terms such as improve quality need an observable interpretation.
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 ↑