Decision Documentation for Communication

  • For long term projects, without customer level 'release', (Eg While Implimenting a design System Private or Broken Links
    The page you're looking for is either not available or private!
    ) it is good to have a time based change log
  • Changelog as a consistent communication toolChangelog as a consistent communication tool

    Write changelogs Consistently. (I prefer Outline Notes format). It provides a clear idea of what the team has achieved and when.
    Also, it communicates to the user about new features, the v...
  • FigmaFigma

    Figma is a vector graphics editor and prototyping tool and is primarily web-based.




    Source

    Figma Website
    §Design

    version control is not that efficient It doesn't provide Version per frame, comparison or search inside push note. Hence we use Google Doc.

Version Numbering

  • Two number version system
    • XX.YY
  • YY is any changes made in Single Source of Truth
    • Any designer can add it
    • Consider it more as Ship / Show of Ship-Show-AskShip-Show-Ask

      Ship/Show/Ask - PR with ability to make changes
      Changes are categorized to three

      Ship (Merge to main, without review)
      Show (PR and Merge to Main)
      Ask (PR, then discuss, ...
  • XX is bi-weekly design meeting count
    • Objective is to do the Ask part of Ship-Show-AskShip-Show-Ask

      Ship/Show/Ask - PR with ability to make changes
      Changes are categorized to three

      Ship (Merge to main, without review)
      Show (PR and Merge to Main)
      Ask (PR, then discuss, ...
    • Decisions are made, SST is updated

Source

  • §Design Private or Broken Links
    The page you're looking for is either not available or private!