Start contributing to VPDS

Prep: Make sure it’s needed

Before proposing a new component, pattern, or enhancement, make sure your contribution is necessary. Start by exploring existing resources and checking the VPDS backlog.

• Explore existing resources: Browse components and patterns to avoid duplication.
• Check the VPDS backlog: Search for open items labeled “contribution” or “in progress” in the VPDS backlog (internal only).
  
  

Note: At this time the VPDS team is only accepting internal design contributions from Visa employees.

Questions to ask

• Does your contribution solve a common problem?
• Is it flexible enough to serve multiple use cases?
• Will it help other design system users?
• Does it replicate anything in the system? If so, is there evidence that your solution is more effective?
• Is it an enhancement of an existing area of the system, or something new?
• Does it align with Visa’s accessibility and brand standards?
• What impact could your solution have on existing implementations?
• Do you have the necessary resources—such as people, time, and tools—to ensure the contribution meets VPDS standards?
  
  

Intake: Propose your idea

Once you’ve confirmed there’s a gap or opportunity, formally propose your idea. The VPDS team will review your submission, provide feedback, and schedule follow-ups if needed.

1. Submit an intake form: Complete the VPDS contribution intake form (internal only) and include all required documentation.
2. Initial review: The VPDS team will review your submission, provide feedback, and schedule follow-ups if needed.
3. Present to the contribution guild: If your proposal moves forward, you’ll be invited to present it to the VPDS guild. This meeting provides the opportunity to explain your idea, answer questions, and gather additional feedback.
4. Guild decision: After your presentation, the contribution guild will review and vote on your proposal, considering backlog priorities, business needs, and feasibility. You’ll be notified once a decision is made.

Plan: Align and scope

If your idea is approved, you’ll move into the planning phase. Here, you and the VPDS team will work with you to define the scope and clarify roles.

1. Form a working group: Collaborate with the VPDS team—including design, content, development, and accessibility experts—to align on roles and responsibilities.
2. Define the scope: Decide together what’s in and out of scope, establish required deliverables, and set timelines.
3. Clarify support pathways: Set up check-ins with your VPDS working group or attend office hours (internal only) for additional support.

Define: Discovery and research

In this phase, gather additional information or use existing research to outline what’s needed, why it’s needed, and how it might be used across different contexts.

1. Conduct or gather existing research: Interview stakeholders to identify pain points and understand constraints (such as accessibility, responsiveness, interactivity, and localization). Research industry trends and best practices from organizations like the Nielsen Norman Group.
2. Competitive analysis: Review how other teams at Visa or other design systems have addressed similar needs. Collect screenshots, prototypes, or code, and document relevant solutions.
3. Create a design brief: Clearly document the design needs using the Contribution template (internal only) in Figma.

Design: Create and refine

Contributors are responsible for creating and refining the design based on the design brief, while the VPDS team provides feedback throughout.

1. Sketch and draft: Sketch your idea or refine existing designs. Begin drafting initial guidelines—such as when to use or not use the component, best practices, and more—using the Usage guidelines template (internal only).
2. Prototype and outline specs: Refer to the Nova Figma library to turn your sketches into prototypes. Document states, redlines, platform scaling, and details using the VPDS specs checklist (internal only).
3. Refine and review: Continue refining your design and documentation, ensuring all states, redlines, and scaling considerations are captured. Keep deliverables up to date and respond to VPDS feedback as needed.

Deliver: Approval and handoff

Contributors are responsible for finalizing and delivering all required designs and documentation. The VPDS team will review and provide any final feedback before approval.

1. Present to the VPDS team: Walk the team through your designs and documentation, highlighting key decisions and addressing questions.
2. Apply final feedback: Gather any final feedback and make necessary updates.
3. Submit final designs and documentation: Package and deliver the final designs and usage guidance to the VPDS team for approval and inclusion in the system.

Want to contribute code or report a bug?

Learn how you can contribute code or report issues.