Notion: let customers show what the product makes possible

Notion’s template marketplace illustrates how customer expertise can become a practical starting point for other users, while giving contributors a reason to keep building useful work.

A flexible product can be difficult to explain because its possibilities exceed any single demonstration. The blank canvas promises freedom, but a new user may experience it as another task to figure out.

Customer-created examples can make that possibility concrete. They show a real workflow in a form another person can adapt, shortening the distance between understanding a product and doing something useful with it.

Notion’s template marketplace provides a documented example of this mechanism. The case is about participation and product explanation, not a claim that templates independently caused the company’s growth.

The exchange is practical

Notion’s creator page describes templates as reusable pages or sets of pages that users can duplicate and customise. It also offers creators a route to publish and sell their work.

That creates two different reasons to participate. A user can find a starting point for a task. A creator can share expertise and potentially earn revenue from a useful implementation.

The company’s marketplace selection guidance includes specific user value and build quality among its criteria. A contribution is therefore more than a public statement of enthusiasm for the brand.

These materials describe the programme’s visible design. They do not establish typical creator earnings, adoption lift or the quality of every template. Those outcomes would require separate evidence and should not be inferred from the existence of the marketplace.

Make the first useful action easier

Consider a hypothetical team adopting a flexible planning tool. A general feature tour explains databases, views and permissions. A relevant project template can demonstrate how those pieces work together for a recognisable job.

The value lies in reducing setup decisions while leaving room for adaptation. Too little structure leaves the user stranded; too much complexity creates another system they must learn before doing their actual work.

A CMO should ask which recurring customer task produces this problem. A sample brief, calculation worksheet, configuration guide or operating checklist may provide the same kind of practical bridge in another category.

Start with the user’s job rather than the product’s most impressive capability. An elaborate showcase can attract attention without helping someone reach a meaningful first result.

Let expertise travel with the example

A reusable asset needs context. Explain who it serves, which assumptions it makes and what the user must change. Include example inputs that demonstrate the intended workflow without exposing private customer information.

For a hypothetical onboarding checklist, the creator might identify team size, required approvals and the point at which the checklist is complete. Those details make the asset easier to evaluate before someone invests time in it.

Show the contributor’s role and expertise accurately. A customer who built something useful should receive clear credit, but their participation should not imply endorsement of every product claim the company makes elsewhere.

The brand also needs a way to distinguish maintained examples from abandoned ones. A template can continue to circulate after the product or workflow it assumes has changed.

Design for both sides of participation

The contributor needs to understand the exchange. Possible benefits include payment, recognition, learning, useful feedback or access to an audience. Name the actual benefit instead of assuming that exposure is sufficient compensation.

Make the effort visible as well. An invitation that starts with “share your workflow” can quietly expand into interviews, revisions, screenshots and ongoing support. That is a different commitment and should be discussed honestly.

For users, explain what happens after adoption. Is the asset a starting point they maintain themselves? Does its creator provide support? Is there an update route? Avoid making the marketplace appear simpler by leaving those expectations unresolved.

Measure use beyond collection

Downloads and duplications indicate interest or acquisition of an asset. They do not establish that the user completed the intended job or remained active in the product.

Define a small set of meaningful adoption signals appropriate to your business. A user might finish setup, invite colleagues or complete a workflow. Observe whether the example helps with that step, while recognising that people selecting templates may already differ from other users.

Gather qualitative feedback too. Where did users hesitate? What did they remove? Which instructions were missing? Those findings can improve both the contribution programme and the product’s standard onboarding.

Build a library people can navigate

Organise examples by user tasks and constraints, not only by internal product categories. Someone trying to plan a hiring process should not need to know your feature vocabulary to find a useful starting point.

Keep discovery selective enough that a new user is not confronted with hundreds of indistinguishable options. Explain meaningful differences between a simple starting template and an advanced implementation.

The broader lesson is that community participation becomes stronger when it produces something another person can use. The contribution explains the product, the creator receives a defined benefit and the user reaches a practical next step.

That exchange deserves ongoing operational support. A growing library is an asset only while its contents remain findable, understandable and useful to the people the product is meant to serve.