Internal Communications Skill

This skill helps you compose various internal communications using professional, company-standard formats.

When to Use This Skill

• Writing weekly 3P updates (Progress, Plans, Problems)
• Creating company newsletters
• Drafting status reports for stakeholders
• Writing leadership updates
• Composing project updates
• Documenting incident reports
• Any internal team communication

Communication Types

1. 3P Updates (Progress, Plans, Problems)

Brief executive updates (30-60 seconds read time) on team status.

Format:

[emoji] [Team Name] (Date Range)

Progress: [1-3 sentences - shipped features, milestones, completed tasks]
Plans: [1-3 sentences - high-priority work for next period]
Problems: [1-3 sentences - blockers, resource gaps, setbacks]

Guidelines:

• Be data-driven and concise
• Use metrics when available
• Small teams = granular tasks; large teams = strategic milestones
• Tone: matter-of-fact, professional

2. Company Newsletter

Organization-wide communications with broader context.

Sections:

• Executive summary
• Team highlights
• Key metrics
• Upcoming events
• Recognition

3. Status Reports

Detailed progress reports for stakeholders.

Format:

• Project name and period
• Objectives and progress
• Risks and mitigations
• Next steps
• Resource needs

4. Leadership Updates

Strategic communications for executive audience.

Focus on:

• High-level progress
• Strategic implications
• Decision points needed
• Resource allocation

5. Project Updates

Focused updates on specific initiatives.

Include:

• Milestone status
• Timeline adherence
• Blockers and dependencies
• Team contributions

6. Incident Reports

Post-incident documentation.

Structure:

• Timeline of events
• Impact assessment
• Root cause analysis
• Remediation steps
• Prevention measures

How to Use

Basic Request

Write a 3P update for the Engineering team for last week

With Context

Create a status report for the Q1 Product Launch project.
Progress: Completed design phase, started development.
Blockers: Waiting on API documentation.

From Multiple Sources

Draft a company newsletter based on:
- Sales hit 120% of target
- Engineering shipped new dashboard
- Marketing launched campaign
- HR onboarded 5 new team members

Best Practices

1. Be Concise: Respect reader time
2. Use Metrics: Quantify when possible
3. Be Specific: Avoid vague statements
4. Action-Oriented: Clear next steps
5. Appropriate Tone: Match the audience
6. Proofread: Check for clarity and errors

Information Gathering

When drafting communications, I can help gather context from:

• Slack messages (high-engagement posts)
• Documents and files
• Previous communications
• User-provided bullet points

Output Formats

• Plain text for quick sharing
• Markdown for documentation
• Email-ready format
• Presentation bullet points