The only page you need to bookmark 🙂 

Contains :

1. Links (which replace your bookmarks from Chrome)
2. Key Metrics (live), so you have them in front of you all the time
3. Work in Progress, cascading from OKRs to tickets
1. Current OKRs, so you have them in front of you all the time
2. Problems to solve now
3. Solutions in progress (Epics)
4. Experiments in progress
5. Tickets (Stories, bug fixes, tech debt) being built.

Classic Scrum/Kanban view with all the tickets in progress

✓ You can easily see if a ticket is blocking another one

✓ Check how your sprint is doing with the completion rate below the board

✓ All your tasks, bugs, user stories, technical debt

✓ Cool templates to standardize the writing and help your team not forget anything

✓ Management of dependencies, tickets ID, relations with sprints, epics, OKR etc.

An Epic is a big topic (in time or in impact) and a group of 🎟️ Tickets

👉 The completion rate is calculated with the storypoints of the 🎟️ Tickets already released

Connected to Epics and Tickets so

• your developers can climb the cascade from their daily tech tasks to the Company Goal associated
• your boss can see how his Company Goals are translated in tasks and when they’re released
• (included) +200 examples from great companies like Duolingo or Snapchat to help you design great OKRs

✓ Fuel of your team = exhaustive list of identified problems, feature ideas & opportunities from someone, someday

✓ You can ⬆️ Upvote an idea by adding your name into the "Upvotes" property

As an alternative way of navigating between problems, ideas and opportunities, you can also use the Opportunity Solution Tree framework which can be handy for brand new products.

An exhaustive list of documentation pages, along with their associated status (validated or not), so we know if it's trustworthy.

✔️ Document all your experiments: AB Tests, User Tests, Bêta Tests etc.

✔️ See all experiments in one place

• How to create OKR
• How many bug tickets should be added in a sprint
• and many more

Turn a feature idea into 3 reasons why this idea is terrible.

No more useless features!

“set up a Paypal integration so people don’t have to send there credit card or iban”

⚡ Powered by Marty Cagan’s way of creating features

Turn a large list of feedback into 5 actionnable key learnings.

Turn an Objective into Key Results & details plan on how to reach them.

⚡ Powered by Matt Mochary’s way of building OKR

Turn a problem into root cause and multiple easier sub-problems.

Turn a problem into creative and uncommon solutions.

Turn an idea into 10 alternate ideas that could solve the root-cause problem.

⚡ Powered by Marty Cagan’s way of brainstorming ideas

Your Brainstorming Sessions 100% on Notion, from problem identification all the way to solution.

⚡ Powered by Matt Mochary’s Brainstorming Method

Turn a project description into a list of things to test, split between Desirability, Usability and Tech assumptions.

⚡ Powered by Marty Cagan’s way of testing solutions

Turn a project description into a Pre-Mortem session: a prediction of why the project has been a failure after his release.

⚡ Powered by research from Deborah J. Mitchell (Wharton School), Jay Russo (Cornell), Nancy Pennington (University of Colorado)

Turn a project description into creative and detailed tests idea like “Fake door tests”, “AB Tests”, “Usability Tests” etc.

⚡ Powered by Marty Cagan’s way of testing solutions

Find the best Key Performance Indicator for your project.

⚡ Powered by Jesse Mawhinney’s blog from Hubspot

Create the description of a User Story with test scenarios from his name.

Turn an epic description into a list of small, independent, and prioritized tasks organized into batches.

Turn an Epic description into Press Release with your target’s tone of voice

Create product names from examples words

Startups are made to scale!

→ Each team has their own Product OS’ dashboards

→ All teams are linked to the same databases to keep it clean