🎨 Design Team

• Multiple platform directions are not helpful
• Features across platforms should be considered and worked on as close to simultaneously as possible
• Reduces efficiency of work to drop and re-pick up context with months apart
• Having multiple CCs involved from an early stage has positive impact for marketing so that comms can be clearer
• 3 Amigos may need to be flexible on the "3" part

📄 Docs Team

• Concern about starting with a feature with a figma file
  • It is uncertain what is implemented and what is not
• Developers write on github, doc team have to hunt down the epics or issues
  • Also it is uncertain what will be included in what release
• Is there shared workspace for all of the activity that the CCs work on
  • Consider Crews workspace template
• Formalise the process of share a screenshot of the feature in the documentation, and release articles
• Changes to features need to be documented somewhere
  • Record somehow that a change decision was made.
  • Explore automation process to highlight when feature changes are made
• When writing an article about a new feature identify who the developers are
• Automate alerting teams when certain stages of a feature lifecycle have been met.
  • Possibly link into label inclusion for same with QA

🖥️🔍 Desktop QA

• The development process doesn't include user stories during a particular point
• Issues lack an entry point in the development lifecycle
• We should have some kind of business ownership of building processes
• Revenue needs to have specific goals from a particular role
• We should have processes that allow us to compete with small startup team in the web3 space.