10.3 Submission and Review Process
Key Concepts
1. Submission Guidelines
Submission guidelines outline the specific requirements and formats for submitting your design work. These guidelines ensure that all submissions are consistent and meet the necessary standards.
Example: If you are submitting a website design, the guidelines might specify that the file should be in Figma format, include all necessary components, and be named according to a specific convention (e.g., "ProjectName_VersionNumber").
2. Review Criteria
Review criteria define the standards and expectations against which your design will be evaluated. These criteria help in assessing the quality, functionality, and alignment with project goals.
Example: For a mobile app design, the review criteria might include usability, visual appeal, consistency with brand guidelines, and responsiveness across different devices.
3. Peer Review
Peer review involves having colleagues or team members evaluate your design work. This process provides diverse perspectives and constructive feedback, helping to identify blind spots and areas for improvement.
Example: After completing a wireframe for a new feature, you might share it with a colleague who can provide feedback on the layout, user flow, and potential usability issues.
4. Stakeholder Review
Stakeholder review involves presenting your design to key stakeholders, such as clients, project managers, or business owners. This review ensures that the design aligns with business objectives and meets stakeholder expectations.
Example: Before finalizing a website design, you might present it to the client for approval. The client can provide feedback on the overall look and feel, content placement, and alignment with their brand identity.
5. Iterative Feedback
Iterative feedback involves making multiple rounds of improvements based on the feedback received during reviews. This process ensures that the design evolves and meets user needs and expectations through continuous refinement.
Example: After receiving feedback from a stakeholder review, you might make iterative changes to the design, such as adjusting the layout, improving the navigation, or enhancing the visual elements. Each iteration brings the design closer to perfection.
6. Documentation of Feedback
Documentation of feedback involves keeping a record of all feedback received during the review process. This documentation helps in tracking changes, understanding the rationale behind decisions, and ensuring transparency.
Example: Create a document that summarizes the feedback received from each review round. Include screenshots, annotations, and reflections on what worked well and what could be improved. This documentation serves as a reference for future projects.
7. Final Submission
Final submission involves delivering the polished and complete version of the design work. This includes all necessary files, documentation, and any additional assets required for implementation.
Example: For a website project, the final submission might include the Figma file, a style guide, a prototype, and any additional assets such as images and icons. Ensure that all files are organized and clearly labeled for easy access.
8. Post-Submission Review
Post-submission review involves evaluating the final design after it has been submitted. This review ensures that all requirements were met, the design is complete, and any last-minute issues are addressed.
Example: After submitting the final design, you might conduct a final review to ensure that all components are included, the design is responsive, and the documentation is comprehensive. This review helps in identifying any remaining issues before the project moves to the next phase.
9. Handoff to Development
Handoff to development involves preparing the final design assets and documentation for the development team. This includes exporting design files, providing style guides, and ensuring clear communication of design intent.
Example: For a mobile app, the design team might export high-resolution images, icons, and other assets. They would also provide a detailed style guide that includes color codes, typography specifications, and component guidelines to ensure consistency in the final product.
10. Continuous Improvement
Continuous improvement involves monitoring the design's performance and gathering user feedback after it has been implemented. This step helps in identifying any remaining issues and planning for future updates and improvements.
Example: After the website is launched, the team might monitor user reviews, analytics, and feedback forms to identify any bugs, usability issues, or feature requests. This information can guide future updates to enhance the design's functionality and user satisfaction.