Design Challenge: Give a Blank Canvas a Bounded Brief

Read the campaign story

Canva’s Design Challenge programme uses a recurring brief to prompt people to create with its design tools. Its official page describes themes, a public hashtag submission route and a showcase of selected entries. Archived examples include an avatar, a postcard and a process-diagram poster. These are treated here as iterations within one programme, not separate campaigns added to the case count. The opened records do not establish a reliable original launch year.

The official terms describe eligibility, skill-based selection and rights associated with entering. At the time of review, the programme page also displayed a notice that no challenge was currently available, alongside older example dates. This study therefore examines the documented mechanism rather than telling readers that a contest is open now. It does not infer user growth, design proficiency or paid conversion from the existence of submitted work or a gallery of winners.

Editorial interpretation: a blank canvas can be a difficult invitation. A small brief supplies a starting point and a reason to finish something, while leaving room for individual decisions. Seeing other responses can broaden a participant’s sense of what the tool can do. The value depends on a task that feels achievable and meaningful, not merely on producing a large volume of branded posts for the organiser.

Competition changes the experience as well as adding excitement. A public showcase may encourage participation, but it can also make beginners feel that only highly polished work belongs. An adaptation should provide value to people who are not selected and explain judging criteria before work begins. It should also distinguish a learning invitation from a request for commercial creative work that would normally deserve an agreed fee.

Choose a brief that teaches through making

Define one practical design problem with enough constraints to help someone begin. Keep the task small enough to complete without specialist equipment or an unreasonable time investment. Offer guidance that explains decisions rather than requiring participants to imitate a model. A good prompt lets people make different valid choices and understand what they learned, even if they never post the result publicly.

Design recognition for more than the winners

Consider how entrants receive useful acknowledgement, feedback or access to learning without promising individual critique the team cannot deliver. Explain how featured examples are selected and avoid presenting aesthetic preference as a universal ranking of talent. Include work that demonstrates a clear idea or thoughtful solution, not only advanced production polish. The community should feel like a place to practise rather than a constant audition for approval.

Make rights and participation costs visible

State what the organiser may do with entries and what participants retain before they invest time. Use appropriately reviewed rules and a clear route for questions. Do not assume a public hashtag grants unlimited permission for advertising, and do not use a challenge to obtain client-ready work without fair terms. Review whether people need to reveal personal information or change account privacy simply to take part in the proposed experience.

A small test for another brief

A small software community offers a voluntary practice prompt using a fictional brief, with a private participation option and a rights-clear showcase.

Measure comprehension, task completion, perceived usefulness and voluntary return. Separate public posts from learning or commercial outcomes.

Pause if people misunderstand rights, face disproportionate effort or believe unpaid work is required for access to a paid opportunity.

• Choose one bounded skill and provide a useful starting explanation.
• State eligibility, any rewards, selection criteria and content-use terms before submission.
• Offer a learning resource that benefits participants whether or not their work is featured.