How should information flow between camp participants, guides and the core team

Design Principles:

• Minimize the amount of calls in Camp; How can we work async?
• Information should be easily accessible so people can act without needing permission and handholding

What it looks like:

• 1 main Dashboard that has all general info available (CHAOS DASHBOARD)
• A team specific page (Visual, Dev, Guides etc.)

<aside> 💡 With only 2 pages as your go to, it’s easy not to be lost in the multiple pages of Notion

</aside>

Context:

• Weekly logs from each team are a means to gather key information from Camp in an asynchronous way
• Each operational team and House (4 bands) need to submit a minimum of one log a week to help Camp stewards understand the inner workings of Camp. Additionally, this information may be used to request additional details for Chaos Radio
• Teams are free to track additional information and take more notes/ logs than the required weekly
• Logs are standalone documents with the most context, but info needs to be pulled from them to be more manageable for the Ops team (as the team may not be able to dig through every detail)
  • But logs can be referred for deeper details anytime it’s needed
• Team Stewards (Music, Visual, Dev) can instead take notes where they see fit and add important items to the directly

Process for Bands:

Process for Team Stewards: