> 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     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.deepwork.studio/teams-departments/deep-work-studio/roles/user-researcher/researcher-skill-tree/quick-fixes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.