🔍
RnDAO workspace
/
😎
Research Agency
/
🤝
Contribution & Compensation
/
Team Syncs
/
📡
Team Communication Framework
📡

Team Communication Framework

DayTouch-pointFormat & DurationPurposeOwner(s)
MondayKick-off “What’s On” PostAsync message (≤ 5 bullets)• Align on priorities• Flag cross-team dependenciesAll, in a shared “#weekly-flowf” channel
Tuesday General Team sync60min VideoCall• Surface blockers early• Quick live decision-makingㅤ
Wednesday Mid-week Pulse (if necessary)Async thread• Bulletpoints any challenges & support neededEach team member, under the “weekly-flowf” channel
FridayWeek-End Wrap-UpAsync bullet brief (≤ 5 lines)• Celebrate wins• Log unresolved items & owners• Capture learnings for retroSmall brief for each team member for open retroactive feedback
Actionable examples
MomentRecommended StructureExample Snippet
Kick-off (Mon)1. Main Goal (one sentence) 2. Key Tasks (3–5 bullets starting with verbs) 3. Dependencies (people / units) 4. Risks / Mitigations (optional)Goal: “Reach out to 150 people” Tasks: • Finalize copy • Get it published in newsletter • Lock in outreach database Dependencies: Marketing needs to sign off on comms
Mid-week Pulse (Wed)• Done: … • Doing: … • Blocked: … (tag) Done: Fianlized Copy Doing: Locke in outreach database Blocked: Get newsletter published by: “Marketing team member”needs to revide outreach
Wrap-Up (Fri)1. Highlights (wins, numbers) 2. Challenges 3. Outstanding → Next Week (owner + ETA)Highlights: Closed x outreach Challenges: Email bounce rate ↑ 4 pp Outstanding: Get newsletter published Next Week: (Cori, Monday)
Channel & Etiquette Rules
  1. One source of truth
      2. Pick a dedicated channel (e.g., #weekly-flow). All 3 asynch touch-points live there, threads keep conversations tidy.
  1. Bullet > Paragraph
      2. • Use verbs first (“Review contract”)
      • One idea per bullet
      • ≤ 2 lines each.
  1. Clear owners & due dates
      • Tag a person (@name) + specify deadline (“→ Wed 18 Jul”).
  1. Response-time SLAs
      2. Async posts: acknowledged with an emoji to signal you’ve viewed the message even if no reply is needed; blockers responded to within 12 h.
  1. Emoji Signals
      2. ✅ task complete ⏳ in progress 🚧 blocker 🙋 help needed 🎉 win
  1. Thread Discipline
      • Reply in the thread, not the main channel, to avoid noise.
      • Summarize any decision at the top for visibility.
Tips to Keep It Flowing
  • Rotate facilitator for Tuesday ice breaker question to share ownership.
  • Automate reminders shared team calendar
  • Time-box calls strictly—stop at minute 15; park deep issues in a follow-up doc.
  • Monthly retro: Use the archived Friday summaries as data for a 30-min retrospective to refine this cadence.
🔍
RnDAO workspace
/
😎
Research Agency
/
🤝
Contribution & Compensation
/
Team Syncs
/
📡
Team Communication Framework
📡

Team Communication Framework

DayTouch-pointFormat & DurationPurposeOwner(s)
MondayKick-off “What’s On” PostAsync message (≤ 5 bullets)• Align on priorities• Flag cross-team dependenciesAll, in a shared “#weekly-flowf” channel
Tuesday General Team sync60min VideoCall• Surface blockers early• Quick live decision-makingㅤ
Wednesday Mid-week Pulse (if necessary)Async thread• Bulletpoints any challenges & support neededEach team member, under the “weekly-flowf” channel
FridayWeek-End Wrap-UpAsync bullet brief (≤ 5 lines)• Celebrate wins• Log unresolved items & owners• Capture learnings for retroSmall brief for each team member for open retroactive feedback
Actionable examples
MomentRecommended StructureExample Snippet
Kick-off (Mon)1. Main Goal (one sentence) 2. Key Tasks (3–5 bullets starting with verbs) 3. Dependencies (people / units) 4. Risks / Mitigations (optional)Goal: “Reach out to 150 people” Tasks: • Finalize copy • Get it published in newsletter • Lock in outreach database Dependencies: Marketing needs to sign off on comms
Mid-week Pulse (Wed)• Done: … • Doing: … • Blocked: … (tag) Done: Fianlized Copy Doing: Locke in outreach database Blocked: Get newsletter published by: “Marketing team member”needs to revide outreach
Wrap-Up (Fri)1. Highlights (wins, numbers) 2. Challenges 3. Outstanding → Next Week (owner + ETA)Highlights: Closed x outreach Challenges: Email bounce rate ↑ 4 pp Outstanding: Get newsletter published Next Week: (Cori, Monday)
Channel & Etiquette Rules
  1. One source of truth
      2. Pick a dedicated channel (e.g., #weekly-flow). All 3 asynch touch-points live there, threads keep conversations tidy.
  1. Bullet > Paragraph
      2. • Use verbs first (“Review contract”)
      • One idea per bullet
      • ≤ 2 lines each.
  1. Clear owners & due dates
      • Tag a person (@name) + specify deadline (“→ Wed 18 Jul”).
  1. Response-time SLAs
      2. Async posts: acknowledged with an emoji to signal you’ve viewed the message even if no reply is needed; blockers responded to within 12 h.
  1. Emoji Signals
      2. ✅ task complete ⏳ in progress 🚧 blocker 🙋 help needed 🎉 win
  1. Thread Discipline
      • Reply in the thread, not the main channel, to avoid noise.
      • Summarize any decision at the top for visibility.
Tips to Keep It Flowing
  • Rotate facilitator for Tuesday ice breaker question to share ownership.
  • Automate reminders shared team calendar
  • Time-box calls strictly—stop at minute 15; park deep issues in a follow-up doc.
  • Monthly retro: Use the archived Friday summaries as data for a 30-min retrospective to refine this cadence.