Melanie Perkins and Canva: Making a Complex Skill Accessible to More People

Before Canva, professional design software already offered powerful capabilities. The barrier for many people was the expertise and time needed to use those tools. A student, small business owner or community organiser might need a poster, presentation or social graphic but could not justify learning a complex application for one task. Melanie Perkins’s Canva story is therefore not simply about putting design online. It is about lowering the skill threshold for a useful outcome.

Canva’s own reflections on its early journey describe the founders’ focus on making design more accessible. Company accounts are useful for understanding the intended product philosophy, while claims about market impact should be evaluated alongside actual user behaviour and independent evidence. The strategic mechanism is clear: templates, guided choices and browser-based workflows can reduce the number of decisions a beginner must make before creating something useful.

A new user does not judge a design tool by the full list of features. They judge it by whether they can complete a task. If the first session ends in confusion, the product’s advanced capabilities may never matter. The key product metric is therefore not just feature availability but time to first successful outcome.

Templates lower the initial cognitive burden by providing structure. Drag-and-drop editing makes some actions visible. Shared assets and collaboration reduce the effort of coordinating with others. The product can then reveal more advanced capabilities as the user’s needs grow. This is a form of progressive disclosure: beginners see enough to succeed, while experienced users can access more control.

The trade-off is that templates can make work look generic or constrain skilled users. A tool designed only for beginners may frustrate people who need precision, brand systems or unusual layouts. Accessibility should mean that more people can achieve a good result, not that every user is forced into the same result.

A beginner-friendly interface is not achieved by hiding every advanced option. It requires a coherent model of how the product works. Users should understand what they can change, how to undo a mistake, how elements relate and how their work will behave when exported or shared. If a simple interface conceals unpredictable rules, the user may succeed once but struggle to repeat the result.

Founders should map the user journey from first attempt to repeated use. Which tasks must be easy immediately? Which capabilities can be introduced later? Where do novices get stuck? Where do experts hit limits? A strong product can offer a simple entry point without creating a dead end as skills develop.

This lesson applies to financial software, analytics, website builders and AI tools. A product can expose powerful capability through defaults, examples and guided workflows. But the defaults must be safe and sensible, and the user must retain control when the task requires judgement.

A template encodes prior decisions about layout, hierarchy, colour and spacing. That helps novices avoid starting from a blank page. It also creates a library of reusable starting points, which can improve speed and consistency across a team. In this sense, templates are not merely content; they are part of the product’s capability system.

Yet templates can encourage sameness. If every user begins from the same set of patterns, outputs may converge visually. A template may also imply that a layout is appropriate when it does not fit the audience, accessibility needs or message. The product should help users understand the template’s purpose and adapt it rather than treating the default as the answer.

For founders, the question is which expert knowledge can be encoded into reusable defaults without erasing context. Templates are strongest when they reduce avoidable decisions while leaving important decisions visible.

Design work often involves more than one person. A file is created, shared, reviewed, revised and exported. Collaboration can make the product spread through ordinary work: a user invites a colleague, who experiences the tool and may use it for another task. But collaboration also creates requirements for permissions, version history, comments, asset consistency and reliable exports.

Product-led distribution works only if the collaborative experience is good enough to protect the core promise. A shared document that loses formatting or exposes the wrong permissions can damage trust. Growth loops should therefore be evaluated alongside the operational work they create.

Measure invitation acceptance, collaborative completion, repeat creation, export success and retention by team size. Do not assume that a high number of shared links means the product is becoming indispensable.

Making design accessible can also mean reducing cost, allowing collaboration across locations, providing templates for unfamiliar formats and supporting users who do not have a dedicated design team. But the company must be careful not to equate ease of use with universal accessibility. People have different language, visual, motor, cognitive and device constraints. A product should be tested with varied users and support meaningful controls where the work demands them.

The product also needs to help users avoid misleading or low-quality outputs. A template can make an attractive design easier, but it cannot guarantee that the content is accurate, readable or appropriate. Design tools should support the human judgement that remains necessary.

Ask: What meaningful task can a new user complete in the first session? How long does it take? Which decisions can be safely handled by defaults? Which decisions require user understanding? Where do templates help, and where do they constrain? Can experienced users reach advanced controls without confusing beginners? Do collaboration and export work reliably? Which groups struggle with the current interface? What evidence would show that the product has become easier without becoming less capable?

Run usability tests with people who have never used the product. Observe behaviour rather than asking only whether they liked it. Measure task completion, error rates, time to outcome, return use and support needs. A user who says the product is easy but cannot finish the task has given a different signal from a user who completes the task without assistance.

Canva’s story illustrates a powerful product strategy: do not require every customer to become an expert before they can receive value from a tool. Encode useful starting points, make the first success attainable and let capability grow with the user. The challenge is to avoid turning accessibility into a ceiling.

For founders, the key question is “What expertise can our product make available to a beginner without hiding the decisions that still matter?”

A product team can claim that its tool is for everyone while testing primarily with experienced users, modern devices and one language. Real accessibility requires evidence from people with different skills, devices, abilities and contexts. It also requires attention to what happens when the output leaves the editor: a design may look good on screen but be unreadable, inaccessible or poorly formatted when printed or shared.

Build a research panel that includes novice and advanced users. Observe task completion rather than relying only on preference surveys. Test keyboard navigation, contrast, text scaling, export formats and collaboration permissions where relevant. Use the findings to prioritise improvements and publish clear limitations where the product cannot yet support a use case well.

Reducing time to first useful outcome can improve activation, but activation alone is not the final goal. A user may create one attractive graphic and never return. The company should examine whether the product becomes part of a recurring workflow, whether users can develop their skills and whether teams can reuse assets without creating inconsistency.

Track first-task success, repeat creation, collaboration, export reliability, retention and support burden by user skill level. If novices succeed but experts leave, the product may need a clearer growth path. If experts succeed but novices abandon, the entry experience may be too demanding. The objective is not to choose one group; it is to make the journey between beginner and capable user intentional.

A design tool can be easy to use and still produce an inaccessible result. Small text, weak contrast, unclear hierarchy or an export that breaks layout can make the finished design ineffective for its audience. Product quality must therefore be evaluated across creation, collaboration, export and actual use - not only inside the editor.

Give users guidance where a common mistake has meaningful consequences. Test output on different devices and formats, and provide checks for contrast, text readability and layout where feasible. Do not imply that a template automatically makes content accessible or accurate. Defaults should make good practice easier, while leaving responsibility for the message with the person creating it.

Measure whether users move from first success to repeated work, from individual work to collaboration and from templates to confident customisation. If many users stop after one task, ask whether the tool solved a one-time problem or failed to become part of a routine. If teams collaborate but exports fail, the product’s sharing loop may be creating demand that operations cannot support.

The distinctive lesson is to design a path from novice to capable user. Accessibility creates the first opening; a coherent learning curve creates the long-term relationship.

A template library can become a major product asset, but its size is not the same as its quality. Templates should be relevant, adaptable, well organised and appropriate for the tasks users actually perform. Poorly structured templates create more work than they remove, while low-quality content can undermine the trust users place in the tool.

Measure template reuse, editing depth, completion rates and user corrections. Review whether the library serves different skill levels and use cases without becoming confusing. Treat curation as product work: the goal is not the largest possible catalogue but a set of starting points that helps people produce better work more confidently.

Templates and defaults reduce effort, but the tool should not imply that every default is right for every situation. A presentation for a classroom, a fundraising deck and a safety instruction sheet may require different hierarchy, contrast, tone and evidence. The product can guide users toward common good practices while helping them recognise when context matters.

A useful approach is to combine defaults with lightweight explanation. Show why a layout works, warn when text is difficult to read or a design is likely to fail in a particular format, and make it easy to adjust the result. This turns the product from a template catalogue into a learning environment.

For founders, the broader lesson is that accessibility and expertise can reinforce each other. A good tool lowers the cost of getting started and gradually helps users understand the decisions that make their work effective.

*

• About Canva - About Canva - Canva
• Melanie Perkins on building Canva - Melanie Perkins on building Canva - Entrepreneur
• 21 Questions from Canva's 10-year journey: Part Two - Founder/company reflection on Canva's development and lessons.

Editorial status: private research draft. The featured photograph is a real-photo candidate, but direct-file availability, rights, credit requirements, and a second distinct article image must be verified before publication. No interviews or private founder experiences are claimed.*

• How to Position Your Business So the Right Buyer Understands It
• Trust Before Attention: Build Signals Buyers Can Verify