# How To Figure Out What's Not Working

## 10 Steps of Design Debugging

Sometimes at the end of the day, we just can't get sh\*t to work. It's okay, things happen. Here's the basics of how to fix any type of problem, big or small. 

1. Make sure player onboarding is aligned to the actions that are necessary to navigate the app successfully
2. Perform usability testing on **both** new and experienced users to find places they struggle with the application or experience (remember to note buttons/locations/actions they also are unaware of existing, as this is important)
3. Create a diagram ([information architecture](https://www.toptal.com/designers/ia/guide-to-information-architecture)) of all content available in the app and how players navigate through the content or options
4. List the features, buttons, or actions within this [information architecture](https://www.toptal.com/designers/ia/guide-to-information-architecture) (if you struggle with this, feel free to look at the link above)
5. Find what is the most easily forgettable in the experience that is also incredibly important (these tend to be dynamic tasks) and potentially make a separate reminder
6. The most important features, buttons, or actions should be the most accessible and upfront components of your app
7. The rest of the features should be organized in a way that makes them useful as players may need them, or in a location that is useful to the content's function
8. The most detrimental features, buttons, or actions should either be deprioritized into a safer location (i.e. away from commonly used buttons or repeated actions), or should have an extra point of friction like a confirmation popup
9. Break down easily forgettable and dynamic tasks into repeatable, simpler actions that grow in complexity over time (this can also afford mastery)
10. Prototype this reorganization of content, researching new ways to convey context (visual, audio, haptic), and repeatedly test on new and experienced users


---

# Agent Instructions: 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:

```
GET https://aliheston.gitbook.io/the-design-of-virtual-and-augmented-reality/by-definition-doing-too-much/how-to-figure-out-whats-not-working.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.