Communication Examples #

These playbooks help streamline team communication by automating regular status updates, standups, and information sharing workflows.

Team Standup Automation #

The Request: “Automatically collect yesterday’s work updates from our tools and post a team standup summary.”

Generated Playbook:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

# Automated Team Standup
Collect and summarize team activity for daily standup meetings.

## Steps

- Get completed Linear tickets from yesterday by team member

- Fetch merged GitHub pull requests from yesterday

- Identify any tickets marked as "blocked" or overdue

- Format as team standup summary:
  
  🚀 Daily Standup - [date]
  
  **Yesterday's Wins:**
  • [X] tickets completed • [Y] PRs merged
  
  **Completed Work:**
  • @[Name] - [ticket title] • [PR title if any]
  • @[Name] - [ticket title] • [PR title if any]
  
  **Blockers:**
  • [Any blocked tickets or issues, or "None"]
  
  **Today's Focus:**
  • [Tickets in progress or planned for today]

- Post to #daily-standup Slack channel at 8:30 AM before team meeting

## Trigger
- Run Monday through Friday at 8:30 AM

What this playbook does:

• Gathers yesterday’s completed work from Linear and GitHub
• Identifies any current blockers that need attention
• Creates a summary that saves time in standup meetings
• Posts before the meeting so people can review

Key learning: This shows how to combine two related data sources (Linear + GitHub) for a single workflow purpose.

Customer Support Summary #

The Request: “I want a daily summary of new customer support tickets from Linear posted to our team Slack channel.”

Generated Playbook:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

# Daily Customer Support Summary
Monitor new support tickets and highlight urgent issues.

## Steps

- Query Linear for tickets created in the last 24 hours with "customer-support" label

- Analyze ticket priorities and identify urgent issues

- Count total tickets, urgent tickets, and unassigned tickets

- Format summary with key metrics and trending issues:
  
  🎫 Support Summary - [date]
  
  **Today's tickets:** [X total] • [Y urgent] • [Z unassigned]
  
  **Urgent tickets:**
  • [Ticket title] - [Customer] - [Brief description]
  
  **Trending issues:**
  • [Pattern or recurring theme]
  
  **Action needed:**
  • [Any immediate escalations or concerns]

- If no urgent tickets: focus on positive metrics and trends

- Post formatted summary to #customer-support Slack channel

## Trigger
- Run Monday through Friday at 9:00 AM

What this playbook does:

• Provides daily visibility into support workload
• Highlights urgent items that need immediate attention
• Tracks trending issues for pattern recognition
• Keeps the support team aligned on priorities

Key learning: This demonstrates metric tracking, prioritization, and trend analysis.

Meeting Notes Distribution #

The Request: “After our weekly team meetings, automatically distribute meeting notes and action items to relevant Slack channels.”

Generated Playbook:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

# Meeting Notes Distribution
Process and distribute meeting notes with automated action item tracking.

## Steps

- Access latest team meeting recording and notes from Google Drive

- Extract key decisions and action items from meeting content

- Identify action item owners and deadlines

- Create Linear tickets for action items that need tracking

- Format meeting summary with decisions and next steps:
  
  📝 Meeting Summary - [date]
  
  **Key Decisions:**
  • [Decision 1 with context]
  • [Decision 2 with context]
  
  **Action Items:**
  • [@Owner] [Action item] - Due: [date] - [Linear ticket link]
  • [@Owner] [Action item] - Due: [date] - [Linear ticket link]
  
  **Next Meeting:**
  • [Date/time and key agenda items]

- Post summary to #team-updates Slack channel

- Send direct messages to action item owners

- Save processed notes to shared meeting archive

## Trigger
- Run manually after weekly team meetings

What this playbook does:

• Ensures meeting outcomes are clearly communicated
• Creates trackable action items in project management tools
• Distributes information to the right people
• Maintains a searchable archive of decisions

Key learning: This shows manual triggers and multi-step distribution workflows.

Communication Patterns #

The Broadcaster Pattern #

Perfect for regular team updates:

• Collect information from multiple sources
• Format for team consumption
• Distribute to appropriate channels
• Handle timing considerations

The Alert Pattern #

Great for urgent or time-sensitive information:

• Monitor for specific conditions
• Identify escalation criteria
• Send targeted notifications
• Include context and next steps

The Summarizer Pattern #

Ideal for regular status reporting:

• Aggregate activity data
• Calculate metrics and trends
• Present in scannable format
• Highlight important changes

Best Practices for Team Communication #

Design for Your Team’s Workflow #

• Timing matters: Post standup summaries before meetings, not after
• Channel selection: Use team channels for shared updates, DMs for personal items
• Format consistency: Use the same template structure so people know what to expect

Include Context and Actions #

• Don’t just report what happened, explain why it matters
• Always include clear next steps or action items
• Tag relevant people when they need to take action
• Link to detailed information when available

Handle Communication Gracefully #

• Skip updates when there’s nothing meaningful to report
• Use positive framing when possible (“No urgent issues today!”)
• Consider different time zones and work schedules
• Plan for holidays and team schedule variations

Getting Started with Communication Automation #

1. Identify repetitive updates you manually create
2. Map your data sources (Linear, GitHub, Google Drive, etc.)
3. Design your output format with your team’s preferences
4. Set appropriate timing based on when people need the information
5. Test and iterate based on team feedback

Ready for more complex workflows? Check out Advanced Examples or learn about Patterns & Best Practices.