LEGO Ideas: Make Participation a Clear Review Process

Read the campaign story

LEGO’s official history traces the programme to a 2008 Japanese experiment with CUUSOO, followed by international expansion in 2011. Fans proposed products and gathered support before a LEGO review. The platform became LEGO Ideas in 2014. Contemporary Brickset reporting documents that transition and the introduction of time limits. This study treats the pilot, renamed platform and subsequent products as one programme family, rather than counting each fan-designed set as a separate campaign.

The mechanism gives participation a defined destination: consideration by the company. Support is not itself a promise that a proposal will be manufactured. LEGO’s history records examples that became products, but those selected examples cannot establish typical contributor success or incremental commercial return. The historical rules have also changed over time. This case examines the relationship between community interest and professional review, not current submission instructions or guaranteed eligibility.

Editorial interpretation: the programme gives enthusiastic users a role that is more substantial than reacting to an advertisement. A proposal makes their interest visible, and gathering support creates a reason to explain the idea to others. The brand receives structured signals about what people find appealing. Those signals remain partial: an enthusiastic supporter is not necessarily a buyer at the final price, and a popular concept may be difficult to produce responsibly.

The review stage therefore carries much of the programme’s credibility. Participants need to know what the company is deciding and why a promising idea may not proceed. Clear boundaries can preserve trust even when the answer is no. An adaptation should avoid presenting community voting as a democratic guarantee if the organisation must still consider safety, rights, cost, manufacturing or portfolio constraints.

Define what support actually earns

Before inviting submissions, describe the stages and the decision at each one. A threshold might earn a review, a prototype discussion or feedback, but these are not interchangeable promises. Make the limits understandable without requiring participants to infer them from examples of past winners. Test whether a prospective contributor can explain what happens after reaching the threshold and what remains uncertain about a possible release.

Make the request proportionate to the opportunity

Creating and promoting an idea takes time. Ask only for detail needed at the relevant stage, and explain rights and compensation arrangements before substantial work begins. Do not use an open call to obtain finished professional work under vague exposure promises. Provide a way to withdraw where appropriate and explain how rejected material is handled. A community programme should respect contributors who are not selected as well as celebrate those who are.

Use popularity as one input rather than a demand forecast

Separate the number of supporters from evidence about price, repeat use and practical feasibility. Look for duplicate or coordinated signals without treating unfamiliar ideas as inherently suspicious. Review whether contributors with large existing audiences have an advantage unrelated to product merit. Complement visible support with appropriate research and technical evaluation, then communicate the result without claiming that the crowd has settled every commercial question.

A small test for another brief

A small craft business invites adult customers to suggest one practical accessory concept, with a published review process and a modest paid prototype commission for any selected contributor.

Measure proposal clarity, review completion, participant understanding and prototype usefulness. Keep votes, intent and actual purchase evidence distinct.

Pause if contributors misunderstand the opportunity, rights are unresolved or the business cannot honour its review commitments.

• State what information is needed and what review promises.
• Explain selection, rights, compensation and rejection handling before accepting ideas.
• Evaluate feasibility and buyer interest separately from public support.