Skip to end of metadata
Go to start of metadata
Goals
Share stakeholder interviews to create common understanding of how various stakeholders view the design system and how it can the team.
Review button styles. Identify blocking feedback or agree to move forward.
Review, discuss, and decide on the Paragon governance model.
Discussion topics
Time | Item | Presenter | Notes |
|---|
5 | Review action items | | |
5 | New confluence space for design documentation | | |
10 | Review stakeholder interviews | Eugene Kang | Research release at 80%: should we choose a time to announce. We’re releasing the process to the organization Should we add notes on the documentation for each function “what this design system can do for you” What’s it going to take to get people to adopt a design system. What would be ideal for me as an engineer is to say: we’re going have x engineers for once every 4 sprints do a paragon sprint. I need dedicated time to invest in this project and make better for me and everyone. I want buy in from managers. it’s going to take a bit to get this incorporated for teams that can’t use Paragon. we still have a lot of code in an old tech stack that can’t use new designs. what do we do in those scenarios.
|
20 | Review button styles | Gabriel Weinberg | Icon buttons 20px and 24px Define buttons with text + icons Jeff will check state change wcag conformance tooltips with icon button angled button: really interesting. maybe we shouldn’t avoid it too much.
|
20 | Governance model review | Adam Butterworth (Deactivated) | Governance |
Action items
Decisions