Vivid Change Process
Vivid uses a phased process to manage changes and enhancements to the design system.
The new ticket should include
- Problem statement
- Detailed use-cases
- Demonstration of shared value
* Additional icon requests will be accepted and scheduled at this stage and do not need to go any further in the process.
Office Hours meeting Agenda
Add a link to the JIRA ticket to provide more information.
Add your name to the item.
The request is discussed with the Vivid team and other attendees at the meeting to establish feasability.
- The request is given an inital estimation of priority and effort
- Within 1 - 2 weeks the Vivid team will communicate the proposed delivery timescale
- Item is added to Road map page
Validate shared value and ensure we understand the change well enough to commit further resources.
Criteria
- Shared value - 2 or more product lines
- Current capacity, skills and tech stack
- Vonage / Vivid strategic goals
Deliverables
- Design brief
- Wireframe / POC
- Scope and timeline
Decisions
- Proceed / Iterate / Defer / Reject
- Assign Priority
- Delegate reviewers / contributors / approvers
Ensure the design meets user and teams needs while upholding brand standards and visual language.
Criteria
- Meets the brief and solves user goals
- Works for all teams concerned
- Usable and accessible
- Meets brand guidelines
Deliverables
- Technical specification
- Detailed design or interactive prototype
- Community feedback
- Usage guidelines
Decisions
- Proceed / Iterate / Defer / Reject
Request item is developed by the Vivid team. Changes are validated in consumers applications before releasing to general availability.
Criteria
- Change is tested in applications by at least 2 teams
- Documentation is signed off
Deliverables
- Alpha and production code
- Assets added/update in Figma live UI kit
- Documentation added to Vivid site
Decisions
- Release / Iterate