Keying 可滢 Guo

---
Keying (Chloe) Guois an aspiring UX designer and NYU student studying Interactive Media Arts. She’s passionate about crafting intuitive and visually compelling user experiences, seamlessly blending art and technology to enhance usability and engagement.

A lover of all things UX/UI design, gamification, creative coding, and iced matcha lattes, Chloe also has a soft spot for Studio Ghibli films, electric guitars, and finding beauty in everyday patterns.

---
  1. Font Police
  2. Rideo
  3. Stone Dry
  4. FlowMingle
  5. Sizzling House


About’
Playground’
Email’
CV’



©2025 Keying Guo

Font Police
// AUG 2025




Font Police is an internal compliance tool that helps Fiserv product owners scan URLs for unauthorized fonts and ensure compliance with brand and licensing standards. We built the product from the ground up by speaking directly with users, uncovering their workflow challenges, and shaping a complete experience that moved naturally from early concept exploration to a fully realized prototype.

consumer product visual design web design

Team Role

ToolsUX Designer

Figma

01Problem Statement
Product owners at Fiserv had no efficient way to detect unauthorized or blacklisted fonts across their digital products. This led to brand inconsistency and posed potential legal risks due to font licensing violations.



02Competitive Analysis
Our team conducted a competitive analysis of existing tools, including Turnitin Reports and the WAVE Plugin, both of which are known for delivering effective, visually clear feedback mechanisms.


           
Key features that stand out from competitors: Generates reports that highlight potential plagiarism and provides a clear numerical report for users.
       
Key features that stand out from competitors: Provides visual feedback on web page accessibility by highlighting issues, such as missing alt text, contrast problems, and structural errors


　　　　　　　　               　　


03Interview Insights

To gain a deeper understanding of the internal review process at Fiserv, the team conducted interviews with one representative from the Quality Assurance team and one from the Cyber Review team.

Link to Interview Script




         
Pain Points


04Archetypes
After gathering interview insights, we put together a user journey map to analyze the user experience pathway for the process of going through the Font Police product. 


05Define & Ideate
We broke down the complex tasks of creating a new scan into simpler steps and used those to make a user flow that shows the happy path taken by the product owner. The Admin can manage the master font list and view scan statistics created by product owners. 

Task Analysis




User Flow




Low Fidelity Wireframes



High Fidelity Wireframes



06Prototype 




07Usability Testing
The team conducted interviews where potential users were asked to complete various tasks to test the accessibility and functionality of Font Police.  

   Success:

  • The platform fitted the mental model that users had
  • Users explained every step clearly as they were going through the platform
   Improvements:

  • Users suggested adding tooltips to make some parts clearer
  • There were suggestions to fix the wording to make it clearer and direct


08Challenges
We faced technical limits since pages behind security walls couldn’t be scanned. To address this, the MVP only supports public URLs. Collaborating with the developer team clarified what was feasible under these restrictions.

Another early challenge was identifying the right stakeholders and where font scanning fit into the system development life cycle. After interviewing potential users, we determined that product owners and engineers should be directly responsible for scanning their products.

09Learning Outcomes