Opinion on rating system: am I over-complicating it?
I'm working on a niche freelance marketplace, and have been putting some thought into the rating system. I want us to have a system that's actually useful, vs typical 1-5 star systems where anything under 5 stars is shameful.
What I'm trying to design, is something that accurately represents whether a freelancer typically completes jobs successfully, and then something to reward freelancers who go above requirements.
What I came up with is the following:
- job satisfaction is rated with 4 emojis: disappointed, neutral, happy, very happy. They correspond to scores from 1 to 4. Once all reviews are added together, we obtain a % that represents the average job satisfaction
- would recommend is rated with yes/no. Corresponding scores are 1 and 0, and we also get a % for the average
- on top of that, if a client gave a "very happy" rating and said they would recommend, we ask them if the freelancer exceeded expectations. If they say yes, then we say they were "wowed". This doesn't affect scores but comes as an additional indicator.
Visually on the profile it looks like this: https://www.dropbox.com/s/u62mfra9skdjdrd/Reviews.png?dl=0
We see job satisfaction as the baseline. Ideally every freelancer has 100%. Recommendations give a better sense of how well past jobs have gone, while Wows helps freelancers who go above and beyond stand out.
What do you all think? Is this a worthy system? Not too complicated?
The system sounds solid - but I agree with @StudioCinematicApp to just start with a more simple version and add-on if/when needed. I just finished a rating system for a marketplace as well and it can get messy, fast.
Could you share about your system?
By looking at the design, this looks pretty neat. It is a bit over complicated IMO.
The thing I suggest - is even if this would be the end goal (what you wrote), start with a simple 5-star system, and go from there.
Not sure if you already have customers, but I take it there's a lot of other features you need to implement, and of course, get users. You can indeed implement this in time.
Thanks for the feedback, it's a good idea.