Team coordination tools SCQH

Tue, 21 Apr 26 · Yoyo, Armelle, Valerie, Jarlath, Matthew

Meeting notes Granola

Team Coordination Tools Decision

• Meeting purpose: decide on coordination tools and ensure team training
• Goal: one central place for documents, project visibility, and collaboration
• Need decision today to move forward with implementation

Core Questions Framework

• Refined questions from morning session with Rufus
• Focus on simplifying processes for team efficiency
• Framework addresses: portfolio view, weekly focus, document conventions, task management

Team Visibility Challenges

• Matthew (remote, time zone difference) needs better project awareness
  • Missing drive-by conversations and informal updates
  • Wants visibility into what others are working on
  • Currently not invited to morning standups
• Solution: transcript summaries and standup channel updates
  • Rufus adding Matthew to standup calendar for transcript access
  • Potential automation: transcript → bullet points → standup channel

Document Management Structure

• Portfolio map: Rufus responsible (with Armelle)
  • Authoritative index of initiatives/projects with owners
  • Links to initiative documents and root folders
• Ideas inbox: Google Drive folder for proposals/concepts
  • Different from full initiatives (e.g., heart circle proposal vs new major project)
  • Valerie can capture residency ideas and feedback here
• Weekly meetings: Monday format with concerns/proposals section
  • Sociocratic approach for surfacing new ideas
  • 10-15 minute open space for team input

Aside re strategy

• Rufus discussed concept of “striping number” - how many different projects per day/week
• Goal: reduce team striping number, work on same initiative together
• Move toward more product-like outputs rather than service-type outputs
  • Products: courses, videos, papers (make once, use repeatedly)
  • Services: residencies, events (require ongoing maintenance)
• Experiment idea: team sprints on single initiative for days/weeks

Digital Asset Management

• Jarlath managing archive of audio/video/visual materials
• Challenge: keeping system updated as live resource
• Approach: centralized location with team access
• Need management strategy and regular maintenance schedule

Document Conventions Decisions

• Strategic documents: portfolio map in strategy repo
• Project documents: decided by individual projects
• Task coordination: up to project preference (GitHub issues, other tools)
• Knowledge base: consolidate in “the tao” (Life Itself handbook)
• Archive/raw material: default Google Drive, one folder per project
• Incoming inputs: ops email, comms channels

Previous content log

• Reference to existing system: https://github.com/life-itself/comms-archive-2026-03-19/tree/main/clog
• Previous content logging work done with Lauren
• System existed but fell into disuse with smaller team

Technical Setup Issues

• Google Drive provisioning doesn’t auto-show Team Drive
• Matthew couldn’t see file architecture initially
• Need better onboarding for new team members
• Balance between documentation and maintenance overhead

Ideas capture at end

• Valerie: Ideas Inbox setup for residency concepts and feedback
• Archive organization by theme (food, relational practice, etc.)
• Website updates: only 25 residencies currently shown
• Need more autonomy for team to update website archives

Use the tao

• Tao as central handbook for Life Itself
• “Great convergence” - consolidate multiple information sources
• Decision: create summary page in tao within next hour
• Single point of entry for team resources

Next Steps

• Rufus & Armelle: create tao summary page (within 1 hour)
• Jarlath & Matthew: follow-up meeting on digital asset management
• Team training session once tool decisions finalized
• Monday weekly meetings start with new format
• Matthew added to standup calendar for transcript access

Rufus notes to self

Aside re strategy

• Rufus went off to discuss the concept of striping number
• Reducing the striping number
• More product like outputs (rather than services type outpus)

Previous content log

• https://github.com/life-itself/comms-archive-2026-03-19/tree/main/clog - previous content log.

Ideas capture at end

• Valerie like Ideas Inbox: set that up …
• archive.lifeitself.org: log stuff to capture. …

Use the tao …

• Tao is our handbook
• Do we converge strategy with it?
• Do we converge other handbooks with it
• What about community site
• What about comms site …

The "great convergence" …