Figma Standardization Guide

A shared system to keep Figma files clean, consistent, and scalable across Dell.

Adopted by 18+ teams
Dell Game Changer Award

Status Indicators

Dev Note

Status Indicators

Flow Titles

Feature Overview

Change Log

File Structure

Feature Overview

Figma
Standardization
Guide

A shared system for clean, consistent files

Status Indicators

Dev Note

Status Indicators

Flow Titles

Feature Overview

Change Log

File Structure

Feature Overview

Figma
Standardization
Guide

A shared system for clean, consistent files

Status Indicators

Dev Note

Status Indicators

Flow Titles

Feature Overview

Change Log

File Structure

Feature Overview

Figma
Standardization
Guide

A shared system for clean, consistent files

Status Indicators

Dev Note

Status Indicators

Flow Titles

Feature Overview

Change Log

File Structure

Feature Overview

Figma
Standardization
Guide

A shared system for clean, consistent files

What is Figma Standardization Guide?

The Figma Standardization Guide is a set of shared practices and components that made design files easier to navigate and manage across Dell’s design org.

Challenge

Inconsistent file structures slowed work

Each team organized Figma files differently, which made reviews confusing, onboarding slow, and collaboration inconsistent.

My role

Leading the effort to standardize Figma

I interviewed designers, audited files, and built a scalable system with shared components like thumbnails, ticket covers, status indicators, and changelogs. I refined the system with feedback and aligned it with Dell’s design system to ensure consistency and scalability.

A clear guide for team members

A clear guide for team members

Created a Figma playbook that explained file structure, naming rules, and asset usage, making onboarding smoother and helping new designers get productive quickly.

Created a Figma playbook that explained file structure, naming rules, and asset usage, making onboarding smoother and helping new designers get productive quickly.

File Thumbnail

Designed standard thumbnails with feature name, project info, and designer details for quick scanning.

Page Structure

A consistent file structure helped everyone find what they needed, fast. Files followed the same layout: overview → flows → components → archive.

Flow Titles & Descriptions

Flow Titles & Descriptions

A standardized layout with clear titles and summaries to make flows easy to understand, organize, and navigate for teams.

A standardized layout with clear titles and summaries to make flows easy to understand, organize, and navigate for teams.

Example

Feature Overview

Feature Overview

This displays Jira ID, feature name, and status at a glance. It clarifies scope and ownership, making design reviews and onboarding faster.

This displays Jira ID, feature name, and status at a glance. It clarifies scope and ownership, making design reviews and onboarding faster.

Example

Status Section Bars

This is used to clearly mark the progress of each design section, helping teams focus on finalized work during reviews.

Example

Change Logs

Change Logs

Change Logs are embedded in design files to track updates. Color-coded by contributor, it helps teams quickly see what changed, when, and by whom.

Change Logs are embedded in design files to track updates. Color-coded by contributor, it helps teams quickly see what changed, when, and by whom.

Sticky Notes

Sticky Notes

Sticky Note is used for quick meeting notes, providing an alternative to numerous inline comments. It lets designers capture personal notes or feedback in one organized place.

Sticky Note is used for quick meeting notes, providing an alternative to numerous inline comments. It lets designers capture personal notes or feedback in one organized place.

Dev Notes

Dev Notes

Dev Notes are placed next to wireframes to share technical details and improve async communication with PMs and developers.

Dev Notes are placed next to wireframes to share technical details and improve async communication with PMs and developers.

Result & Impact

Widely adopted across teams and recognized for improving efficiency and collaboration

This has been picked up by over 18 teams and won a "Game Changer Award" for improving design efficiency. It made Figma files easier to use for PMs, engineers, and new designers. The playbook is now the go-to template for new features, and it’s helped teams work better together by making things clearer and reducing confusion.

Do you want to learn more about this project?
Let's talk!