I have to comment on the "Jeremy gets to decide what is and isn't a geocache". Undeniably true - he calls the shots.
But why the heck would the Jeremy as the CEO of a company care so little about the customers? Here is what I think is the epitome of not caring about customers:
Forum poll to Keep Challenges: 3 votes
http://feedback.geocaching.com/forums/75775-geocaching-com/suggestions/2184225-keep-challenges?ref=title
Forum poll to Remove Challenges: 1489 votes before it was closed down
http://feedback.geocaching.com/forums/75775-geocaching-com/suggestions/2170539-remove-challenges-it-has-nothing-to-do-with-geoca
Geocaching.com is really just a software company - their product is the concept plus the site to support the concept. We buy that software+concept bundle. Most client facing software companies care enough about their customers that they have a beta test site. The very best type of beta test is open to any customer, but even a 'by invitation' closed beta test is better than rolling out a new concept (after clearly significant development) without customer comment. Beta testing lets you find out the crap (in your design, in your performance, knock on problems, etc.) before you spring it on your purchasing customers. If Groundspeak had opened up a proper beta test for Challenges:
1. A Beta Test would have pointed out putting as the 'shining example' of a Challenge is to 'Kiss a Frog' was the most idiotic, unproductive. and development budget wasting thing they could have possibly done. (If that one was Jeremy's idea then hopefully some lacky (or all of them) has had the guts to tell the Emperor he was a fool.)
2. Some reasonable ideas on how to improve the roll-out would have come out in beta testing:
a. don't make challenges count in the find count until the concept is working well - easier to retrofit counts up than take the heat while the bugs in the concept are being worked out.
b. Some method of review should take place before publishing challenges (if not forever then in the initial go)
c. Oh - even though Groundspeak knows what a challenge is perhaps we should by gosh have more than a half a paragraph on the web site as to what makes a good challenge
d. The crashing of the base Geocaching.com system (that, er, pays the bills) caused by the introduction of challenges would have hopefully been averted.
e. Groundspeak would have created several extremely good challenges of "standard" type that could be viewed as shining examples (did anyone mention that the global "Kissing a Frog" challenge created by Groundspeak as the 'best practice' challenge was mind numbingly stupid?)
We really like virtuals (and while much respect for Clan Rifster, I'm cool with these 'go use your GPS to go somewhere and learn something' caches counting as real caches.) Jeremy says he spent too much of his development budget on Challenges so they are going to stay in the game no matter what the backlash from the paying customers is - so we better like them dammit! But I could not imagine a worse implementation or worse implementation roll-out.