<aside> <img src="/icons/book-closed_gray.svg" alt="/icons/book-closed_gray.svg" width="40px" /> How to use this document: If you are a Notion user, duplicate it as a template. If not a Notion user, copy/paste the content on your favourite writing tool.

</aside>

Product Main Goals

<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" /> After the kickoff session, we draft a high-level definition of the main problem to solve & the key opportunities to capture with this new digital product. This step is not about super detailed specs; it's about understanding what's the main goal and why it's important to achieve it.

</aside>

Ideation Bucket

<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" /> With the right context, it's time to explore potential solutions for the detected needs and opportunities. This step is about discussing the details of the considered features through question banks or how-might-we definitions.

</aside>

Feature List Proposal

<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" /> This is the first high-level definition of the product roadmap and project scope. We can include features that may be deprioritized later. From here, we will be in a perfect place to start working on the Feature List and Blockframes.

</aside>

[High-Level Categorization (e.g. Contact Management)]

[Feature Name (e.g. Share Contact)]

Description of User Need

[Describe the need we’re trying to meet ideally with the user story format.]

Potential Solution

[Describe how we could solve the problem or capture the opportunity.]

Requirements

[Outline low-level definition of specific requirements detected for this feature.]

Assumptions, Constraints & Dependencies.

[Describe externalities that would enable or limit the potential solution.]

Open Questions

[List here the doubts we need to discuss to refine the solution proposed.]