> For the complete documentation index, see [llms.txt](https://outdraw-academy.gitbook.io/become-a-ux-designer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://outdraw-academy.gitbook.io/become-a-ux-designer/roadmap/month-4-design-products.md).

# 🚀 Month 4: Design products

This time, you need to develop an idea for a product, solve all the problems, design interactions and flows, and create a design system.

## Coming up with a design brief

{% hint style="info" %}
I have a full lesson on how to come up with design briefs for your portfolio projects in my [Free 5-Day Portfolio Masterclass](https://www.outdraw.academy/courses/portfolio-masterclass).
{% endhint %}

To come up with a design brief for your project, you can go with one of those two approaches:

### #1: Solve a problem that you see in the world

Find a solution to an issue that bothers you personally in your everyday life. I recommend that it's something well-known to you. At this point in your design journey, exploring an entirely new and difficult topic, like an app for doctors or programmers, would be overwhelming.

### #2: Solve the same problem as another product but better

For example: Let’s say you’re using a fitness app with videos on demand, but you don’t like that videos from all levels are all mixed together. It’s hard to navigate and track your progress. You can design an app with a proprietary fitness level score system that leads users through video choices based on their level.

To do it properly, you need to really know the niche and have experience with multiple products in this niche. Come up with something that none of those apps are doing or… bring together all the good aspects of the products you know and eliminate the downsides.


---

# 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://outdraw-academy.gitbook.io/become-a-ux-designer/roadmap/month-4-design-products.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.