Primary Role: Workflow Manager - Admin
Learning Focus: Learn
Where: Editor
🎯 Why This Matters
Strength Score helps encourage thoughtful, complete workflow submissions. When used appropriately, it improves data quality and reduces rushed or incomplete responses.
📝 What Strength Score Measures
Strength Score is a quality indicator that reflects how thoroughly a workflow was completed, not whether answers were “right” or “wrong.”
It is designed to:
Discourage rushing through workflows
Encourage photos, text, and follow-up actions
Promote consistent effort across users
Strength Score focuses on behavior, not judgment.
🛠️ When Strength Score Adds Value
Strength Score is most useful when:
Workflows require careful observation or inspection
Quality of input matters as much as completion
There’s a risk of users rushing just to finish
In these cases, Strength Score helps reinforce expectations without adding manual review.
⚠️ When Strength Score May Not Be Needed
Strength Score may not be appropriate when:
Workflows are short or informational
The goal is awareness, not evaluation
Narrative input is more important than completeness
Users are still learning a new process
Overusing Strength Score can create unnecessary friction.
✅ What Good Looks Like
When Strength Score is working well:
Users understand what “good completion” looks like
Scores feel fair and achievable
Data quality improves without slowing adoption
If users are confused or frustrated by scores, it’s time to revisit the approach.
🔑 Key Takeaways
Strength Score encourages quality, not correctness
Use it where thoughtful completion matters
Avoid using it on every workflow by default
Set up and validate Strength Score:
Job Role: Workflow Manager | Permission Level: Admin / ANVL Web + ANVL Workflows | Special Rights: Workflow Management (Create / Edit / View / Publish - UAT / Publish-ALL / Admin)