### **Problem**

We get valuable feedback from users through support and sales channels. They can be from a current user, a former one or someone who's recently cancelled a plan. Apart from feedback concerning pricing, internal decisions or procurement, they tend to fall in one of these categories:

* feature requests
* bugs
* UX issues

We have a system in place to track feature requests (with votes) and report bugs, but nothing for UX issues that are neither feature requests or explicit Begin of the insertionbugs.End of the insertion Begin of the deletion bugs. End of the deletion

Begin of the insertionSometimes, feedback concerns multiple features/bugs, and is harder to pin to one particular thing. And when this feedback is in Odoo, it's hard to follow-up with it in an actionable manner, because the feedback concerns _usage_ rather than individual features. (Often after on-boarding).

End of the insertion Examples of such feedback are:

* Incomprehension around a certain design element or feature (what does this do?)
* Difficulty using a feature (too small, too hidden, too slow...)
* Lack of discoverability or feedback of a certain feature
* Cumbersome experience

**The feedback is often shared on Element or on our weeklies, but they are not always tracked and or even structured for them to be actionable.**

###

### **Goal**

Direct feedback is extremely valuable. Our goal is to:

* **improve how we collect and channel user feedback** concerning UX optimisations
* **improve our internal process** to track and prioritise Begin of the insertionthemEnd of the insertion Begin of the deletion them End of the deletion
* **commit to addressing high-value feedback** to continuously improve Begin of the insertionOpenProject

End of the insertion Begin of the deletion OpenProject 



End of the deletion ### **Proposal**

We propose treating UX optimisations similarly to bugs and features, and introducing a process to help channel, track and respond to feedback:

* **Create a new type in Community called "UX optimisation"** or simply "UX" with this structure: Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion * UX issue in one paragraph
* Source: user feedback, personal experience...
* Details (ex: copy/paste user Begin of the insertionfeedback), or summarise manually
* Odoo ID (or link? privacy), also tag "feedback" on Odoo so that the Sales team will then also prepare meetings to share relevant feedback.End of the insertion Begin of the deletion feedback)End of the deletion
* Related features or bugs (if any)
* UX optimisation (from Design team)
* **Create a wishlist-like version** for such optimisations, like "Known UX issues". Once a UX issue is "confirmed" by the UX/Design team, it goes into this pool
* **We commit to addressing at least one UX optimisation per release**
* We can take on more if there are sufficient resources
* For urgent optimisations, we can take them on in point releases and patches
* **Optionally, a system of votes** imilar to features can be implemented should we find that multiple users report the same issue Begin of the insertion

End of the insertion Begin of the deletion



End of the deletion The Design/UX team will be responsible for prioritising UX optimisations and, along with the dev team, deciding which ones to add to a certain version during version scope planning. Begin of the insertion

### **Open questions**

* Sometimes hard to distinguish between Feature and Optimisation. 
* Communicate problem maybe?
* Workflow: Once feedback is gathered and structured, what next? How do we turn it into something devs can respond?
* **Proposal**: When we add it to a release, then Design team comes up with a proposal (specs + mockup if necessary) and then we treat it similar to a feature.End of the insertion