h a l f b a k e r yWe are investigating the problem and will update you shortly.
add, search, annotate, link, view, overview, recent, by name, best, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
The architecture is defined by a workflow or project methodology, which becomes a separate management product in and of itself, and of which players may also contribute. Some methodology plugins may prove better than others, so good idea-synthesizing methodologies become perhaps as praised/prized as
good ideas themselves.
The first step, depending on the methodology plugin in use, may be something like 'define the problem space'. This is a stage in which many contemporary individually-contributed ideas are frequently generated without even touching the sides. Said stage is more likely skipped altogether due to an assumption along the lines of "the problem is already obvious, let's just get on with providing a solution".
Beyond that, the methodology defines what happens to arrive at the output product (ie, an idea worth holding up to the world). How it happens, who is involved, the resources, timing, effort, and any methodology-specific stages, methods, techniques or procedures, are entirely up to the methodology. Perhaps there should be a default collaborative idea-having methodology for this venue, just to get the ball rolling. Similarly, there should be available some nifty online tools to utilise for the various activities that comprise professional-level idea generation.
The 'release' stage is probably not quite the end result, and would resemble a 'critique' stage, and itself might act like the halfbakery does now in that it gathers input from non-participants (who are nevertheless equally likely at that stage to become late-process participants through contribution).
As you can probably see, the idea is slightly decoupled from the individual ego in this process, and emphasises not only the team but the application of the methods.
FabLab
http://fab.cba.mit.edu/about/ The inclusion of *local* crowd wisdom in innovation. [4whom, Dec 11 2007]
Neil's speech on Fablabs
http://www.ted.com/...ToJACFQ6hQwodFRAn-w Ian, you will love this. If you have not loved it already [4whom, Dec 11 2007]
..and here's one on stifling creativity. Probably more useful on the shortened curriculum post.
http://www.ted.com/...hp/talks/view/id/66 Funny, entertaining, and true, to a degree. [4whom, Dec 11 2007]
Please log in.
If you're not logged in,
you can see what this page
looks like, but you will
not be able to add anything.
Annotation:
|
| |
Yep, pretty much. It's sort of a way for the casual participant to play the same game, with more powerful tools than they might be used to, contributing to two outputs: robust ideas; novel methodologies. It might transpire that good ideas happen, but it might equally transpire that novel methodologies for idea-having come to the fore and become adopted by industry, if they're that good. |
|
| |
At the very least, it'd present a paradigm where functional ideas aren't necessarily always the burden and brainchild of a single personality, arrived at by some tortuous occluded haphazard round-the-houses uncontrollably creative route. |
|
| |
Will link to a great speech by the Centre of Bits and Atoms head, but for now, please see link. |
|
| |
Those fab labs look like an impressive initiative. |
|
| |
One line to take home from Neil's speech is: |
|
| |
"The other 5 billion people on the planet are not technology sinks, they are sources..." |
|
| |
There are already creative think tanks and industrywide R&D collaborations, I think you'll find. Their limitations are such because they are driven by a profit motive and the need to control ownership of the IP. |
|
| |
In addition, there are industry initiatives such as GNU software that fulfill your requirements, as far as I can tell. |
|
| |
Since this has nothing to do with halfbakery.com, you should probably move it out from under Halfbakery:. |
|
| |
Experimenting with different ways of generating ideas is something that designers and artists naturally do. And so's analyzing a problem. Yeah, bad designers can skip that, as can bad designers in the presence of lots of buzzwords and a website. |
|
| |
You sure like saying "methodology" a lot. |
|
| |
That's my current strategy. |
|
| |
Leverage it going forward, facilitating alignment of scopes within key stakeholder paradigms. |
|
| |
Bone on the grounds of the WIBNIness.. besides, that sounds like something from a science fiction novel. |
|
| |