Photo by charlesdeluvio on Unsplash

Managing Change in Continuous Design

A diagram can be the difference between an organization of “petty kings” doing their own thing and having actionable plans built on a shared identity: What we need is some kind of governance.

High-level: The change process

Change flow
Change flow
  • Does the identified feature/component exist?
  • Do current use-cases cover new needs?
  • Has access been provided to implementors?
  • Is the feature/component built and pushed?
  • Is it reviewed and deemed satisfactory?
  • Buy a matching solution
  • Use existing component/solution
  • Publish a new component/solution

In practice: Responsibilities and artifacts

Responsibilities and artifacts
Responsibilities and artifacts
  • The Figma file and any UI kit that might be made from its assets
  • Storybook with components
  • Component library package (code)

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Mikael Vesavuori

Cloud Software Architect (and Technical Standards Lead) at Polestar