> For the complete documentation index, see [llms.txt](https://docs.deepwork.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwork.studio/teams-departments/deep-work-studio/roles/user-researcher/researcher-skill-tree/quick-fixes.md).

# Quick Fixes

**Quick Fixes are minor UI changes or additions that affect the product's UX and usability, such as:**

* Copy change: e.g., labels, headlines, paragraphs
* Text and number legibility: e.g., small characters, low contrast, number separators, alignment
* Contextual helpers: e.g., tooltips, helper text, links
* Visual cues: e.g., arrows, icons, colour change

{% hint style="warning" %}
 High-level strategic or conceptual issues are **not** Quick Fixes.
{% endhint %}

#### When to share them?

* Quick Fixes are discussed in a 30-minute scheduled call between the User Researcher and Product Designer the day after the user research sessions.
* If they prefer and agree beforehand, this can be an async video recording posted in the project's Discord channel by the User Researcher.

{% hint style="info" %}
As a User Researcher, the earlier you share these, the better. Consider that the Product Designer has a 4-hour working day to work on the Quick Fixes before the client presentation and design hand-over.
{% endhint %}

#### How to include them in the presentation?

| Presentation order  | What to present?                                                    | Time cap      |
| ------------------- | ------------------------------------------------------------------- | ------------- |
| 1. Product Designer | User-tested prototype                                               | 10-15 minutes |
| 2. User Researcher  | Minor issues (Quick Fixes) and high-level strategic recommendations | 15-20 minutes |
| 3. Product Designer | Prototype with the Quick Fixes included                             | 2 minutes     |