But to run with the analogy....imagine the bacon got to the table and then said "hey, I cost extra and I'm really tasty and delicious, but also high in fat content"...if someone then decided to get the bacon, wouldn't that be their choice?
It depends - if they reasonably believed going in that the bacon was included, and then found it was extra, that's reason enough to complain. On the other hand, if the breakfast deal had "BACON IS EXTRA" is big honking letters, then that's on them.
Unfortunately, of course, most situations lie somewhere between the two extremes.
Well, that's a valid response when determining whether you feel the breakfast is good or not by your own standards. But when you're putting a review together, you have a responsibility to deal in more than just your own personal opinion.
Nope. I'm reviewing it based on
my breakfast experience. I can't do anything else - after all, it's equally possible that I had the breakfast on the one day they actually cooked it right. If my breakfast experience is ruined because I was ambushed by a bacon surcharge, it's entirely valid that goes into my review.
And, equally, if you happen to arrive on the day they have the "bacon free today!" special, that's almost certainly going into
your review - probably even if you try to adjust for it.
That's why aggregate reviews are useful: you're "bacon free today" experience negates my "bacon surcharge" one.
For instance, I'm not the sort of person who gets bothered by paying more for bacon if it's good enough bacon -- but if your review just says 'bacon extra -- 2 stars'
Sure, I get that.
IMO there are two good ways to use reviews: either find someone whose tastes broadly match your own and see what they have to say (in which case you'd rightly ignore me, and instead read people who don't mind paying for good-enough bacon),
or look at lots of reviews and take the aggregate (the "wisdom of crowds" approach). Either approach can work.