Glow Financing Integration

Role: Senior Product Designer

Completed: December 2025

Users: 80,000

Team: 1 Lead Product Designer, 1 Senior Product Designer

Project summary

Problem

Lead designers are unable to keep up with the pace of changes going on in individual projects, leading to inconsistencies, delays and missed changes.

Solution

Create a Figma file that makes it possible to see changes across projects in real-time, ensuring consistency and reducing mistakes.

Tracfone FWA Hero
Process Image
Next Project: Credit Report Service

Approach

Lead designers oversaw 2-3 Senior Designers who are working heads down with product team, the Figma files were constantly changing. Comments were initially used to track changes and provide feedback, but as comments reached 2000, it became difficult to manage and prioritize them effectively.

  • Hard to track changes
  • Hard to link work to Jira stories
  • Difficult to prioritize feedback
Mobile UI

Product XM Trust

In the reality of multiple designers working and deliver multiple projects in the same file, the working Figma was impossible to read. There was no way to see what the most recent work was, who did it and why. Leading the Product team not to trust the Figma or the designers, often missing or losing content that had previously been updated.

  • XM's would avoid involving design because the work would get lost inside huge Figma files
  • Lead Designers and Senior Designers needed to work hard to align to be a unified voice.
  • The relationship between design and product teams was strained due to lack of visibility and trust.
Prototype Flow

Structure

Files needed to be consistently structured so that Lead Designers and Product Owners could easily find the most recent work, understand the context and link it to Jira stories. This structure needed to be maintained across multiple projects and teams to ensure consistency and ease of use.

  • Added a Feedback Log and Update Log so that changes and feedback could be tracked effectively per each section of work
  • Created a consistent file structure across projects to improve visibility and trust.
  • Add statuses to the Page.
  • created simple page structure so that Lead UX design and Product owner can see exactly what they are loooking at, they don't need to be a 'Figma expert' to understand the context.
Results Achieved

Conclusion

Poorly maintained and unstructured files led to a lack of trust and visibility between design and product teams. By implementing a consistent file structure, feedback logs, and clear page statuses, we were able to improve collaboration, streamline workflows, and ensure that the most recent work was easily accessible and understandable. Making the Figma the go to single source of truth again.

  • Requires dedicated effort from designers to maintain the structure and logs
  • Streamlined workflows and reduced confusion
  • Increased trust in the Figma files as a single source of truth