Answer
Strength Score is a quality indicator that measures how thoroughly a workflow was completed. It does not measure whether responses were correct. Instead, it helps encourage thoughtful completion by reinforcing behaviors such as adding useful detail, providing evidence, and taking enough time to complete the workflow properly.
Strength Score is most helpful when the quality of the submission matters as much as completion, especially for workflows that require observation, inspection, or careful review.
Steps
Use Strength Score when it adds value
Use Strength Score when users need to make careful observations or complete meaningful inspections.
Use it when rushed or low-effort submissions are a real risk.
Use it when you want to encourage evidence, follow-up, or stronger completion quality without relying only on manual review.
Avoid using Strength Score by default
Do not use Strength Score on every workflow automatically.
Avoid it for short, informational, or awareness-based workflows.
Avoid it when narrative input matters more than structured completeness.
Be cautious when users are still learning a new workflow or process.
Evaluate whether it is working well
Check whether users understand what good completion looks like.
Make sure scores feel fair and achievable.
Confirm the scoring approach is improving data quality without creating frustration or slowing adoption.
If users are confused or discouraged by the score, revisit the design.
Helpful notes
Strength Score encourages quality, not correctness.
It works best when thoughtful completion matters.
Overusing it can create unnecessary friction.
Strength Score should support the intent of the workflow, not distract from it.