Can You Crowdsource a Big Idea?

Bill Joy, co-founder of Sun Microsystems, famously said, “No matter who you are, most of the smartest people work for someone else.” This insight is almost a tagline for the rise of online distributed innovation, commonly referred to as “crowd sourcing.” A number of scholars at Harvard Business School have gotten in on the act, studying how crowds solve problems in new product development, scientific breakthroughs, and even trying to find the tomb of Genghis Khan. Recently, Nitin Nohria, Dean of HBS, challenged some of us to apply what we have learned to a core function of the school – generating relevant, rigorous knowledge.

Working with Professor Clayton Christensen on the research that became “The Capitalist’s Dilemma,” and taking a page from his book, we thought, How might we disrupt our own knowledge generation process? While HBS certainly has brilliant professors who are creating new knowledge, the mathematical truth is that there are more smart people outside of HBS than within it. We realized that we had a strong connection to an enormous untapped asset — the HBS alumni — and decided to formulate a “beta” challenge to test with the alumni of Clay’s course, Building and Sustaining a Successful Enterprise (BSSE in HBS-speak). We used the OI Engine software, dreamt up by Tom Hulme while he was studying at HBS and currently used for OpenIDEO, a diverse community that solves challenges with a social-impact focus. In one sense, this project was cutting edge, but it builds on really promising methods developed by organizations like the open source software community, the Wikipedia collective, TopCoder, OpenIDEO, General Electric, Siemens and NASA.

You can see the outcome of our challenge in this HBR article, as well as in an interactive exhibit showing how the process worked.

Here are some lessons we learned along the way.

Consider what your question assumes.

We invested considerable time in framing the challenge question, How do we innovate for long term growth and job creation? We could have opted for a simpler or broader question, but we hoped the tough challenge would pique the intellectual interest of community members. In hindsight, this set a significant hurdle to participation: we selected for people that understood the challenge, found value in it, and felt that they had something to add. While this resulted in high quality contributions, it also led to at least some selection bias. In this situation, we consciously accepted this trade off for reasons both substantive, like our desire to build on an existing knowledge base, and contextual, such as managing HBS’s inaugural foray into working collaboratively with the crowd.

Ask the right parts of your community.

We consciously decided that virtually all of the invited community would be alumni of the BSSE course at HBS, both because they shared a common intellectual framework and because we believed they would be more likely to answer a call to action from Clay. While our ultimate goal is to tap a broader group, research suggests that starting with a small, connected community is the best way to seed a thriving community.

Set norms for contributions early.

We quickly observed what we called a “culture of composed contribution”; people did not seem comfortable thinking aloud (as it were) in front of the community. This response was in marked contrast with other open source situations, but very much in line with HBS culture. The general reluctance to contribute imperfectly finished thoughts created a significant barrier to entry; we suspect that it discouraged creative but less developed ideas that could have pushed thinking, been more open to refinement, and served to build ties among participants. Next time, we might deliberately contribute less refined ideas at first, to convey their acceptability and usefulness.

Get people up to speed.

As the infographic reveals, our collective thinking evolved over time; while many early ideas shaped the article directly, other ideas sparked others’ thinking, sometimes weeks later. Given our time-poor community, this made urgent the challenge of bringing community members up to speed. (The site generated an extraordinary amount of material.) Our solution was to offer accessible building blocks of the conversation. We featured contributions that we thought would give the users a soft re-entry into the challenge and sent summary newsletters to the community outlining some key activities on the platform.

Keep them coming back.

Our colleagues in the HBS Digital Initiative have studied the construction of online communities; they often begin as small, passionate, and densely populated, then later become a collection of interlinked communities. We hope to pull a much larger group in to our discussions in the future and otherwise explore how to bring the crowd into all aspects of our mission. (A continuation of the work done on Capitalist’s Dilemma appears at this site – please join in.)

In a more general sense, we intend to continue exploring how “the crowd” can contribute to academic work, how together we can deepen our understanding of complex, hard-to-solve problems, and how – maybe, just maybe – we can contribute to solving those problems. With that in mind, we would love to read your feedback on this process and thoughts in the comments below on what other challenges the community might take on.

Can You Crowdsource a Big Idea?

Research & References of Can You Crowdsource a Big Idea?|A&C Accounting And Tax Services
Source

error: Content is protected !!