internal-comms-3p-updates

name	internal-comms-3p-updates
description	Framework for writing concise 3P (Progress, Plans, Problems) team updates for executives and stakeholders
progressive_disclosure	{"entry_point":{"summary":"Framework for writing concise 3P (Progress, Plans, Problems) team updates for executives and stakeholders","when_to_use":"When working with internal-comms-3p-updates or related functionality.","quick_start":"1. Review the core concepts below. 2. Apply patterns to your use case. 3. Follow best practices for implementation."}}

Instructions

Write a 3P update. 3P updates stand for "Progress, Plans, Problems." The main audience is executives, leadership, and teammates. Keep updates succinct and to-the-point: 30-60 seconds reading time. Write for people with some context on what the team does, but not deep familiarity.

3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals."

They represent the work of the team across a time period, almost always one week. They include three sections:

1. Progress: what the team has accomplished over the next time period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
2. Plans: what the team plans to do over the next time period. Focus on what things are top-of-mind, really high priority, etc. for the team.
3. Problems: anything that is slowing the team down. This could be things like too few people, bugs or blockers that are preventing the team from moving forward, some deal that fell through, etc.

Before writing, confirm the team name. If not specified, ask explicitly for the team name.

Tools Available

Whenever possible, try to pull from available sources to get the information you need:

• Slack: posts from team members with their updates - ideally look for posts in large channels with lots of reactions
• Google Drive: docs written from critical team members with lots of views
• Email: emails with lots of responses of lots of content that seems relevant
• Calendar: non-recurring meetings that have a lot of importance, like product reviews, etc.

Gather as much context as possible, focusing on the time period being covered:

• Progress: anything between a week ago and today
• Plans: anything from today to the next week
• Problems: anything between a week ago and today

If lacking access, ask the user for topics to cover. They may also provide these directly - in which case, format them appropriately for this particular format.

Workflow

1. Clarify scope: Confirm the team name and time period (usually past week for Progress/Problems, next week for Plans)
2. Gather information: Use available tools or ask the user directly
3. Draft the update: Follow the strict formatting guidelines
4. Review: Ensure it's concise (30-60 seconds to read) and data-driven

Formatting

The format is always the same, very strict formatting. Never use any formatting other than this. Pick an emoji that is fun and captures the vibe of the team and update.

[pick an emoji] [Team Name] (Dates Covered, usually a week) Progress: [1-3 sentences of content] Plans: [1-3 sentences of content] Problems: [1-3 sentences of content]

Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.