Problem
Research
To improve the handoff process, I surveyed both developers and designers. This helped identify what was working well, what needed improvement, and what was missing.
The key challenge was finding the right balance between the time designers spent preparing files and the time developers needed to analyze them before implementation.
Solution
The most effective and low-effort solution was introducing a cross-review process, where another designer checked the file against predefined criteria before it was handed off. This peer-review approach is widely used in development and has already proven its efficiency.
1. Defining the cross-review process
I mapped out the entire review flow, detailing each step to make the process clear and structured.
Cross-review flow diagram
2. Setting review criteria
Based on feedback from both designers and developers, I created a list of key review points. These fell into three main categories:
File structure & organization
Content of the file
Design decisions (optional)
Each criterion was documented with descriptions and examples.
Example of criterion description
3. Cross-review report
To track feedback, I created a table where reviewers assigned one of the following statuses to each criterion:
🥒 All good – Everything meets the requirements
🌝 Needs clarification – Unclear if something is an issue or not
🦀 Requires revision – Needs some adjustments
🗿 Not checked – Skipped if not relevant to the file
Reviewers also left comments directly in Figma to help designers make necessary fixes.
Cross-review report