Jump to content

Feature voting and pledge system


TheCarterFamily

Recommended Posts

Posted

When a new feature is requested in the forums, a discussion starts. Reading these discussions I walk away with a sense of what will be implemented is based on who screams the loudest.

 

I thought a better system would be like the Dell Idea Storm or CodeWeavers voting system (http://www.codeweavers.com/compatibility/browse/name/?app_id=6293) Where someone can present an idea and it can be voted on. That way the developers can get a clear sense of which features people find most useful. The second part, which code weavers has implemented, would be a pledge system. I've had many show stopper issues come up for me that have hindered my ability to cache paperless effectively. I personally would mind throwing some money at an idea to get it put in, if that's what it takes.

Posted

....but good idea - no matter how well thought out and how well received and voted on may conflict with the basic business model and then cannot be implmented. Since TPTB tend to not comment much on such things - I am quite certain that the outcome of a vote will make no difference.

 

Besides - companies tend not be democratic in what/how services are offered. Nor should they be if profit is at all a consideration.

Posted

Being a scout leader and involved in the District and Council level of scouting, I was amazed that I stumbled on their professional interface for an "Innovation Engine". It's similar to what you have suggested, and the best ideas rise to the top with "props" voting them up, and fall to the bottom with people dissing the idea.

 

Here's the top 3 ideas, and the bottom 3

 

#1 A quick report for Scout professionals to seeing if a unit has met minimum training standards for their leaders

#2 Training reports for volunteers to have their e-mail addresses built right in for easier contact

#3 Have Mike Rowe from Dirty Jobs (an Eagle Scout) do a show on the National Centennial Jamboree coming up this summer

 

#418 Renaming the Venturing program to something else like "Teen Adventure"

#419 To achieve Arrow of Light in Cub Scouts or Eagle in Boy Scouts, a scout has to participate in fund raising for at least 3 years

#420 Having Eagle Rank awards for Adults

 

These are voted on by the professionals (executives).

 

I think the idea has merit, as long as TPTB have a "veto" ability.

Posted

I think the idea has merit, as long as TPTB have a "veto" ability.

 

With the Groundspeak "veto", I agree that this is a great idea. The veto would allow the company and developers to weigh what the "public" really wants against time/money investments and the super-secret corporate plans.

 

The more ways that a company can get the pulse of their customer base, the better. There's nothing requiring them to implement the top 10 requests just cuz lots of folks want them.

Posted

When a new feature is requested in the forums, a discussion starts. Reading these discussions I walk away with a sense of what will be implemented is based on who screams the loudest.

 

I thought a better system would be like the Dell Idea Storm or CodeWeavers voting system (http://www.codeweavers.com/compatibility/browse/name/?app_id=6293) Where someone can present an idea and it can be voted on. That way the developers can get a clear sense of which features people find most useful. The second part, which code weavers has implemented, would be a pledge system. I've had many show stopper issues come up for me that have hindered my ability to cache paperless effectively. I personally would mind throwing some money at an idea to get it put in, if that's what it takes.

Sadly, features and bug requests are 2nd to revenue, they focus on revenue first (ads on the pages and in forums, making sales pitches out of the gps reviews "feature", etc), only after they quit working on that do they finally take a serious look at bug fixes and features.

 

Its nothing about what current paying customers want, they figure you are already on the hook, and new customers aren't aware of the bugs and much requested features till they are on the hook too.

 

The only thing that changes companies attitudes on things like this is a mass exodus of customers, and too many people want their pq's over making a statement to get bugs fixed and usable features implemented.

 

I'm not saying features and bug fixes never happen, they are just low on the totem pole and gc has no incentive to prioritize them.

 

For example, its been asked since I started gc'ing for the keyword search to return results in order of distance, or at least limit them to a state or area. Currently, and as it has been since I started using the site, keyword searches are returned by date, a totally useless order, I could care less about caches that are 5000 miles away. When I search for the word "bridges" I have to page about 10 or 15 pages before even finding one in my area. No one has stated they like it the way it is. The problem? There is no revenue incentive to fix it.

 

Another example, what have they stated they have been working on for a soon release? PQ's. Why? Because they know they've lost paying customers because of the overall unreliability and weakness of the current pq system.

Posted
[quote name='TheCarterFamily' Sadly, features and bug requests are 2nd to revenue, they focus on revenue first (ads on the pages and in forums, making sales pitches out of the gps reviews "feature", etc), only after they quit working on that do they finally take a serious look at bug fixes and features.

 

That's why I suggested the pledge system in there. If we pledge the top 10 with enough money they could hire someone temporarily to implement them.

 

Personally I'd like to see them adopt an open-source business model like Google is doing, or at least partially. I'd be happy to write your feature request, free of charge, and submit it to TPTB for review and implementation. I'm sure there are others that would write enhancements for GC.com just because they love the sport.

 

A while back I created a database build from 3 years of collecting GPX Pocket Queries, just so I could do polygon and search by route type queries. This came in handy for trips where standard Center of Screen type searches would return 10,000 caches to cover the distance. Granted once I got my iPhone the need for this DB went away as it can do live searches from my current position and I've archived the entire system. But the time I spend developing that system I could have easily submitted code changes for review and GC.com would have benefited.

Posted

Sadly, features and bug requests are 2nd to revenue, they focus on revenue first (ads on the pages and in forums, making sales pitches out of the gps reviews "feature", etc), only after they quit working on that do they finally take a serious look at bug fixes and features. <snip>

 

This is a little cynical. It's true revenue is a primary concern; afterall, the site doesn't run on butterflies and fairy dust. Also there are 40 people here who must be fed and clothed.

 

However, it would be pretty shortsighted of us to only focus on making money. There is a balance to be struck. We weigh the needs of the community against the needs of the business and measure the results. Sometimes we get it wrong, sometimes right, but always with the best intentions.

Posted

A petition may be better than voting. If you get enough users to stand up and ask for something it may help Groundspeak prioritize changes that may be on the list. Change is difficult and comes with risk. As OpinioNate say, there is a balance. I like to think that the time it takes to get things changed on the site is because of diligence to make sure it is the right choice and it is done correctly to minimize any possible disruption.

 

You are probably somewhat correct in observation that the squeaky wheel gets the grease. That may also be because the squeaky wheel needs the grease.

 

Don't get me wrong about money being the number one thing. I have learned over the years that if you can show money to be made, or happier customers, and I don't mean a few dozen but rather a considerably large volume of customers will noticeably benefit from the change, the chances are your idea will move up on the list.

Posted

Sadly, features and bug requests are 2nd to revenue, they focus on revenue first (ads on the pages and in forums, making sales pitches out of the gps reviews "feature", etc), only after they quit working on that do they finally take a serious look at bug fixes and features. <snip>

 

This is a little cynical. It's true revenue is a primary concern; afterall, the site doesn't run on butterflies and fairy dust. Also there are 40 people here who must be fed and clothed.

 

However, it would be pretty shortsighted of us to only focus on making money. There is a balance to be struck. We weigh the needs of the community against the needs of the business and measure the results. Sometimes we get it wrong, sometimes right, but always with the best intentions.

You should try the butterflies and ferry dust. They burn pretty clean...
Guest
This topic is now closed to further replies.
×
×
  • Create New...