Could a school yearbook test a much larger idea?

Melanie Perkins's account of Canva's origins begins with people trying to learn design software. While teaching design programs in Perth, she saw how long beginners took to become comfortable with the tools. Her response was an ambition to make design simpler and collaborative online. But an ambition to change design software did not identify a manageable first customer. The earlier business, Fusion Books, supplied one: schools whose staff and students needed to assemble a yearbook without becoming professional designers in the process.

In her published founder account, Perkins describes choosing yearbooks because the need was familiar and concrete. She and Cliff Obrecht worked from her mother's living room and arranged the development of an initial tool. The story is retrospective and belongs to the founder, so it should not be treated as an independent audit of every early decision. Its central sequence is nevertheless clear: start with a defined publishing task, enable the users to contribute, and connect their design work to a physical book that could actually be delivered.

That last step matters. A yearbook is not complete when a student has successfully moved an image on a screen. Contributions must be assembled, the layout must be acceptable, and the finished product must arrive. The context gave the team a way to learn about a whole job rather than a collection of attractive software features. A school also has a deadline and a group of people with different responsibilities. Making their work easier required more than reducing the number of buttons in a professional application.

A 2017 SBS interview provides a specific encounter that widened the opportunity. Perkins said Fusion Books customers asked whether they could also use the tool for newsletters, canteen menus, and other materials. This is an attributed customer-discovery account, not evidence that every school made the request or that those requests alone caused Canva's creation. It does show a useful signal: people were trying to apply the capability beyond the original product category. The existing solution had made another possible use easier for them to imagine.

The move toward Canva extended the proposition to broader visual communication. A 2019 Entrepreneur interview describes Fusion Books as the earlier test of that larger idea and reports the subsequent range of design uses. The important transition is from a particular artifact to a reusable capability. That expansion still required judgment. A request from a yearbook customer does not establish demand in every market. Different users may need different collaboration rules, formats, assets, commercial permissions, or standards of quality. Breadth creates new requirements as well as a larger potential audience.

The stakeholders clarify the original problem. A coordinator needed a finished book without an unmanageable workload. Students needed a way to contribute. Production partners needed files they could use. The founders needed a service people would pay for and a process they could deliver repeatedly. A tool that delighted one participant while creating trouble for the next would leave the job incomplete. Viewed this way, the early market was valuable because it connected usability to a visible outcome, not simply because it was small enough for a startup to enter.

The case suggests a disciplined way to hold a large ambition without requiring the first product to serve everyone. Choose a setting where the problem, participants, and completion criteria can be observed. Then pay attention when users try to carry the capability into adjacent work. That is a reason to investigate, not automatic permission to expand. Canva's later scale should not turn the earlier choice into a story of inevitability. The useful lesson is how a narrow task can generate evidence about a broader need while keeping the next decision grounded in what people are actually attempting to do.

For a discussion tailored to your team, explore a workshop with Julien.