I'd like submit the following workflow for transforming an idea into a profitable business. Please "crowsdsource" it!

Bold items in the abstract are what I consider "features."

Abstract:
The workflow funnels through iterative phases. People subscribe into project categories and choose the roles in which they want to participate. The idea moves through the workflow (through email/messaging) and subscribers collaborate according to their roles and phases. If within a specified phase an “idea” doesn’t pass rankings (based on predefined criteria) or idles, then the project is kicked back to the author (or expires).

Iterations:

- Problem and solution Definition
Questions: What is the problem? What is the solution? for whom? What category? Does it already exist? (CH and otherwise.)
Roles: Author, Idea critics, solution seekers
Comments: Take your time. Focus on the problem. Decide whether your idea is right for CH/crowd-sourcing, as you must consider giving up full ownership. Decide how you want to compensate subscribers. Use forums and idea wars to get it going. When done, submit it through “the funnel.” Note that the first few steps are synchronous and you may have to wait in line.


- Mindset
Questions: Is it interesting to you? Would I work on this project?
Roles: contributors, such as project managers, designers, developers
Comments: Only projects that are interesting enough need to move to the next phase. Interest is subjective and includes compensation terms and general interests.

- Business
Questions: Can it be profitable? Is competition manageable?
Roles: Marketers
Comments: Concentrate only on business criteria

- Funding
Question: Would you put your own money up front to kick it off? How is profit distributed?
Roles: Investors, contributors
Comment: No commitment required by investors, but we pitch better knowing there is a good business case.

- Project
Questions: how, who, what, when, where?
Roles: contributors, investors
Comment: Crowd-sourcing should follow open source model of execution.

- Construction iterations See: http://en.wikipedia....software_development
Questions: Status? Do we still have the resources and funds? Are we on time? what are the artifacts between
Roles: contributors, investors
Comment: data models, prototypes, art, docs, etc.

- Release and Post Mortem
Questions: What did we do wrong? How could we do it better for the next project?
Roles: everyone in project
Comments: Rate subscriber anonymously!

BTW, don't expect me to defend or prototype this

/ooper
http://www.socialthumbs.com

Posted: March 4, 2008, 9:43 pm

Ooper,
Thansk for sharing your thoughts.
Do yo usee this as something for CH3?
Tommy

Posted: March 5, 2008, 12:43 am

Vanhees, I would hope so.

All,

What category of solutions would interest you? Which roles would you play?

/ooper
http://www.socialthumbs.com

Posted: March 5, 2008, 1:19 am

I wanted to re-emphasize the need for contributors to be ranked anonymously by others. It's the only way for projects to produce quality and timely releases.

Posted: March 6, 2008, 6:28 pm

On March 6, 2008, 7:28 pm ooper said:

I wanted to re-emphasize the need for contributors to be ranked anonymously by others. It's the only way for projects to produce quality and timely releases.

Agreed.

Posted: March 6, 2008, 7:23 pm