Light

Proposal Template

Use this template to document any proposed addition or modification to the Helix design system. Complete every section before bringing the proposal to a design critique. Incomplete proposals will be returned.

Header

FieldValue
Proposer
Date
TypeNew/Modified Component · New/Modified Variant · New/Modified Token · New/Modified Pattern
PriorityUrgent · Planned · Nice to Have

What Are You Proposing?

A short title and a clear description of the change. Describe what you're proposing and the problem it solves — what user or product need does this address?

Title:

Description:


Gap Analysis

What is specifically missing or insufficient?

Describe exactly what the current system lacks. Do not just say "there is no X" — explain why existing options don't work.

Current workarounds in use

How is this problem being handled today? List any one-off solutions, snowflakes, or inconsistencies that exist because of this gap.


Visual Evidence

This section is required. A proposal without visuals will not be reviewed.

Current state

Show how the current system handles this use case today. Include a Figma link and a screenshot.

Figma link (current):

Screenshot (current state):

Proposed design

Show what the change looks like. Include a Figma link and a screenshot.

Figma link (proposed):

Screenshot (proposed design):

System conventions alignment

Confirm that the proposed design uses Helix conventions. Fill in which tokens are used.

PropertyToken Used
Background color
Text color
Border / stroke
Spacing
Typography
Border radius
Shadow
Icon (Lucide name)

If your proposal cannot align with an existing token, explain why and what new token you are proposing.

Alternatives considered

What other approaches did you explore? Why were they rejected? Showing your work here is important — it demonstrates that the proposed solution is the right one, not just the first one.

AlternativeWhy it was rejected

Impact Assessment

Products and surfaces affected

List the products, pages, or surfaces that will use this change.

Impact on existing components

Does this change require updates to existing components? Does it break any current usage patterns?

Accessibility considerations

How does this change affect accessibility? Have you accounted for keyboard interaction, focus states, screen reader behavior, and color contrast?


Acceptance Criteria

What does "done" look like? List the specific conditions that must be true for this proposal to be considered fully implemented.

  • [ ]
  • [ ]
  • [ ]

Open Questions

List any unresolved questions or concerns you want to raise during the critique.


Critique Notes

To be filled in during or after the critique session.

Date of critique:

Attendees:

Feedback and discussion summary:

Decision:

  • Approved — proceed to design & build
  • Approved with changes — see notes
  • Deferred — revisit when:
  • Rejected — reason:

Next steps:


Template version: 1.0 — Last updated: March 2026