2026 Figma Organization

Figma Structure

Enterprise
├─ Workspace (Consumer Digital)
│  ├─ Teams
│  │  ├─ Projects
│  │  │  └─ File - Work (Cover) 1.1
│  │  ├─ Page Structure 1.2
│  │  │  └─ Section 1.3
│  │  └─ File - Libraries (Extensions)

Reference: Figma 101 Niche

Context

Overview
Problem
Context	Previous Figma work groups
Limitations	Plugins need to get approved
Goals

MyHumana

List of Figma file structure challenges that we should try to address

Folks ignore branches and only go into the main file
Sometimes things within the branch don't get built before the next thing is picked up
Multiple scrum teams may be developing on one singular screen
Do we still need a source of truth? (what's live TODAY) (From onboarding perspective - yes. I'm always being asked for the 'live' version because it is an experience that spans MyH-ip)
No time in sprint to integrate anything into a source of truth (if that's what we want)
7 different libraries to pull assets/styles from is overwhelming
Nucleus is just aUl kit and does not give guidance on layout, content, and hierarchy
App doesn't have any Figma components
Can't touch what's currently being developed (separate working stuff from "ready for dev" stuff that's already assigned to their stories)
Many designs are on a Mac Air that aren't as powerful
Historically challenging to have a single file with multiple designers working/updating in it
File naming conventions, how do we ensure they are semantically current (like when "Plan benefits" becomes "Plan" or "My Meds" becomes"Pharmacy")
Should we have a master web prototype?
Future-state thinking outside of the day-to-day work

Approach

Option	Description
Library Assets	Each team maintains their own system of organization, i.e. local cover components
Community Plugins and Widgets	Note: Not all community plugins would get approved.
Local Plugin/Widget	Educate community on Widgets vs Plugins

Proposal

1.1 Plugins	Description
Covers	Unify cover formats across workflows, streamline maintaince and syncing
Context	Build context to support scaling teams of all sizes and enable more transparency for other designers and leadership.
Workflow	Empower teams to continue to leverage workflows that best suit teams delivery maturity

1.2 Widgets	Description
Changelog	To reduce clicks for various team members to contribute and maintain a log of updates in product development lifecycle
Checklist	To enhance to be specific to Humana ways of working
Note	Seperate from Figma comment, goal is for this to be an aid to inform change logs

1.3 Cover	Description
Status	Dropdown: Discovery, Ideation, Wireframes, In Progress, In Review, Complete, Library
Brand	Dropdown: Humana, MyHumana, Reliance, CenteWell, Go365, CarePlus
Title	Examples: Dashboard, Registration, Claims, Benefits, etc.
Subtitle	Examples: PI, Year, MVP, etc.

1.4 Pages	Description
Index	Table of Content with link to pages, brief executive summary, status
Version History	Example: New Feature, Enhancement, Defect, etc.

1.5 Sections	Description
Context	Table of Content with link to pages, brief executive summary, status
Goals	Why are we doing this?
Status	Status syncs with index page
Links	i.e. Jira, Copy Deck, Other?
Version History	Example: New Feature, Enhancement, Defect, etc.

Section Treatment	Description
Figma Section	Native Figma section grouping with support for dev ready
Horizontal	Local Text Banner resized per screen sections
Vertical	Local Text Banner resized displayed first on left before screen sections

1.5 Branch consideration

Same as 1.4 or 1.5 depending on scope of work being actively worked on

Workflows

By Design Framework

Workspace
├─ Team (Consumer Digital)
│  ├─ File
│  │  ├─ Page
│  │  │  └─ Cover
│  │  │  └─ Index
│  │  │  └─ Components
│  │  │  └─ Research
│  │  │  └─ Design WIP
│  │  │  └─ Ready for Dev
│  │  │  └─ Archive

By Timeframe

Workspace
├─ Team (Consumer Digital)
│ ├─ File
│ │ ├─ Page
│ │ │ └─ Cover
│ │ │ └─ Index
│ │ │ └─ PI 26.#.# ? — MM/DD
│ │ │ └─ Jira Number? — MM/DD
│ │ │ └─ Feature - MVP v#? — MM/DD
│ │ │ └─ Archive

By Iteration

Workspace
├─ Team (Consumer Digital)
│ ├─ File
│ │ ├─ Page
│ │ │ └─ Cover
│ │ │ └─ Index
│ │ │ └─ Iteration MM/DD
│ │ │ └─ Iteration MM/DD
│ │ │ └─ Iteration MM/DD
│ │ │ └─ Archive

Glossary

Part	Description	Note
Cover	Cover thumbnail for file	Previously explored from team
Index	Allow teams to easily navigate to a specific page	Is Index universally known? Does this need to be quick access? Directory? Other?
Components	Component library, variants, assets etc	Do we really want to get in the business of maintaining multiple files with components or is the intent strictly to be used within this page only? If goal is to use across multiple files, consider local library.
Research	UX flows, Architectures, Systems and additional Documentation etc.	Does this need to be embeded within file or should this be seperated out to UX Research Repository?
Design WIP	Designs, Prototypes, Pros & Con lists, all in varieying states
Ready For Dev	Pixel perfect designs, high-fidelity prototypes with specs	Is this used globally by dev teams?
Archive	Archive and solutions that didn’t solve the problem or aren’t feasabile
Sections	The grouping of content within a page for wayfinding

References

Appendix: