The process is simple.

1. Component Inventory - Screenshots of the component in its app

2. Best Practices - Notes, Links, or any additional information from how others are implementing this component

3. Considerations - A place to collect the input from Engineering and Design folks

4. Themes - The considerations are affinity mapped to a theme

5. Scope - Prioritization of the themes into the current work

6. Prototype & Screenshot - This is where folks could share their considerations and ask for adjustments before production; eventually we found a clickable phoenix-storybook instance to be the best

The first components that went through this process required an initial meeting with the team. However, over time folks desired this to be an async process. In order to accommodate this, a Slack channel had to be set up where folks would see a thread for the newest component in the works.

Trust was achieved with the teams. The components were built with everyone's opinions and feedback in mind. We were also able to provide the first Proof of Concept in the form of Time Input to the business stakeholder in a few weeks. It achieved cross-app integration (amidst the different frameworks and dependencies) from a single source of truth.