> For the complete documentation index, see [llms.txt](https://documentarians.gitbook.io/metadocumentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentarians.gitbook.io/metadocumentation/master/contributing/design/understanding-the-design-workflow.md).

# Design Workflow

## Mapping our process

The process to open-up the design collective is based on a specific concept**:**

**Clarity and transparency in the design process.**

In order to achieve this common ground, the design collective has created a **consensual** **map of an ideal design process.** One that could adapt to different project sizes and complexities, well understood by designers and non-designers alike.

### What does it serve a process map for?

* Open-up the design production process
* Produce efficiently
* Maintain brand cohesion
* Make sure each individual is working on projects that come to fruition
* Help adjacent collectives or teams like product management, marketing and engineering know exactly how to work with design

### Ideal sprint cycle

The following diagram describes the ideal workflow of a sprint of 10 working days, all the way from planning the sprint to the demo day where the series of design solutions are presented with a public release.

![](/files/-Ls-APtlFKPUtBEJiY-9)

### Sprint workflow and key players

![](/files/-Ls-APtn4Si3jr1PK65F)


---

# 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://documentarians.gitbook.io/metadocumentation/master/contributing/design/understanding-the-design-workflow.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.