<aside> 👥 Responsible team members: Role: @someone, Role: @someone

</aside>

<aside> 📒 Related specs: 🔗 Type plus @@ to link to a notion doc

</aside>

<aside> 💬 Discussion in Team communication app: 🔗 Link to channel

</aside>

<aside> 🚦 Status: Early 🌱 In Progress 🔨 Finished ⭐

</aside>

Goal

This document aims to outline pain-points about what's your user pain-point? and support our company values.

Describe how will your product support our company values

Company valuest listed here

<aside> ℹ️ Note: The numbering is added for legibility, not priority. After discussions we could think about reordering and prioritizing.

</aside>

Priority table (to discuss/reorder)

List all features in the following table:

Priority Table

01 – Add the first feature name

<aside> 🌊 Impact: Is it a feature that is potentially used every day and essential, a must-have to stay competitive or just a nice-to-have?

Describe the potential impact with hashtags like #high, #medium, #low, #everyday_use, #communication_improvement, #growth

</aside>

<aside> 💊 Pain-point: Analysis from customer support tickets, a feedback forum or user research sessions, feedback from the support team, internal team feedback. Describe all the current pain points of this particular problem.

</aside>

<aside> 💡 Solution: What concrete changes are needed? How could a potential solution look like? Describe the potential solution. Link to design exploration (if available) Link to user research documentation (if available)

</aside>

Timeline

Include a timeframe for the milestones – like tentative release dates, mark timeframes for quarters like Q1, Q2… or other kind of milestones to keep the momentum of the development flowing: