---
description: General knowledge intended to understand the workflow of OpenCollective Design
---

# Design Workflow

## Mapping our process

The process to open-up the design collective is based on a specific concep&#x74;**:**

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

![](https://2682340432-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LnScH_KG1YJixOv0LJB%2F-Ls-AJlbuiL8iVARH02B%2F-Ls-APtlFKPUtBEJiY-9%2F2%20\(3\).png?generation=1571961029785613\&alt=media)

### Sprint workflow and key players

![](https://2682340432-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LnScH_KG1YJixOv0LJB%2F-Ls-AJlbuiL8iVARH02B%2F-Ls-APtn4Si3jr1PK65F%2F5%20\(1\).png?generation=1571961029819600\&alt=media)
