If I worked for Notion, here is the list of things that will be in my backlog and this is how I will go about writing a feature brief for leadership...
Assumptions
Usage data of 60% of Notion customers using the "Share to web" feature.
The core reasons they share to web
User persona for the people that share to web the most.
Notion's desktop application is written in Electron JS
List of features
The three features that will be in my backlog will include:
"Share to the web" Analytics.
Writing assistance that reviews spelling, grammar, punctuation and clarity. Integration with tools such as Grammarly, Hemingway etc.
Board view flexibility.
Prioritisation technique
I will prioritise using the MoSCoW (MUST HAVE, SHOULD HAVE, COULD HAVE and WOULD HAVE) framework by prioritising the "Share to the web" analytics feature. It is for an already existing feature that requires this optimisation. Analytics for things that involves sharing to the web is a must-have. Share to the web analytics also provides a much better ROI vs the effort required compared to the remaining two features.
Feature brief for the leadership team
Introduction
The share to web function has seen a surge in usage after the launch of this feature. A lot of our customers use the feature to share things from ideas to a job description and even use it as a way to create and manage their portfolio.
Here is what we know-
About 60% of customers use the "Share to web" feature.
The "Share to the web" feature is a feature that a lot of customers have different use cases for.
It is important to the customers
Notion customers share to the web so that they can-
Build a portfolio
Share documentation information with a group of individuals.
Share job descriptions
Share a public roadmap.
Build landing pages for their waitlist.
The problem
These customers do not have any data to be able to measure the success or consumption of whatever content they have shared via the web using Notion. Lack of access to this data leads to a lot of uninformed decisions on actions to carry out.
Our Solution
We will fix this problem by adding basic analytics to the pages shared by allowing our customers access to data on their pages. It will include collecting information about:
Number of views
Most viewed location: This describes the locations where the majority of their views are coming from.
Link clicks: This describes the number of times links within the pages was clicked and accessed by visitors.
Example use cases
An HR lead can measure inbound interest from candidates vs the number of applications they have received when they post job applications via Notion pages using the "Share to the web" feature.
A partnership PM for a product needs to confirm if a partner has gone through the documentation so that they can follow up accordingly.
A product designer who has set up his portfolio on Notion and needs to check the number of views he/she has received after sharing their case study on an animal care product they were working on.
Timeline
We hope to launch the first version/iteration of this feature 4 weeks after the engineering team has received the PRD.
Success metrics
Number of shared pages with analytics set up
Number of customers that view the analytics dashboard
Number of subscribers that use the analytics feature- This will feed into the decision to probably make this a paid feature that has a free element (A limit to the free section)
Stay tuned for the engineering PRD for this feature…