<aside> ❗ Strategy: don't try to make Polygloss a lot better, but to make Polygloss a bit better many times.

</aside>

It might be difficult to know what could add value to Polygloss and our users. Feel free to create cards not just for planned work that come out of discussions among the team, but also for ideas you find interesting, player requests, bugs you found, etc. After that, any member can decide if something already in the board is worth being prioritized and started. Prioritizing some work should be backed up by some reasonable explanation or process. Some examples:

<aside> ⚠️ If you are unsure, a good rule of thumb is to ask the opinion from one other team member before making any decisions related to the project such as starting to work on a card or spending money from the budget. This is a simple check to see if you are going in the right direction and it will help avoid re-works. A full team review or unanimous approval is usually unnecessary and too slow for most situations.

</aside>

• you conducted a survey with players, noticed that a certain feature is frequently requested, and considered it to align well with our values and mission
• you just know that it is a good idea and you can clearly explain why to 1 other team member who agrees
• there was a meeting or discussion where there was an agreement that that work should be conducted next

Some questions you can answer when trying to elaborate on how important a card is:

• What kind value does this task add? (monetization, learning experience, community growth, etc...)
• How fast can this task start adding value?
• Can I break the task into sub-parts and start with something that is simpler and also adds some value?
• What is the goal of the card? Is there a different work that is a lot simpler and reaches similar goals?