GatorRyde
A simple way for students to connect and plan long-distance trips together
ESTIMATED READING TIME
8 mins
ROLE
UX Researcher
UX Designer
SKILLS
Design Systems
Developer Handoff
TIMELINE
10 Weeks
Project Overview
The Summer I Became a Design Detective
During my internship at JPMorgan Chase, I realized my job wasn’t just about designing screens, it was about uncovering clues to why handoffs between designers and developers kept breaking down. Specs went missing, documentation lived in too many places, and developers were left guessing about design intent.
Like a detective, I dug into the evidence: interviews, workflows, and countless Figma files. What I uncovered was clear, the process itself needed to be redesigned.
The Challenge
Cracking the Case of Messy Handoffs
Inconsistent Handoffs
Even after designs were completed, the handoff process created more challenges than solutions:
Designers organized files differently, which confused engineers
Specs inside files were inconsistent
Developers frequently needed additional clarifications
Inefficient Workflows
The existing workflow was inefficient:
Teams worked in silos
Checkpoints were limited, and handoff happened too early
Feedback arrived too late to be effective
The Result
Releases slowed down, frustration grew, and testing uncovered errors and usability discrepancies that could have been prevented.
Inconsistent Handoffs
Even after designs were completed, the handoff process created more challenges than solutions:
Designers organized files differently, which confused engineers
Specs inside files were inconsistent
Developers frequently needed additional clarifications
Inefficient Workflows
The existing workflow was inefficient:
Teams worked in silos
Checkpoints were limited, and handoff happened too early
Feedback arrived too late to be effective
The Result
Releases slowed down, frustration grew, and testing uncovered errors and usability discrepancies that could have been prevented.
Inconsistent Handoffs
Even after designs were completed, the handoff process created more challenges than solutions:
Designers organized files differently, which confused engineers
Specs inside files were inconsistent
Developers frequently needed additional clarifications
Inefficient Workflows
The existing workflow was inefficient:
Teams worked in silos
Checkpoints were limited, and handoff happened too early
Feedback arrived too late to be effective
The Result
Releases slowed down, frustration grew, and testing uncovered errors and usability discrepancies that could have been prevented.
Inconsistent Handoffs
Even after designs were completed, the handoff process created more challenges than solutions:
Designers organized files differently, which confused engineers
Specs inside files were inconsistent
Developers frequently needed additional clarifications
Inefficient Workflows
The existing workflow was inefficient:
Teams worked in silos
Checkpoints were limited, and handoff happened too early
Feedback arrived too late to be effective
The Result
Releases slowed down, frustration grew, and testing uncovered errors and usability discrepancies that could have been prevented.
USER RESEARCH
I Cracked the Case…
Or So I Thought
At first, I considered a simple shortcut:
One universal design file template with a rigid structure that every team could use.
USER RESEARCH
User Insights
To investigate these challenges, I did interviews with both designers and engineers.
Interviews: 30 participants (conducted over Zoom and in-person)
17 designers
13 engineers
From this research, two clear personas emerged:
The Designer: Wants to share work but struggles with inconsistent file organization, repetitive annotations, and no clear rules for version control.
The Developer: Needs clarity and consistency but wastes time digging through messy files and chasing missing specs
Nina Miles
Age: 27
Occupation: Junior UX Designer
MAIN TASK:
Ensure design files are organized and annotated for smooth developer handoff while balancing multiple projects and deadlines.WANTS/NEEDS:
Needs a clear system to structure design files for easier navigation by developers.
Wants assurance that design intentions are consistently communicated to reduce back-and-forth.
FINDINGS:
Organized and detail-oriented, but experiences frustration when developers misinterpret design choices.
Values clarity and standardization in file handoff but recognizes adoption is sometimes inconsistent.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
Jamie Douglas
Age: 36
Occupation: Senior Developer
MAIN TASK:
Accurately implement design intentions into code while minimizing delays from unclear or incomplete design files.WANTS/NEEDS:
Wants access to consistent design files with proper naming conventions and annotations.
Needs reliable version control for components across platforms (e.g., Figma, Storybook).
Seeks reassurance that collaboration with designers will reduce rework and discrepancies.
FINDINGS:
Frequently encounters missing details and inconsistent documentation in design handoffs.
Hesitant to adopt new workflows unless benefits to speed and accuracy are clear.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
Nina Miles
Age: 27
Occupation: Junior UX Designer
MAIN TASK:
Ensure design files are organized and annotated for smooth developer handoff while balancing multiple projects and deadlines.WANTS/NEEDS:
Needs a clear system to structure design files for easier navigation by developers.
Wants assurance that design intentions are consistently communicated to reduce back-and-forth.
FINDINGS:
Organized and detail-oriented, but experiences frustration when developers misinterpret design choices.
Values clarity and standardization in file handoff but recognizes adoption is sometimes inconsistent.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
Jamie Douglas
Age: 36
Occupation: Senior Developer
MAIN TASK:
Accurately implement design intentions into code while minimizing delays from unclear or incomplete design files.WANTS/NEEDS:
Wants access to consistent design files with proper naming conventions and annotations.
Needs reliable version control for components across platforms (e.g., Figma, Storybook).
Seeks reassurance that collaboration with designers will reduce rework and discrepancies.
FINDINGS:
Frequently encounters missing details and inconsistent documentation in design handoffs.
Hesitant to adopt new workflows unless benefits to speed and accuracy are clear.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
Nina Miles
Age: 27
Occupation: Junior UX Designer
MAIN TASK:
Ensure design files are organized and annotated for smooth developer handoff while balancing multiple projects and deadlines.WANTS/NEEDS:
Needs a clear system to structure design files for easier navigation by developers.
Wants assurance that design intentions are consistently communicated to reduce back-and-forth.
FINDINGS:
Organized and detail-oriented, but experiences frustration when developers misinterpret design choices.
Values clarity and standardization in file handoff but recognizes adoption is sometimes inconsistent.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
Jamie Douglas
Age: 36
Occupation: Senior Developer
MAIN TASK:
Accurately implement design intentions into code while minimizing delays from unclear or incomplete design files.WANTS/NEEDS:
Wants access to consistent design files with proper naming conventions and annotations.
Needs reliable version control for components across platforms (e.g., Figma, Storybook).
Seeks reassurance that collaboration with designers will reduce rework and discrepancies.
FINDINGS:
Frequently encounters missing details and inconsistent documentation in design handoffs.
Hesitant to adopt new workflows unless benefits to speed and accuracy are clear.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
Nina Miles
Age: 27
Occupation: Junior UX Designer
MAIN TASK:
Ensure design files are organized and annotated for smooth developer handoff while balancing multiple projects and deadlines.WANTS/NEEDS:
Needs a clear system to structure design files for easier navigation by developers.
Wants assurance that design intentions are consistently communicated to reduce back-and-forth.
FINDINGS:
Organized and detail-oriented, but experiences frustration when developers misinterpret design choices.
Values clarity and standardization in file handoff but recognizes adoption is sometimes inconsistent.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
Jamie Douglas
Age: 36
Occupation: Senior Developer
MAIN TASK:
Accurately implement design intentions into code while minimizing delays from unclear or incomplete design files.WANTS/NEEDS:
Wants access to consistent design files with proper naming conventions and annotations.
Needs reliable version control for components across platforms (e.g., Figma, Storybook).
Seeks reassurance that collaboration with designers will reduce rework and discrepancies.
FINDINGS:
Frequently encounters missing details and inconsistent documentation in design handoffs.
Hesitant to adopt new workflows unless benefits to speed and accuracy are clear.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
Main Issues
Key Takeaways
Conversations with designers and developers revealed why this “one-size-fits-all” approach would backfire:
Different teams, different needs: Not every product required the same level of annotation.
Flexibility matters: Overly rigid templates slow designers down instead of helping them.
Context counts: A small internal tool doesn’t need the same depth as a customer-facing app.
Problem Statement
How can we improve communication and guidelines to make the design handoff process smoother and more efficient?
Solution
Solutions
After delving into the research, I decided on two key deliverables:
Design Workflow Guide (Confluence)
A documented guide outlining the recommended steps and best practices for the entire design process.
Includes collaboration tips for smoother communication with developers and stakeholders.
Scalable Design Template (Figma)
A flexible, scalable Figma template designed to guide both new and senior designers in structuring their files and applying annotations.
Guides designers on organizing layers, components, and annotations to fit their project.
Design Workflow Guide (Confluence)
A documented guide outlining the recommended steps and best practices for the entire design process.
Includes collaboration tips for smoother communication with developers and stakeholders.
Scalable Design Template (Figma)
A flexible, scalable Figma template designed to guide both new and senior designers in structuring their files and applying annotations.
Guides designers on organizing layers, components, and annotations to fit their project.
Design Workflow Guide (Confluence)
A documented guide outlining the recommended steps and best practices for the entire design process.
Includes collaboration tips for smoother communication with developers and stakeholders.
Scalable Design Template (Figma)
A flexible, scalable Figma template designed to guide both new and senior designers in structuring their files and applying annotations.
Guides designers on organizing layers, components, and annotations to fit their project.
Design Workflow Guide (Confluence)
A documented guide outlining the recommended steps and best practices for the entire design process.
Includes collaboration tips for smoother communication with developers and stakeholders.
Scalable Design Template (Figma)
A flexible, scalable Figma template designed to guide both new and senior designers in structuring their files and applying annotations.
Guides designers on organizing layers, components, and annotations to fit their project.
🔒 Final deliverables contain internal information, so I can’t share links publicly.
Please connect with me for details and check out my final presentation!
REFLECTIONS
Metrics of Success
Adoption Rate
Measure the percentage of designers who are actively using the design handoff template for organizing their Figma files.
Feedback & Satisfaction
Collect qualitative and quantitative feedback from designers and developers regarding the ease of use and effectiveness of the template.
Reduction in Discrepancies
Track the number of discrepancies found during audits before and after implementing the design handoff template.
Improved Communication
Evaluate the quality of communication between designers and engineers through surveys or feedback sessions.
Adoption Rate
Measure the percentage of designers who are actively using the design handoff template for organizing their Figma files.
Feedback & Satisfaction
Collect qualitative and quantitative feedback from designers and developers regarding the ease of use and effectiveness of the template.
Reduction in Discrepancies
Track the number of discrepancies found during audits before and after implementing the design handoff template.
Improved Communication
Evaluate the quality of communication between designers and engineers through surveys or feedback sessions.
Adoption Rate
Measure the percentage of designers who are actively using the design handoff template for organizing their Figma files.
Feedback & Satisfaction
Collect qualitative and quantitative feedback from designers and developers regarding the ease of use and effectiveness of the template.
Reduction in Discrepancies
Track the number of discrepancies found during audits before and after implementing the design handoff template.
Improved Communication
Evaluate the quality of communication between designers and engineers through surveys or feedback sessions.
Adoption Rate
Measure the percentage of designers who are actively using the design handoff template for organizing their Figma files.
Feedback & Satisfaction
Collect qualitative and quantitative feedback from designers and developers regarding the ease of use and effectiveness of the template.
Reduction in Discrepancies
Track the number of discrepancies found during audits before and after implementing the design handoff template.
Improved Communication
Evaluate the quality of communication between designers and engineers through surveys or feedback sessions.
With more time...
Implementation and Training:
Roll out the template to all design teams.
Conduct training sessions to ensure designers understand how to use the template effectively.
Continuous Improvement:
Analyze feedback to identify areas for improvement.
Update the template based on feedback to enhance its usability and effectiveness.
What I Learned
This summer, I learned that sometimes the real design problem isn’t the screen, it’s the system. By becoming a design detective, I uncovered the hidden inefficiencies in handoff and transformed them into a scalable solution.
Good design isn’t just about pixels; it’s about how smoothly those pixels make it into production.
Thank you!
I’m so grateful to my amazing team: Adam, Danny, Daniela, Ginger, and Ylan, for making this project possible. Special thanks to my mentors, Max McVeigh and Chetan Dusane, for their constant guidance and belief in me. A final thank you to my intern cohort for our lunchtime chats on the patio with our free side salads :)
Design to Development Handoff Guide
ESTIMATED READING TIME
8 mins
ROLE
UX Researcher
UX Designer
SKILLS
Design Systems
Developer Handoff
TIMELINE
10 Weeks
Project Overview
The Summer I Became a Design Detective
During my internship at JPMorgan Chase, I realized my job wasn’t just about designing screens, it was about uncovering clues to why handoffs between designers and developers kept breaking down. Specs went missing, documentation lived in too many places, and developers were left guessing about design intent.
Like a detective, I dug into the evidence: interviews, workflows, and countless Figma files. What I uncovered was clear, the process itself needed to be redesigned.
The Challenge
Cracking the Case of Messy Handoffs
Inconsistent Handoffs
Even after designs were completed, the handoff process created more challenges than solutions:
Designers organized files differently, which confused engineers
Specs inside files were inconsistent
Developers frequently needed additional clarifications
Inefficient Workflows
The existing workflow was inefficient:
Teams worked in silos
Checkpoints were limited, and handoff happened too early
Feedback arrived too late to be effective
The Result
Releases slowed down, frustration grew, and testing uncovered errors and usability discrepancies that could have been prevented.
I Cracked the Case… Or So I Thought
At first, I considered a simple shortcut:
One universal design file template with a rigid structure that every team could use.
USER RESEARCH
User Insights
To investigate these challenges, I did interviews with both designers and engineers.
Interviews: 30 participants (conducted over Zoom and in-person)
17 designers
13 engineers
From this research, two clear personas emerged:
The Designer: Wants to share work but struggles with inconsistent file organization, repetitive annotations, and no clear rules for version control.
The Developer: Needs clarity and consistency but wastes time digging through messy files and chasing missing specs
Nina Miles
Age: 27
Occupation:
Junior UX Designer
MAIN TASK:
Ensure design files are organized and annotated for smooth developer handoff while balancing multiple projects and deadlines.
WANTS/NEEDS:
Needs a clear system to structure design files for easier navigation by developers.
Wants assurance that design intentions are consistently communicated to reduce back-and-forth.
FINDINGS:
Organized and detail-oriented, but experiences frustration when developers misinterpret design choices.
Values clarity and standardization in file handoff but recognizes adoption is sometimes inconsistent.
Jamie Douglas
Age: 36
Occupation:
Senior Developer
MAIN TASK:
Accurately implement design intentions into code while minimizing delays from unclear or incomplete design files.
WANTS/NEEDS:
Wants access to consistent design files with proper naming conventions and annotations.
Needs reliable version control for components across platforms (e.g., Figma, Storybook).
Seeks reassurance that collaboration with designers will reduce rework and discrepancies.
FINDINGS:
Frequently encounters missing details and inconsistent documentation in design handoffs.
Hesitant to adopt new workflows unless benefits to speed and accuracy are clear.
Main Issues
Key Takeaways
Conversations with designers and developers revealed why this “one-size-fits-all” approach would backfire:
Different teams, different needs: Not every product required the same level of annotation.
Flexibility matters: Overly rigid templates slow designers down instead of helping them.
Context counts: A small internal tool doesn’t need the same depth as a customer-facing app.
Problem Statement
How can we improve communication and guidelines to make the design handoff process smoother and more efficient?
Solution
Solutions
After delving into the research, I decided on these 2 key deliverables:
Scalable Design Template (Figma)
A flexible, scalable Figma template designed to guide both new and senior designers in structuring their files and applying annotations.
Guides designers on organizing layers, components, and annotations to fit their project.
Design Workflow Guide (Confluence)
A documented guide outlining the recommended steps and best practices for the entire design process.
Includes collaboration tips for smoother communication with developers and stakeholders.
🔒 Final deliverables contain internal information, so I can’t share links publicly.
Please connect with me for details and check out my final presentation!
Reflections
Metrics of Success
Adoption Rate
Measure the percentage of designers who are actively using the design handoff template for organizing their Figma files.
Feedback & Satisfaction
Collect qualitative and quantitative feedback from designers and developers regarding the ease of use and effectiveness of the template.
Reduction in Discrepancies
Track the number of discrepancies found during audits before and after implementing the design handoff template.
Improved Communication
Evaluate the quality of communication between designers and engineers through surveys or feedback sessions.
With more time...
Implementation and Training:
Roll out the template to all design teams.
Conduct training sessions to ensure designers understand how to use the template effectively.
Continuous Improvement:
Analyze feedback to identify areas for improvement.
Update the template based on feedback to enhance its usability and effectiveness.
What I Learned
This summer, I learned that sometimes the real design problem isn’t the screen, it’s the system. By becoming a design detective, I uncovered the hidden inefficiencies in handoff and transformed them into a scalable solution.
Good design isn’t just about pixels; it’s about how smoothly those pixels make it into production.
Thank you!
I’m so grateful to my amazing team: Adam, Danny, Daniela, Ginger, and Ylan, for making this project possible. Special thanks to my mentors, Max McVeigh and Chetan Dusane, for their constant guidance and belief in me. A final thank you to my intern cohort for our lunchtime chats on the patio with our free side salads :)