Calculate the Effort Score:
Use the responses from the column "[Column with effort ratings]" in the attached CSV to calculate the Effort score using the following formula:
Effort Score = (sum of all Likert ratings in [Column with effort ratings]) ÷ (number of responses) ÷ 7
Likert Ratings are coded on a 7-point scale, where:
Strongly Agree (least effort) = 7
…
Strongly Disagree (most effort) = 1
After calculating the Effort score, report where it lands on the following scale:
Very Good = above 90%
Good = 70–89%
Average = 50–69%
Poor = 30–49%
Very Poor = 0–29%
Next, analyze the responses in the column "[Column with qualitative explanations]" in the CSV to identify common themes and provide clear, actionable suggestions for how the Effort score could be improved.
Here’s your Effort analysis from the CSV you attached.
Effort Score (Section 3 Choices)
Scale used (7-point; 7 = least effort, 1 = most effort).
Your data in “Section 3 Choices” is already recorded as numeric 1–7 values, so I computed the score directly.
Counts (N = 100):
7: 55
6: 25
5: 9
4: 5
3: 1
2: 1
1: 4
Computation
Effort Score
=
∑
ratings
𝑁
÷
7
=
609
100
÷
7
=
0.870
=
87.0
%
Effort Score=
N
∑ratings
÷7=
100
609
÷7=0.870=87.0%
Scale placement: Good (70–89%)
You can review the distribution table I shared in the workspace, and download it here:
Download the distribution CSV
A bar chart of the 7-point distribution is shown above.
“Section 3 Explanation” — themes
I checked the “Section 3 Explanation” column in this file and it has no non-empty responses, so there isn’t qualitative text to analyze in this export.
Recommendations to push Effort from Good → Very Good
Based on the distribution (most ratings clustered at 6–7 but a few low scores remain), here are targeted actions that typically shift effort perceptions upward:
Eliminate the friction points that create 1–3 ratings
Add a short guided first-run (30–60 seconds) with defaults and a single “Next” action per step.
For any form or input, provide inline validation and examples to prevent trial-and-error.
Shorten the path for common tasks
Identify the top 1–2 tasks and add a one-click shortcut (preset template or auto-filled starter).
Replace multi-page flows with in-place steps (progress header: Step 1/3 → Step 2/3 → Step 3/3).
Strengthen information scent & orientation
Use verb-led labels (“Create project”, “Invite team”) and contextual help (tiny “?” tooltips, no external docs) exactly where confusion ever occurs.
Keep primary actions visually dominant; demote secondary links.
Guardrail complexity
Hide advanced options behind “Show advanced” so novices aren’t overwhelmed, but power users still have access.
Remember last choices and pre-select sensible defaults on return visits.
Measure the lift
After shipping the tweaks, re-field the same 7-point question; target ≥90% overall (Very Good) and reduce 1–3 ratings to ≤2 total.