The Visa Product Design System (VPDS) is built for our community. We invite designers, developers, and teams across Visa to contribute ideas, solutions, and improvements. Whether you’re enhancing a component, proposing a new pattern, or refining guidance—we welcome your input.
Want a quick overview of our contribution process? Take our quiz.
Note: While this quiz is publicly available, the VPDS team is only accepting internal design contributions from Visa employees.
Why contribute?
Contributing to VPDS helps scale accessible, inclusive, and consistent product experiences across Visa. By contributing, you:
- Solve once, share widely: Reusable solutions help other teams and reduce redundant work.
- Promote best practices: Contributions ensure consistent accessibility, usability, and brand standards.
- Showcase your work: Gain recognition from your peers and further the impact of your day-to-day work.
- Foster a stronger design community: Sharing knowledge between teams promotes a healthy design culture.
- Build a system that reflects real needs: Contributions based on real product challenges make the system future-proof.
- Shape the tools you use every day: Your feedback guides the system’s roadmap, priorities, and growth.
Who can contribute?
Anyone at Visa can contribute to VPDS. Whether you’re a product designer, content designer, engineer, accessibility specialist, or researcher—your perspective is valuable. We especially encourage contributions from teams addressing real-world needs or edge cases not yet covered by the system.
What can you contribute?
There are several types of contributions you can make.
New components and patterns
A new contribution proposes a brand new component, pattern, or guidance to be added to the design system. This can be a design, content, or code contribution. Examples include creating a slider component or developing a bucket-picker pattern.Component and pattern enhancements
An enhancement contribution adds a new feature or interaction to existing components, patterns, or guidance. This can be a design, content, or code contribution. Examples include adding a processing state for text buttons or adding new interactions like hot keys.Code bug fixes
A bug fix is a code contribution that resolves issues in our coded components or patterns to ensure their behavior matches expectations. This can be a code contribution only. Examples include fixing accessibility issues, correcting visual discrepancies, or restoring broken interactions.How do contributions help?
Contributions help VPDS evolve to meet the needs of real products. Your participation helps:
- Increase adoption by making the system more comprehensive.
- Improve quality through shared knowledge and testing.
- Make it easier for teams to build the right thing, the right way, faster.
The more we collaborate, the more powerful the system becomes.
What’s the contribution process?
Contributing to VPDS is a structured but flexible process:
- Prep: Review the VPDS backlog (internal only) and existing components or patterns to ensure your idea is unique or an enhancement.
- Intake: Complete the VPDS contribution intake form (internal only) and present your idea to the VPDS Contribution Guild—a group that reviews and recommends contributions.
- Plan: If recommended, your contribution is added to the VPDS backlog and assigned a working group with design, content, development, and accessibility representatives.
- Define: Conduct any necessary discovery and research, using internal or external resources.
- Design: Bring well-developed ideas. The VPDS team is available for support during office hours (internal only) before you submit for final approval.
- Deliver: Once approved, the VPDS team will publish design assets and work with engineering to add development assets to applicable libraries. Changes will be published to the VPDS website, along with quality assessments and communications about your contribution.
Ready to contribute?
Help transform the Visa Product Design System with your contribution.