Skip to content

communication.md

Latest commit

 

History

History
132 lines (105 loc) · 3.82 KB

communication.md

File metadata and controls

132 lines (105 loc) · 3.82 KB

Communication Unwritten Rules

Overview

Effective communication is crucial for team success. These guidelines help maintain clarity, respect, and productivity in our interactions.

Core Principles

1. Default to Transparency

  • Share progress regularly, even if incomplete
  • Communicate blockers early
  • Document decisions publicly
  • No surprises in retrospectives

2. Assume Positive Intent

  • Start with curiosity, not criticism
  • Ask clarifying questions before making assumptions
  • Give benefit of the doubt in written communication
  • Remember we're all working toward the same goals

3. Be Direct but Kind

  • Provide honest feedback constructively
  • Address issues promptly and privately first
  • Praise publicly, critique privately
  • Use "I" statements when expressing concerns

Communication Channels

Teams Guidelines

Channel Usage

Channel Purpose Response Time
General Company-wide announcements No response expected
Dev Team Development discussions 2-4 hours
Urgent Critical issues 15 minutes
Random Non-work discussions Optional
Help Technical questions 1-2 hours

Teams Etiquette

  • Use threads for detailed discussions
  • @here only for time-sensitive team matters
  • @channel only for critical urgent issues
  • DMs for private or sensitive topics
  • Status updates when away or focused

Message Formatting

✅ Good: "Hey team, I'm blocked on the API integration. Error details in thread. Any ideas?"
❌ Bad: "Nothing works!!!"

✅ Good: "@john Can you review PR #123 when you have time today?"
❌ Bad: "review pls"

Async Communication

Best Practices

  • Over-communicate context - Others lack your background
  • Use bullet points for clarity
  • Include timezones when scheduling
  • Set expectations for response times
  • Use recordings for complex explanations

Documentation First

  • Write it down before asking
  • Update docs after solving problems
  • Link to documentation in discussions
  • Create FAQs for repeated questions

Decision Making

For technical and business decisions, use the Decision Making Template to document comparisons and rationale.

Remote Communication

Video Call Best Practices

  • Camera on for team meetings (when possible)
  • Good lighting and audio quality
  • Minimize background noise
  • Be present - Avoid multitasking
  • Record important sessions

Feedback Culture

Giving Feedback

  • Be specific and actionable
  • Balance positive and constructive
  • Timely - Don't wait for reviews
  • Focus on behavior, not personality
  • Offer help and resources

Receiving Feedback

  • Listen without defending
  • Ask clarifying questions
  • Thank the person
  • Reflect before responding
  • Follow up on improvements

Do's and Don'ts

Do's

✅ Acknowledge messages even if you can't respond fully
✅ Update tickets/issues with progress
✅ Celebrate wins and learn from failures
✅ Ask questions - No question is stupid
✅ Respect focus time and deep work blocks
✅ Use inclusive language
✅ Proofread before sending

Don'ts

❌ Ghost on conversations
❌ Make assumptions about availability
❌ Use ALL CAPS (seen as shouting)
❌ Discuss personnel issues publicly
❌ Forward emails without permission
❌ Schedule meetings without agenda
❌ Interrupt or talk over others

Cultural Considerations

  • Be aware of cultural holidays
  • Respect different communication styles
  • Avoid idioms that don't translate
  • Be patient with non-native speakers
  • Learn about teammates' backgrounds

Remember

  • Written communication lacks tone - be extra clear
  • When in doubt, over-communicate
  • Kindness and respect cost nothing
  • We're all human - mistakes happen
  • Building trust takes time, losing it takes seconds