🧭 Before You Start
Strength Score does not appear in ANVL Manager.
Validation must be performed using Power BI reports and real production submissions.
Before validating:
Strength Score is enabled and configured on the workflow
The workflow is active in a production site
Users are completing the workflow as part of normal work
🔗 See the following to Enable Strength Score:
🎯 Why This Matters
Strength Score is intended to reflect real user behavior over time.
Short-term testing, UAT submissions, or test users will not produce meaningful results.
Validation confirms that:
High-quality workflows score higher
Low-effort workflows score lower
Scores align with program expectations
📝 What “Validation” Means for Strength Score
Validating Strength Score is not about checking if a score exists.
It is about confirming that:
The distribution of scores makes sense
The score reflects observed quality, not noise
The metric is trustworthy for leaders and programs
Validation Steps
🛠️ Step 1: Allow Real Usage Time
After enabling Strength Score:
Allow approximately 2 weeks of normal workflow usage
Do not coach users differently during this period
Aim for enough volume to see variation in behavior
Strength Score needs behavioral diversity to be meaningful.
🛠️ Step 2: Review Strength Score in Power BI
Open the Trending Metrics or Weekly Summary report in Power BI
Filter to:
The specific workflow
The desired time range
Relevant site(s)
Review overall score distribution:
High scores
Mid-range scores
Low scores
You are looking for patterns, not perfection.
🧠 Step 3: Sample and Compare Workflows
Select approximately:
5 high-scoring workflows (expected “excellent”)
5 mid-range workflows (expected “good”)
5 low-scoring workflows (expected “poor”)
For each group, manually review the workflows and ask:
Does the observed quality match the score?
Are high scores earned through good behavior?
Do low scores reflect rushed or incomplete submissions?
⚠️ Step 4: Identify Misalignment (If Any)
Strength Score may need adjustment if:
“Excellent” workflows score lower than expected
Poor-quality workflows score too high
Scores cluster too tightly with little variation
Common causes include:
Weights that overemphasize one behavior
Parameters that are too strict or too lenient
Using too many parameters at once
🛠️ Step 5: Adjust and Re-Evaluate
When tuning Strength Score:
Adjust weights first (preferred)
Adjust parameter thresholds only if needed
Avoid adding new parameters unless necessary
After changes:
Republish the workflow
Allow additional real usage time
Re-review Power BI results
Iteration is expected.
✅ What Good Looks Like
Strength Score is working when:
Score ranges feel intuitive
High-quality behavior is consistently rewarded
Low-effort submissions score meaningfully lower
Stakeholders trust the metric
Strength Score does not need to be “perfect” to be valuable.
🔑 Key Takeaways
Strength Score validation happens in Power BI, not Live Feed
Real production data is required
Compare scores to actual workflow quality
Iterative tuning is normal and expected