[maemo-community] Brainstorm implementation (was Re: Brainstorm: useful?)

[From: Randall Arnold]

 ----- Original message ----- 
From: "Tim Samoff" 
To: "List for community development" 
Subject: Brainstorm implementation (was Re: Brainstorm: useful?)
Date: Tue, 15 Dec 2009 09:01:47 -0600

  
   
Hi, I wonder if the implementation of Brainstorm was just done wrong in the first place (as initially proven by how many people submitted ideas without solutions attached). To me, it seems like Brainstorm should consist of single-level ideas/issues that can be voted upon... Then, the discussion of such ideas/issues may or may not include solutions (some half-baked, some not), which are not voted upon. Then, either an independent dev, or someone at Nokia could claim the idea/issue if there are enough votes and act on it -- either by using the discussion as a "guide," or going about it in their own way. Afterall, the idea/issue is the important factor, not the various solutions... Sometimes, the solution providers know absolutely nothing about what it would take to implementat said solution (I'll add myself to that group), and sometimes, solution providers really come up with some gems. But, I'm proposing that the solutions should be presented in the form of casual discussion, not formal answers. Then, whomever thinks they can solve the item in question can claim it and begin work -- maybe even by adding it to Bugzilla with a proposed milestone date. When the item is complete -- by an independent dev or by a Maemo dev -- the Brainstorm item is closed (as is the Bugzilla item). Hope that made sense. Tim -- http://samoff.com      
<< 2.dat >>

I get what you're saying Tim but have to disagree-- with a caveat.

IMO if Brainstorms are constructed properly, they are abstracted as much as possible from solutions.  With exceptions of course being very basic subjects with one or two easily-identified solutions.

If/when Brainstorms are constructed at a high level (ie, "Improve Ovi Maps") then Solutions can be very diverse, ranging from adding a line to documentation to overhauling the application.  Personally I'd like to see most Brainstorms done that way, and receive the attention of numerous solutions.  But if there are multiple valid solutions that come under the umbrella of a single group, then they need to be prioritized-- thus the value of voting on Solutions.

I also see nothing wrong at all with posing problems having no initial solutions.  The idea there is to foster Brainstorming, with the originator acting as facilitator and trying not to lead contributors down an arbitrarily narrow, predetermined path.  Brainstorming should be as free as possible/practical at first and only refined (normed) once the storming starts to fizzle.

The way I see it, Solutions need to be classified individually, and that being the case, they can become more important than the original Brainstorm item.  They should be managed independent of each other, closed as they are implemented or discarded, and the original Brainstorm proposal itself not closed until all individual Solutions associated with it have been addressed in some form or fashion.

I believe there's a lot of potential value in Brainstorming that's not yet fully realized, but like all new and growing things it will take a refinement of the process to bring that potential out.  If someone needs to act as process mapper and document the flow, I don't mind doing it.

Randall (Randy) Arnold
maemo.org community council
http://tabulacrypticum.wordpress.com/

--------------------------------------------------------------
Ovi Mail: Being used by users in 178 countries
http://mail.ovi.com