# Workflow

## Write a user journey

The product designer should create a user journey that is in alignment with the team that understands the user's requirements. This user journey should be documented and clearly made visible [on this Miro board](https://miro.com/app/board/uXjVOFVyrKM=/).

{% hint style="info" %}
Make sure that your update is visually distinguishable from what is currently implemented.
{% endhint %}

## Sketch the screens on paper

It may be useful to sketch the screens on paper first to validate the idea with the user researcher or the person who understands the stakeholder requirements.

## Create screens in Figma

The product designer should then go into Figma and create screens for each step of the user journey, keeping all new elements and information contextually in the appropriate components.

## Reuse existing components

It is important to not invent anything that is completely new, but instead to inform the design from the existing visual style and components. It is also important to avoid redundant elements.

## Check-in with the user researcher or team lead

After the design is done, it is important to check in with the relevant party to make sure that everything is in alignment with the user's needs.

{% hint style="info" %}
You can now visually merge your [user journey update](https://miro.com/app/board/uXjVOFVyrKM=/) with the existing one.
{% endhint %}

## Record summary for the engineering team

The last step is to record a video summary of how everything works for the engineering team, outlining every single change and how everything is supposed to function.


---

# 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://docs.deepwork.studio/teams-departments/software/roles/software-product-design/workflow.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.