An enterprise tagging article, “The Name Game“, mentions IBM’s internal suggestion box application called ThinkPlace…the entries in this box were first classified in a taxonomy, but soon user tags seemed more applicable. Besides the obvious I can see why, as ideas and suggestions may involve cutting edge terminology that the taxonomy just doesn’t keep up with.
Web 2.0 Suggestion Digger
This got me thinking, what about a web2.0 suggestion box, there are so many web 2.0 services out there, and we all blog about them, offer feedback, compare them to other services, make wishlists…
What if instead, we could contribute our suggestions to a central place…owners or services like Bloglines, del.icio.us, Rojo, etc… could subscribe to the tag RSS feed for their company name, and listen to what people have to say, and offer comments…anyone can rate these ideas, some entries may get many positive votes/ratings, inturn the company may think it’s worthwhile implementinga suggested feature.
So it’s kind of like Digg, but with tagging as well, and the content is focused on feedback/suggestions/wishlist…actually you are not submitting a URL, you are writing a text entry.
Also, categories may not be required as “Web2.0″ already is a specific enough category.
- user space
- users make a text entry and tag it
- each entry has a permalink
- others can rate it (actually voting may be more appropriate, or even both)
- others can leave comments
- all entries are aggregated into a tag cloud
- latest entries are on the homepage (most popular entries, most popular tags, etc…)
When you add an item you fill in the:
- title field
- body of text
- tag field 1 for the brand/company name
(even type in the URL of the company/brand name)
- tag field 2 for the type of service eg. RSS Reader
(if this was provided as a drop down selection menu, then you have the disadvantage of not finding a value that suits the service you are talking about..tags are better, especially if the service is the first of it’s kind
…ie. tagging over inhouse categories)
- tag field 3 to describe the suggestion
TITLE - Bloglines needs tags, not folders
BODY - I think tags are better than folders when organising your feeds, as feeds can live in multiple places…blah, blah, blah,blah, blah, blah,blah, blah, blah…
TAG (Service/Brand/Company) - Bloglines
TAG (Type) - RSS Reader
TAG (Keyword) - folders, tags,
Then someone can come along and add to these fields:
COMMENT - totally agree, it’s about time they catch up
RATE - 1 Vote
I guess you could have 3 tag clouds, one for the TAG (Service) field, one for the TAG (Type) field, and one for the TAG (Keyword) field
…maybe the last 2 fields could be merged into one.
This proposed service is based on a centralised idea…not sure if it could be aggregated like the edgeio idea.
This could be an option has people like to publish in their own place instead of having original content scattered all over the web…and plus you have to build a community which is very difficult.
Microcontent aggregating may need to still build a community, but the people are not required to congregate at the community house. That is, in “edgeio” people have to be aware to use the rel=tag “list” in order for their content to appear (re-syndicate) in edgeio, so the first stage is awareness, if people are happy with that as they blog they may choose to include the “list” tag and that’s it, they don’t have to go to edgeio.
So it may be more suitable for the publisher to apply some tags to their content where others can pick these up in order to re-syndicate the content.
Another way a company welcomes feedback is in a forum (if the service provides one)…these are usually divided into mini-topic forums to discuss; bugs, user issues, question, feedback, suggestions, etc. The topic forum called, “feedback/suggestion”, could instead be in the form of a Suggestion Box Memedigger tagging service instead of a forum.
A “suggestion box memedigger tagging service” can be of help for any company, it may be more powerful than a forum or a simple email service to send in feedback and suggestions.
The second application can be for a login user service around the topic of web2.0 companies, people can join and write text entries, and tag these entries…then others can leave comments and ratings.
The content of the text entries have to be about a suggestion or feedback to a given company/brand/service.