Skip to content

Commit

Permalink
adding feedback advice (#9631)
Browse files Browse the repository at this point in the history
Update rule.md
  • Loading branch information
sethdaily authored Nov 29, 2024
1 parent d49e98d commit 97b74d7
Showing 1 changed file with 15 additions and 2 deletions.
17 changes: 15 additions & 2 deletions rules/do-you-offer-specific-criticism/rule.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ When you find a problem, pinpoint it directly (and recommend a solution):

::: good
Figure: Good Example - Offering criticism in this way ensures that something will happen to fix the problem
:::
:::

::: greybox
"Not done, please try again"
Expand All @@ -51,8 +51,21 @@ Figure: Bad Example - If they don't immediately know what to fix, this might end

::: good
The specific missed requirement lets them quickly fix the mistake
:::
:::

Of course, there are times that you can 'feel' that a problem exists, but you may not even be sure how are unable to pinpoint it or can't think of a good solution. In this instance you should speak to someone who you think may be able to identify a solution, come to an agreement, and then request that action be taken.

When criticism is generic, it is impossible to know what to fix.

It's alsoimportant to consider both your audience and the overall context.

* Internally, you might assess the work on a scale of 1 to 10 (without sharing the score).
* If the work rates a 9/10 or higher, feedback is generally unnecessary. Moving from a 9/10 to a 10/10 often requires incremental feedback that can feel overly critical.
* While aiming for a 10/10 is ideal, it's often acceptable to settle for a 9/10 if the effort to achieve perfection isn't justified.

:::greybox
_I hope people ask for a ‘Checked By’ when it is at least a 7/10.
Then I hope the feedback gets it to a 9/10, if not a 10._
* Adam Cogan

:::

0 comments on commit 97b74d7

Please sign in to comment.