menu_open
Open Menu
Component Design: Preventing Errors and Building Trust With Dialogs
Project Summary and Role

During my Academic Year Internship at SportsEngine, I designed a new set of dialog components to prevent irreversible user errors and unify inconsistent patterns across the platform. The project focused on building flexible, reusable components that clearly communicate different levels of risk, helping users feel confident when taking potentially destructive actions.

SKILLS
UX Research
UX Writing
Design System
TOOLS
Figma
Qualtrics
DURATION
6 weeks
TEAM
Me

My Role

As an intern, I conducted research and reviewed guidelines, created wireframes and implemented feedback, designed components from scratch, and contributed to SportEngine's design system.

Problem

SportsEngine had only one dialog pattern in its design system. It wasn’t flexible enough to accommodate varying use cases, which led designers to create one-off solutions. This inconsistency introduced usability risks, especially for destructive actions like deleting critical user data.

Objective

Design a reusable, accessible dialog system that:

  • Follows design system standards.

  • Handles a range of destructive and non-destructive use cases.

  • Guides users clearly and efficiently through confirmation workflows .

User Experience Impact

  • Clearer language and visual hierarchy helped users better understand the consequences of their actions.

  • Tailored dialog types reduced the chance of accidental data loss.

  • Guides users clearly and efficiently through confirmation workflows.

Business Impact

  • Reduced need for custom dialogs saved designers and developers time.

  • Decreased potential for support tickets due to misclicks or errors.

  • Strengthened trust and satisfaction through a smoother, safer user experience.

Research & Audit

What are Dialogs?

A big stop sign that interrupts a destructive or permanent action that the user has taken. Allows for a second chance to consider before proceeding.

I Audited Existing SportsEngie Dialogs

I audited dialogs across SportsEngine and found major inconsistencies:

  • Some had headers, others didn’t.

  • UX copy varied widely in tone and formatting (especially bolding).

  • Designers were improvising, leading to visual and functional confusion.

Examples of Varied Needs
Gaurdianships
Deleting an account meant losing high-value user data.
Season Management
User can delete items that will remove data, but not necessarily delete it. There are varied levels of risks, requiring a more nuanced warning

Industry Research and Best Practices

I explored best practices from trusted sources like Windows' Guidelines, Nielson Norman Group, and Material Design on dialog use cases. A key insight: dialogs should match the severity of the action. The more permanent the consequence, the more caution the interface should prompt.

Created Guidelines For Different Dialog Use Cases

I identified three main types of dialogs to address different levels of destructive actions. During the brainstorming process, I considered the diverse needs within SportsEngine. For example, in Guardianships, deleting account profiles results in the loss of valuable data. In Season Management, deleting items removes data but does not necessarily destroy it. These dialogs account for varying levels of risk.

I presented these guidelines to the team, and they were approved.
Wireframing and Feedback

UX Writing

The Issue

Different guidelines recommended different things. Some stated that using phrases like "Are you sure?" and "Do you want to?" are unnecessary and undermine the user's confidence. Others stated that these questions encourage caution. I had to decide whether the header should be succinct or focus on slowing the user down and making them consider their actions.

Writing Feedback

I consulted the UX team to gauge if anyone had strong opinions, and then based my decision on what everyone preferred, which was my other idea of using a more direct “Delete [item]”.

Users should understand the dialog and their choices based on the title and button text alone. The copy must be succinct and efficient.

Iterations and More Feedback

Feedback for the Double Confirmation Dialogs

Using a checkbox reminded us of terms and conditions agreements, which users often click without second thought. Therefore, we all decided to use typing ‘delete’ as a double confirmation would be more effective at stopping the user. The caution icon denotes extra danger and is better practice than using "Warning!" for accessibility.

Component Design

I outlined the dialog type variants, booleans, and size variants for implementation into my new dialogs. Then I designed the dialogs from scratch.

Final Dialogs
Double Confirmation Dialog
Destructive Dialog
Non-Desctructive Dialog
Sign Post
Reflection

What I learned

I was assigned this mini Dialog Project in addition to my Global Settings Project. Even seemingly small projects require thorough research and intentional design. I had to consider UX copy, hierarchy, and component design to effectively convey warnings to users. This project highlighted the importance and impact of dialogs in preventing errors, reassuring users, and fostering trust. I also learned how to manage multiple projects simultaneously and work under tighter deadlines.

What I'd Improve

Use of Visuals in Dialogs
A SportsEngine designer Catalina shared that she uses icons, avatars or visuals in dialogs related to profiles so I did some research and created rough guidelines for their use:
  • When the action has an emotional impact, like removing a team member or guardian, to help identify who will be impacted.
  • When the object being deleted is personalized.
  • Avoid using visuals for teams/seasons; use them for objects already reliant on images.  Ensure visuals add value to the user experience rather than detract from it by cluttering the interface.
If I had more time, I would've designed this type of variant to the dialog components I created and explore other ways visuals can be used within dialogs.

View other projects