The high quality of our platforms is a task that every team member is responsible of. Use this guide to learn how the Design team promotes quality assurance practices during the whole life of a project.

After a Design Sprint (and before development)

The Sprint designer must make sure that:

• Run a Design Review with another designer from the team
• Keep track of received feedback, as well as other concepts suggested in the Post-Sprint Design Backlog document
• Malke sure to properly clean and organize her final files (so any other designer can continue the work later)

During development (MVP)

A designer from the team must 'adopt' the project, as an official supervisor. Each designer should then be able to engage in an average of 2 projects at a time; and that involvement implies she makes sure of:

Right at the beginning of the development

Take one or two weeks (at least) to work exclusively on the project's interface. This work implies:

• Clarify, improve or correct existing screens (based on client's input, or changes to features during scope negotiation)
• Design missing screens (including responsive states, when applyable)
• Organiza and cleas as much as possible the design system (UI elements), making sure that each element is used in a clean way, without innecesary variations of key elements

Afterwards, take one or two weeks (at least) to generate front end code base. The main focus should be:

• Font styles
• UI sizing and styling (buttons, cards, titles, lists, forms, and other common elements)
• Complex layouts
• Responsive bases (when relevant)

During the whole development

Considering that the designer will not be able to assist during the full development process, after her initial involvement she will seek to run at least 3 Design Reviews with the developers.

In each one of these reviews (spread equally over the time left before deployment) the designer will evaluate:

• Layouts
• Responsiveness
• Elements size and style
• Proper alignment
• Fidelity to original design

Bugs and possible enhancements will be documented and prioritized, so that the developers fix every suggestion (with or without the help of the designer).

Previous to final delivery

During the last week of the project (before final presentation with the client), the designer will engage closely with the development team to make sure that no one is missing any critical detail that hurts the quality of our delivery.

This engagement implies:

• Review any existing backlog (of bugs and fixes), as well as any possible new error
• Promote the timely correction of these bugs, letting developers take care of backend issues more freely
• Provide support to the Engagement Manager (or any other relevant project leader) to keep visibility of all issues detected, and solutions delivered

Final notes

Specific formats and practices described in this guide are in constant evoution. Make sure to check in with the current Lead Designer to obtain better details and references.