Activity: Update process
  • 31 Jan 2023
  • 1 Minute to read
  • Dark
    Light

Activity: Update process

  • Dark
    Light

Article Summary

Work together with you Makers to determine how revisions to the system are made and who is responsible for them.

Once reviews take place, any revisions required need to be documented and implemented. This process is key for design system makers to define responsibility and have clear delineation in tasks.

Stakeholders: 

  • Designer
  • Developer

Answering the activity's questions

Think through how you will approach each of the following questions as part of your review plan. You can include the answer within DSM as part of your governance process documentation.

Steps Release Tracking How are revisions recorded? Do you maintain a JIRA, Asana, or Trello board with tasks? Request Process Will the requester be included in revisions? If a user requests an update to the system that requires revisions, will they be a part of that process? Or notified in any way? Implementation Who is responsible for the implementation? Does a core design system team make revisions to the design/code/documentation or is the original requester responsible? Uploads Who uploads the content? Define responsible parties for pushing Sketch Library, Storybook and documentation updates.

Steps

  1. Release Tracking
    • How are revisions recorded?
    • Do you maintain a JIRA, Asana, or Trello board with tasks?
  2. Request Process
    • Will the requester be included in revisions?
    • If a user requests an update to the system that requires revisions, will they be a part of that process? Or notified in any way?
  3. Implementation
    • Who is responsible for the implementation?
    • Does a core design system team make revisions to the design/code/documentation or is the original requester responsible?
  4. Uploads
    • Who uploads the content? Define responsible parties for pushing Sketch Library, Storybook and documentation updates.

Was this article helpful?