Design Process Overview:

• First, ensure that none of the existing components can address the issue at hand. It's best to confirm this before initiating a request for a new component.
• Next, collaborate with the Design System (DS) team; a solution might be identified at this stage, such as adding a new variation or modifying existing elements.
• If a new component is deemed necessary, the designer will develop it within the context of the case.
• Afterward, it will be sent to the DS team, which will prepare it for production, verify consistency, finalize all required states, and document everything. Finally, the design will be reviewed by the initiating designer.

Flow of creating a request for a component:

Interaction with the DS team will be built on a ticket system.

• A request to add a component is created immediately after the need arises, before any syncs and interactions (in other words - Ticket is the entry point into the process).
• Within the framework of the ticket we sync/ decide to add a component/ search among ready-made solutions.
• After making a decision to add the component to the task body, the designer attacks the developments within the case and transfers the task to the DS team.
• After the component is worked out in the DS team, the designer is reviewed
• After the review stage, the component is sent to the producer and gets into the storybook