Hi Team
@calumjs @MarcusIrmscherSSW @alexleessw @isaaclombardssw @robweitzssw
Create SSW Rule: Avoid Noncommittal 7/10 Feedback
Objective
Create a new SSW Rule explaining why reviewers should avoid giving vague "7/10" feedback and instead provide a clear, actionable assessment.
Problem
When someone asks for feedback on their work, giving a score such as "7/10" can sound helpful but often doesn't communicate what the reviewer actually thinks.
A vague middle score can leave the recipient unsure:
- Is the work good enough?
- What specifically is wrong?
- What should be changed?
- Is it ready to ship?
The rule should explain that the problem isn't using numerical scores — the problem is using a noncommittal score without explaining what it means.
Proposed Guidance
The rule should recommend that reviewers:
- Clearly state whether something is ready or not ready.
- Use Pass / Fail when the decision is whether something is ready to go live.
- If using a numerical score, make it meaningful and decisive.
- Explain what is preventing the work from being a 10/10.
- Give specific, actionable suggestions for improvement.
Example
❌ Bad
"I'd give this a 7/10."
This doesn't explain what needs to change or whether the work is good enough to proceed.
✅ Good
"I'd give this an 8/10. The overall concept works, but the opening is too slow and the CTA isn't clear enough. I'd tighten the first 10 seconds and make the CTA more prominent before publishing."
Important Nuance
Do not create a blanket rule saying that numerical scores should never be used.
Scores such as 8/10 or 9/10 can be useful when they are accompanied by specific feedback. The focus should be on avoiding vague, noncommittal feedback and making reviews actionable.
Tasks
- < Research why 7/10 feedback can be ineffective >
- < Define when Pass / Fail feedback should be used >
- < Explain how to make numerical feedback actionable >
- < Add a bad example of vague 7/10 feedback >
- < Add a good example of specific and actionable feedback >
- < Write and structure the SSW Rule >
- < Add relevant visual examples or screenshots >
- < Add links to related SSW Rules >
- < Review the rule for clarity and consistency >
- < Submit the completed rule for review >
Hi Team
@calumjs @MarcusIrmscherSSW @alexleessw @isaaclombardssw @robweitzssw
Create SSW Rule: Avoid Noncommittal 7/10 Feedback
Objective
Create a new SSW Rule explaining why reviewers should avoid giving vague "7/10" feedback and instead provide a clear, actionable assessment.
Problem
When someone asks for feedback on their work, giving a score such as "7/10" can sound helpful but often doesn't communicate what the reviewer actually thinks.
A vague middle score can leave the recipient unsure:
The rule should explain that the problem isn't using numerical scores — the problem is using a noncommittal score without explaining what it means.
Proposed Guidance
The rule should recommend that reviewers:
Example
❌ Bad
This doesn't explain what needs to change or whether the work is good enough to proceed.
✅ Good
Important Nuance
Do not create a blanket rule saying that numerical scores should never be used.
Scores such as 8/10 or 9/10 can be useful when they are accompanied by specific feedback. The focus should be on avoiding vague, noncommittal feedback and making reviews actionable.
Tasks