# Exemple: Lancement nouveau produit
project_communication_matrix:
  product_launch:
    decisions:
      pricing_strategy:
        responsible: "Product Manager"
        accountable: "VP Product" 
        consulted: ["Sales", "Marketing", "Finance"]
        informed: ["Engineering", "Support", "Leadership"]
        
      feature_prioritization:
        responsible: "Product Manager"
        accountable: "VP Product"
        consulted: ["Engineering", "UX", "Customer Success"]
        informed: ["Marketing", "Sales"]
        
      launch_timeline:
        responsible: "Project Manager"
        accountable: "VP Product"
        consulted: ["Engineering", "Marketing", "Sales"]
        informed: ["All teams"]
        
    communication_channels:
      decisions: "Email + Slack #product-decisions"
      updates: "Weekly all-hands + Slack #product-updates"
      discussions: "Product meetings + Slack threads"
      escalations: "Direct message + Calendar meeting"

## Template SBAR (Situation, Background, Assessment, Recommendation)

### SITUATION
- **Quoi**: Description factuelle de la situation actuelle
- **Quand**: Timeline et contexte temporel
- **Qui**: Parties prenantes impliquées

### BACKGROUND  
- **Historique**: Contexte et événements précédents
- **Données**: Métriques et informations pertinentes
- **Contraintes**: Limitations et dépendances

### ASSESSMENT
- **Analyse**: Évaluation de la situation
- **Risques**: Impacts potentiels identifiés
- **Options**: Alternatives considérées

### RECOMMENDATION
- **Action proposée**: Décision/action recommandée
- **Justification**: Pourquoi cette approche
- **Next steps**: Étapes concrètes et timelines

voice_video:
  primary: "Zoom" # Réunions principales
  secondary: "Google Meet" # Quick calls
  internal: "Slack Huddles" # Discussions équipe
  
instant_messaging:
  primary: "Slack" # Communication principale
  urgent: "WhatsApp/Telegram" # Urgences hors bureau
  notifications: "Push notifications" # Alertes système

real_time_collaboration:
  documents: "Google Workspace / Office 365"
  design: "Figma / Miro"
  code: "GitHub / GitLab"
  project_planning: "Linear / Jira"

documentation:
  knowledge_base: "Notion / Confluence"
  specs_techniques: "GitBook / Slab"
  processes: "Process Street / Notion"
  
project_management:
  tasks: "Linear / Asana / Monday"
  planning: "Notion / ClickUp"
  roadmaps: "ProductPlan / Roadmunk"
  
reporting:
  analytics: "Dashboards (Metabase/Tableau)"
  status_updates: "Email templates + Slack"
  retrospectives: "Retrium / Miro"

## 📱 SLACK BEST PRACTICES

### 🎯 UTILISATION DES CHANNELS
- **Public by default**: Favoriser transparence et inclusion
- **Thread pour discussions**: Garder channels organizés
- **@channel avec parcimonie**: Seulement si vraiment urgent
- **DM pour 1-on-1**: Conversations privées et feedback

### ⚡ COMMUNICATION EFFICACE
- **Context d'abord**: Donner contexte avant de poser question
- **Bullet points**: Structure claire pour infos importantes
- **Emojis reactions**: Acknowledger sans encombrer
- **Search first**: Vérifier si info existe avant de demander

### 🕐 ASYNC RESPECT
- **No response pressure**: Pas d'attente réponse immédiate
- **Status indicators**: Utiliser statut pour disponibilité
- **Time zones awareness**: Considérer fuseaux horaires équipe
- **Meeting notes**: Toujours partager résumés des calls

### 📋 TEMPLATES UTILES
- **Daily standup**: What I did / Will do / Blockers
- **Decision log**: Context / Options / Decision / Reasoning
- **Incident report**: What / When / Impact / Resolution / Prevention

meeting_policies:
  core_hours: "10h-15h CET" # Overlap global team
  
  focus_time:
    morning_focus: "9h-11h" # Deep work protégé
    afternoon_focus: "14h-16h" # Code/création
    
  meeting_types:
    daily_standup:
      duration: "15min max"
      frequency: "Daily"
      format: "Async Slack + optional sync"
      
    sprint_planning:
      duration: "2h max"
      frequency: "Bi-weekly"
      participants: "Dev team + PM"
      
    all_hands:
      duration: "45min"
      frequency: "Weekly"
      format: "Présentation + Q&A"
      
    one_on_ones:
      duration: "30min"
      frequency: "Bi-weekly"
      format: "Manager + Direct report"

meeting_hygiene:
  agenda_required: true
  prep_time: "24h advance"
  recording: "Optional, avec consent"
  notes: "Template standardisé"
  action_items: "Owner + deadline assignés"

daily_practices:
  async_standup:
    channel: "#engineering-standup"
    template: |
      🎯 **Yesterday**: Completed tasks
      📋 **Today**: Planned work  
      🚫 **Blockers**: Issues needing help
      🔗 **Links**: PRs, docs, relevant info
    timing: "Before 10h CET"
    
  code_reviews:
    notification: "Slack integration GitHub"
    response_sla: "24h for feedback"
    approval_required: "2 approvals min"
    
  incident_communication:
    immediate: "Slack #incidents + on-call ping"
    updates: "Every 30min during outage"
    post_mortem: "Within 48h, no-blame culture"

weekly_practices:
  demo_day:
    frequency: "Every Friday 16h"
    format: "Screen share des nouvelles features"
    audience: "Toute l'équipe"
    
  architecture_review:
    frequency: "Bi-weekly"
    participants: "Senior engineers + Architect"
    documentation: "Confluence tech specs"
    
  retrospective:
    frequency: "End of sprint"
    format: "What went well / What didn't / Actions"
    tool: "Retrium ou Miro"

stakeholder_communication:
  product_updates:
    audience: "Leadership + Sales + Marketing"
    frequency: "Weekly"
    format: "Dashboard + written summary"
    content: "Metrics, progress, blockers, plans"
    
  user_research:
    sharing: "Slack #product-research + Notion page"
    format: "Key insights + recordings + next actions"
    distribution: "All product team + relevant stakeholders"
    
  roadmap_updates:
    frequency: "Monthly"
    participants: "Product team + Engineering leads"
    deliverable: "Updated roadmap + rationale doc"

customer_feedback_loop:
  collection: "Intercom + Slack #customer-feedback"
  analysis: "Weekly synthesis meeting"
  action: "Feature requests → Roadmap consideration"
  communication: "Back to customer via Support team"

asynchronous_first:
  documentation:
    principle: "Write it down first, discuss second"
    tools: "Notion pour decisions, Loom pour explications"
    access: "Public by default, searchable"
    
  decision_making:
    async_rfc: "Request for Comments process"
    timeline: "72h pour input avant decision"
    documentation: "Decision log avec reasoning"
    
  status_communication:
    daily: "Async status updates"
    weekly: "Accomplishments + next week goals"
    monthly: "OKR progress + challenges"

synchronous_optimization:
  meeting_efficiency:
    agenda_required: "24h advance + pre-read materials"
    participants: "Essential people only + recording for others"
    time_zones: "Rotate meeting times quarterly"
    
  social_connection:
    virtual_coffee: "15min random pairing weekly"
    team_bonding: "Monthly virtual activity"
    annual_meetup: "In-person gathering when possible"

## 🚨 CRISIS COMMUNICATION PROTOCOL

### PHASE 1: DÉTECTION (0-15min)
1. **Identifier**: Personne détectant l'incident devient Incident Commander
2. **Alerter**: Slack #incidents + ping @on-call team
3. **Évaluer**: Sévérité (P0: Critical, P1: High, P2: Medium, P3: Low)
4. **Escalate**: Si P0/P1, alerter leadership immédiatement

### PHASE 2: RESPONSE (15min-2h)
1. **War room**: Channel Slack dédié #incident-[timestamp]
2. **Roles assignment**:
   - Incident Commander: Coordonne response
   - Engineering Lead: Technical resolution
   - Communications Lead: Internal/external comm
3. **Status updates**: Toutes les 30min sur progress
4. **Stakeholder notification**: Leadership, Sales, Support selon impact

### PHASE 3: RESOLUTION (2h-24h)
1. **Solution déployée**: Engineering validation
2. **Monitoring**: Confirmer résolution stable
3. **Communication**: All-clear message à tous stakeholders
4. **Documentation**: Incident timeline pour post-mortem

### PHASE 4: POST-MORTEM (24-48h)
1. **Blameless analysis**: Root cause, timeline, impact
2. **Prevention actions**: Specific tasks avec owners
3. **Process improvements**: Communication et technique
4. **Sharing**: Learnings avec toute l'équipe

pre_launch: # T-4 weeks
  stakeholder_alignment:
    meeting: "GTM kickoff avec tous stakeholders"
    deliverable: "GTM plan documenté et approuvé"
    communication: "Slack #project-launch + email leadership"
    
  internal_enablement:
    sales_training: "Product demo + pitch deck"
    support_documentation: "FAQ + troubleshooting guide"
    marketing_assets: "Messaging, blog posts, social content"

launch_week: # T-0
  daily_standups:
    participants: "GTM core team"
    format: "Progress, blockers, adjustments needed"
    communication: "Slack thread + dashboard updates"
    
  real_time_monitoring:
    metrics: "Usage, conversions, support tickets"
    escalation: "Immediate Slack alerts si problèmes"
    response: "War room si issues critiques"

post_launch: # T+1 week
  retrospective:
    format: "What worked, what didn't, improvements"
    documentation: "Lessons learned pour futurs launches"
    sharing: "All-hands presentation des résultats"

feedback_mechanisms:
  peer_feedback:
    frequency: "Monthly via 15Five ou Culture Amp"
    format: "Strengths + Areas for growth + Specific examples"
    sharing: "1-on-1 avec manager + self-reflection"
    
  upward_feedback:
    frequency: "Quarterly anonymous survey"
    topics: "Management effectiveness, communication clarity"
    action: "Results shared + improvement actions"
    
  customer_feedback:
    collection: "NPS + support interactions + user interviews"
    synthesis: "Monthly customer insights report"
    action: "Product roadmap input + process improvements"

performance_communication:
  goal_setting:
    frequency: "Quarterly OKR alignment"
    format: "Individual goals tied to team/company OKRs"
    tracking: "Weekly check-ins + public progress sharing"
    
  recognition:
    peer_recognition: "Slack #wins channel + quarterly awards"
    manager_recognition: "1-on-1 praise + public acknowledgment"
    company_recognition: "All-hands shoutouts + career advancement"

cultural_considerations:
  high_context_cultures: # Japon, Allemagne, France
    communication_style: "Plus de contexte, nuances importantes"
    meeting_approach: "Agenda détaillé, préparation extensive"
    decision_making: "Consensus building, longer timeline"
    feedback: "Indirect, focus on improvement"
    
  low_context_cultures: # États-Unis, Australie, Pays-Bas  
    communication_style: "Direct, to-the-point"
    meeting_approach: "Efficient, action-oriented"
    decision_making: "Faster, individual accountability"
    feedback: "Direct, specific, actionable"

adaptation_strategies:
  documentation:
    multilingual: "Key docs traduits si besoin"
    cultural_notes: "Context culturel sur decision making"
    examples: "Use cases adaptés aux marchés locaux"
    
  meeting_facilitation:
    rotation: "Meeting leadership rotates across time zones"
    inclusion: "Specific invitation for input from quiet members"
    follow_up: "Written summary pour clarity"
    
  relationship_building:
    virtual_watercooler: "Culture sharing sessions"
    local_liaisons: "Cultural ambassadors in each region"
    face_to_face: "Annual in-person gatherings"

communication_preferences:
  gen_z: # Born 1997-2012
    preferred: "Slack, Discord, short videos"
    style: "Visual, immediate, authentic"
    feedback: "Frequent, specific, growth-oriented"
    
  millennials: # Born 1981-1996
    preferred: "Email + Slack, collaborative tools"
    style: "Purpose-driven, tech-savvy, team-oriented"
    feedback: "Regular, constructive, development-focused"
    
  gen_x: # Born 1965-1980  
    preferred: "Email, phone calls, structured meetings"
    style: "Independent, direct, results-focused"
    feedback: "Quarterly, outcome-based, pragmatic"
    
  baby_boomers: # Born 1946-1964
    preferred: "Phone, email, face-to-face"
    style: "Formal, detailed, relationship-based"
    feedback: "Formal reviews, respect for experience"

inclusive_approach:
  multi_channel: "Important info via multiple channels"
  format_variety: "Written + verbal + visual options"
  mentoring: "Cross-generational knowledge transfer"
  flexibility: "Accommodate different communication styles"

class CommunicationMetrics:
    def __init__(self):
        self.slack_analytics = SlackAnalytics()
        self.meeting_analytics = MeetingAnalytics() 
        self.survey_analytics = SurveyAnalytics()
    
    def calculate_communication_health(self):
        metrics = {
            # Engagement
            'slack_daily_active_users': self.slack_analytics.get_dau(),
            'message_response_time_avg': self.slack_analytics.get_response_time(),
            'meeting_attendance_rate': self.meeting_analytics.get_attendance(),
            'meeting_on_time_rate': self.meeting_analytics.get_punctuality(),
            
            # Efficiency  
            'meeting_duration_vs_scheduled': self.meeting_analytics.get_duration_efficiency(),
            'action_items_completion_rate': self.get_action_item_completion(),
            'decision_velocity': self.get_avg_decision_time(),
            'rework_due_to_miscommunication': self.get_rework_percentage(),
            
            # Quality
            'communication_clarity_score': self.survey_analytics.get_clarity_score(),
            'information_findability': self.survey_analytics.get_findability_score(),
            'cross_team_collaboration_score': self.survey_analytics.get_collaboration_score(),
            
            # Culture
            'psychological_safety_index': self.survey_analytics.get_safety_score(),
            'feedback_frequency': self.get_feedback_frequency(),
            'conflict_resolution_speed': self.get_conflict_resolution_time()
        }
        
        # Score global pondéré
        weights = {
            'engagement': 0.25,
            'efficiency': 0.35, 
            'quality': 0.25,
            'culture': 0.15
        }
        
        return self.calculate_weighted_score(metrics, weights)

communication_pulse_survey:
  frequency: "Monthly"
  response_rate_target: ">80%"
  
  questions:
    clarity:
      - "Les objectifs et priorités sont clairement communiqués (1-5)"
      - "Je reçois les informations nécessaires pour bien faire mon travail (1-5)"
      - "Les décisions sont expliquées de manière compréhensible (1-5)"
      
    efficiency:
      - "Nos réunions sont productives et bien utilisent le temps (1-5)"
      - "Je peux facilement trouver les informations dont j'ai besoin (1-5)"
      - "Les processus de communication sont efficaces (1-5)"
      
    inclusion:
      - "Je me sens à l'aise de partager mes idées (1-5)"
      - "Mon opinion est valorisée dans les discussions (1-5)"
      - "L'équipe communique de manière inclusive (1-5)"
      
    satisfaction:
      - "Je suis satisfait de la communication dans l'équipe (1-5)"
      - "Les outils de communication répondent à mes besoins (1-5)"
      
  open_ended:
    - "Quel aspect de notre communication fonctionne le mieux ?"
    - "Quel est le plus gros problème de communication actuel ?"
    - "Quelle amélioration aurait le plus d'impact ?"

action_planning:
  threshold_red: "<3.0 average"
  threshold_yellow: "3.0-3.5 average"  
  threshold_green: ">3.5 average"
  
  improvement_process:
    - "Analyse détaillée des réponses"
    - "Workshop équipe sur points d'amélioration"
    - "Plan d'action avec timelines et owners"
    - "Suivi monthly du progress"

executive_communication:
  transparency_levels:
    public: # Toute l'équipe
      - "Vision et stratégie entreprise"
      - "Objectifs trimestriels et progress"
      - "Changements organization majeurs"
      - "Succès et célébrations"
      
    management: # Managers seulement
      - "Décisions RH sensibles en preparation"
      - "Négociations business confidentielles"
      - "Performance issues individus"
      - "Stratégies competitive"
      
    board: # Leadership team seulement
      - "Informations financières détaillées"
      - "Acquisitions potentielles"
      - "Issues légales ou compliance"
      - "Changements leadership"

communication_channels:
  all_hands:
    frequency: "Weekly 45min"
    format: "Présentation + Q&A anonyme"
    content: "Company updates, metrics, recognition"
    recording: "Available pour remote team"
    
  leadership_blog:
    frequency: "Bi-weekly written post" 
    topics: "Vision, learnings, industry insights"
    tone: "Authentic, vulnerable, inspiring"
    distribution: "Company newsletter + Slack"
    
  office_hours:
    frequency: "Weekly 1h open session"
    format: "Drop-in questions avec CEO/Leadership"
    promotion: "Slack reminder + calendar invite"
    notes: "Key takeaways shared afterwards"

## 📢 CHANGE COMMUNICATION PLAYBOOK

### PHASE 1: PREPARATION
**Timeline**: T-4 weeks avant annonce

1. **Stakeholder mapping**
   - Champions: Early adopters qui supporteront le change
   - Influencers: Personnes respectées dont l'opinion compte
   - Resistors: Potential objections et concerns

2. **Message crafting**
   - Why: Reasoning derrière le changement
   - What: Specific changes à attendre  
   - When: Timeline et milestones
   - How: Process et support available

### PHASE 2: ANNOUNCEMENT
**Timeline**: T-0 Change annoncé

1. **Cascade communication**
   - Leadership team briefé en premier
   - Managers briefés avec Q&A prep
   - All-hands announcement avec détails
   - Individual team sessions pour specifics

2. **Multi-channel approach**
   - Verbal: All-hands presentation
   - Written: Detailed email avec FAQ
   - Visual: Slides et graphics explicatifs
   - Interactive: Q&A sessions et feedback channels

### PHASE 3: IMPLEMENTATION  
**Timeline**: T+0 à T+12 weeks

1. **Ongoing communication**
   - Weekly progress updates
   - Success stories et early wins
   - Addressing concerns et obstacles
   - Adjustments based on feedback

2. **Support mechanisms**
   - Training sessions si applicable
   - Change champions network
   - Open feedback channels
   - Regular pulse surveys

### PHASE 4: REINFORCEMENT
**Timeline**: T+12 weeks ongoing

1. **Embedding new norms**
   - Recognition pour adoption
   - Metrics tracking et sharing
   - Story telling sur positive impact
   - Continuous improvement based on learnings

# 1-ON-1 MEETING TEMPLATE

**Date**: [Date]
**Participants**: [Manager] & [Direct Report]
**Duration**: 30min

## AGENDA

### 1. Personal Check-in (5min)
- How are you feeling overall?
- Any personal updates affecting work?
- Work-life balance status

### 2. Work Progress (10min)  
- Key accomplishments depuis dernier 1-on-1
- Current priorities et progress
- Upcoming deadlines ou deliverables

### 3. Challenges & Support (10min)
- Current blockers ou obstacles
- Support needed from manager/team
- Resource requests

### 4. Growth & Development (5min)
- Learning goals progress
- Skill development opportunities
- Career development discussion

## ACTION ITEMS
- [ ] [Action item 1] - Owner: [Name] - Due: [Date]
- [ ] [Action item 2] - Owner: [Name] - Due: [Date]

## NOTES
[Free form notes space]

---
**Next meeting**: [Date & Time]

project_communication_plan:
  project_name: "[Project Name]"
  duration: "[Start Date] - [End Date]"
  
  stakeholders:
    core_team:
      - role: "Project Manager"
        name: "[Name]"
        communication_needs: "Daily progress, blockers, decisions"
      - role: "Tech Lead"  
        name: "[Name]"
        communication_needs: "Technical decisions, resource needs"
        
    extended_team:
      - role: "Marketing"
        communication_needs: "Launch timeline, feature updates"
        frequency: "Weekly"
      - role: "Sales"
        communication_needs: "Feature benefits, competitive positioning"  
        frequency: "Bi-weekly"
        
    executives:
      - role: "VP Product"
        communication_needs: "Progress vs timeline, budget, risks"
        frequency: "Weekly"
        
  communication_methods:
    daily: "Slack #project-[name] async standup"
    weekly: "30min team sync meeting"
    bi_weekly: "Stakeholder update email + dashboard"
    monthly: "Executive review meeting"
    ad_hoc: "Slack for urgent issues, email for FYI"
    
  escalation_path:
    level_1: "Project Manager"
    level_2: "Engineering Manager" 
    level_3: "VP Engineering"
    critical: "CTO + VP Product"
    
  success_metrics:
    - "Project delivered on time"
    - "Stakeholder satisfaction >4/5"
    - "No communication-related delays"
    - "Action items completion >90%"