All issues regarding any design work should be included in this project board.
When adding an issue to this board, please associate the corresponding labels (listed below). Any Issue can have multiple labels
Design › Brand/Communication: For tasks regarding things like logotypes/symbols, stationery (letterheads, business cards, etc), social networks' covers and avatars, presentations (keynote/pdf/etc). An example could be: Create the logo variations for geographical regions and verticals (i.e. Open Collective UK, Open Collective LGBT).
Design › Copy-write/Messaging: For tasks regarding written content that aim to increase brand awareness and ultimately persuade a person or group to take a particular action. An example could be: Re-write the Homepage content to increase user conversion to create a new collective.
Design › Illustration/Imagery: For tasks regarding the production of iconography, glyphs, vector graphics/art, photo production/manipulation, etc. An example could be: Create illustrations to explain the flow of applying for a host during the on-boarding experience.
Design › System: For tasks regarding the setup and update of the system created to execute and maintain the design deliverables. This includes things like version control for source files (currently Sketch files), library creation and management (typography, colors, components, buttons, etc.), and assets management (svgs, typefaces, optimized imagery, etc). An example could be: Migrate Open Collective's version control workflow from Abstract to InVision DSM.
Design › UI/IA: For tasks regarding additions and updates to the user interfaces (this includes Information Architecture when applicable) of Open Collective. Any digital space where interactions between users and Open Collective occur: Web platform, email templates, back-office (when it exists if it'll exist), mobile apps (when they exist if they'll exist). An example could be: Update the expenses page with data visualization (line/bar graphs) components to show a monthly summary of inflow and expenses.
Design › UX: For tasks regarding the processes of enhancing user satisfaction with Open Collective by improving the usability, accessibility, and pleasure provided in the interaction with the product. An example could be: Create an on-boarding experience for new hosts to increase the number of possible hosts to which collectives that are ready to receive financial contributions can apply to.
In Queue: For tasks that aren't a priority to execute or there isn't enough visibility to fully solve, but, the need to solve is already identified.*
Design tasks need to clearly describe intended goals, context, and CONSTRAINTS (logistical, technical, time-based) to increase the probability of valuable solutions.
New: This is where all new tasks (requests or self imposed) are going to be listed. When an issue is added here, it will be reviewed by the core team. If accepted, it'll be moved to the next column. If it is accepted but for some reason it can't be scheduled, then we'll leave it in this column and add the ⏳ In Queue label to it and schedule it when possible.
Accepted & Scheduled: Once an Issue is accepted it gets moved to this column to be prioritized and scheduled within the planned milestones. This is the column that gives visibility of the planned workload and can help everyone make better decisions on what and how to organize new work.
In Progress: When the time comes to work on solving an Issue, it gets moved to this column. This shows the current workload in a given milestone.
In Review: When a solution to an Issue has been reached, it gets moved to this column for the stakeholders to review. If the solution needs more work/iterations, then it will be moved back to the previous column.
Completed: If the Issue in review is accepted as solved by stakeholders, then it will get moved to this column. At this point, the issue can be moved to a development board or milestone. If it doesn't need to be further worked on, then the Issue will be closed.