Jump to content

Mods/Admins: Compulsory feedback when accepting/denying delicate suggestions


kuli.fresh

Recommended Posts

What made me post this:

 

Suggestion A

http://backpack.tf/vote/id/514639deba2536120b000004 (questionable price suggestion without any proof itself that got accepted according to the proof of the later one)

Suggestion B

http://backpack.tf/vote/id/5146633e4bd7b85a5f000017 (decent price suggestion that got closed, originally posted 3 hours after the first one)

 

All discussions about pricing newly released items (in this case) left aside, I think there is need for a little change of how suggestions are accepted or denied. When dealing with shaky suggestions it should be compulsory for the mods and admins to post a short feedback/statement that outlines how and why the decision of either accepting or denying the relevant suggestion was made.

 

What's a 'shaky suggestion'?

- A suggestion that is accepted although it has not gotten up to 66,6% (two-thirds majority) of all the votes

- A suggestion that is denied although it has gotten up to/above 66,6% of all the votes

- All other undisputed suggestions (those that are clearly to deny or to accept) are not included in my reasoning at the moment

 

Where to post the feedback?

- Publicly, inside an accordingly featured box on the suggestion's page that has yet to be integrated

- Also, it would be neat if the one who suggested got a 'notification' about wether or not his suggestin got accepted (with a link to the feedback box)

- Alternatively, there could be created a sub forum, where only these official feedbacks could be posted

 

When to post the feedback?

- ONLY in cases that are questionable (see my first definition of a shaky suggestion)

- Maybe - only when the workload isn't too high, time will tell - feedbacks can be given on every suggestion

 

What to post as feedback?

- A short, clear explanatory statement (could be done with only one sentence!) why the relevant decision was made

- As an example for the above linked decision: "Although not having its own proof, suggestion A (insert link) was accepted and prefered to suggestion B (insert link). Because its price range of 13-14 keys matched the given proof of suggestion B (price range of 13-14.5 keys) a tiny bit better." This should be posted on both suggestions accordingly.

 

Why to post the feedback?

- Making the decision-making process more transparent

- Increasing verifiability and plausibility of the staff's decisions and simultaneously avoiding wasting discussions afterwards

- Giving informative, official feedback on delicate suggestions (hopefully) will help backpack.tf to maintain its reputation as a pricing guide based on consent principle (that's right, f/o spreadsheet!)

 

 

And now, hit me with your comments!

 

 

EDIT:

 

To make things clear: My idea right here is not supposed to help users create valid price suggestions in general, by giving them feedback by mods/admins afterwards. That's a learning process everyone has to experience on his own. I'd like to improve the way how shaky, fussy (or w/e you want to call them) suggestions are handled by the staff and how the staff's decisions are communicated!

Link to comment
Share on other sites

I get your idea, and it seems flawless. But admins already do so much work, I feel the other suggestion ( A note when entering backpack.tf for first time how to create a good suggestion) is a better idea, allow users to analyse them selves. Having admins do this, will really decrease the amount of suggestions they can accept or close per day.

Link to comment
Share on other sites

I get your idea, and it seems flawless. But admins already do so much work, I feel the other suggestion ( A note when entering backpack.tf for first time how to create a good suggestion) is a better idea, allow users to analyse them selves. Having admins do this, will really decrease the amount of suggestions they can accept or close per day.

 

 I get your point. That's why I limited the compulsory feedback to questionable suggestions only. I don't have numbers though how many suggestions are denied/accepted each day; how many suggestions a mod/admin processes usually each day; how many suggestions each day would be considered 'questionable' (e.g. this number might be supposedly higher on weekends than on other weekdays because of the sheer amount of more (unexperienced) users) etc.

 

Backpack.tf is expanding as latest user statistics show. The staff surely will expand accordingly and I still think that you have to handle each suggestion thoroughly when you're aim is the one of providing reliable data.

 

To make things clear: My idea right here is not supposed to help users create valid price suggestions in general, by giving them feedback by mods/admins afterwards. That's a learning process everyone has to experience on his own. I'd like to improve the way how shaky, fussy (or w/e you want to call them) suggestions are handled by the staff and how the staff's decisions are communicated!

Link to comment
Share on other sites

I almost always post feedback on suggestions I deny, and I usually post on suggestions that don't have over 85% acceptance. A bit of reasoning never hurts

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...