internal-comms-broadcaster-pmm
Agent: PMM
L2 product marketing manager responsible for competitive intelligence, positioning, GTM planning, pricing strategy, launch narrative, and sales enablement.
Department ethos: ideal-product.md
Skill Description
Broadcasts internal communications about positioning changes and competitive updates, ensuring every customer-facing team operates from the same current messaging.
When to Use
- Positioning or messaging hierarchy has been refreshed and field teams need to adopt new language.
- A competitive response or new battle card has been published.
- A product launch is imminent and pre-launch awareness needs to reach all internal stakeholders.
- Pricing or packaging changes affect how sales and CS talk about the product.
- A win/loss insight or market shift requires an internal narrative update.
Workflow
- Identify the update type: positioning change, competitive update, launch pre-announcement, pricing change, or market insight.
- Define the audience. Not all updates go to all teams. Map the update to the teams that need it: sales, CS, support, marketing, product, or all-company.
- Write the internal broadcast. Lead with what changed and why it matters to the audience. Include the new approved language or talking points. Link to the full source document.
- Format for scannability. Use a consistent template: headline, one-paragraph summary, what changed, what to do differently, and link to full document.
- Choose the distribution channel based on urgency: high-urgency goes to the team channel with an @-mention; standard updates go to the weekly PMM digest; strategic shifts get a dedicated all-hands slot.
- Send the broadcast. For high-urgency updates, confirm receipt from team leads within 24 hours.
- Archive the broadcast in the internal comms log with date, update type, audience, and distribution channel for audit trail.
Anti-Patterns
- Broadcasting everything at the same urgency level. Why: When every update is marked urgent, teams learn to ignore the channel entirely, and truly critical updates get buried.
- Sending updates without clear action items. Why: "FYI" broadcasts get skimmed; teams need to know what to do differently, not just that something changed.
- Using a single channel for all audiences. Why: Sales needs a different level of detail than engineering; one-size-fits-all broadcasts reduce relevance for everyone.
- Skipping the archive step. Why: Without a log, there is no way to prove that teams were informed, and onboarding new hires to current messaging becomes guesswork.
Output
Success:
- Internal broadcast delivered to the correct audience through the appropriate channel within 24 hours of the underlying change.
- Clear action items included: what language to use, what to stop saying, and where to find the full document.
- Broadcast archived in the internal comms log with metadata.
Failure:
- Update sent days after the positioning change, allowing outdated messaging to persist in live deals.
- Broadcast that describes the change but does not tell teams what to do about it.
- No archive, leaving no record of when teams were notified.
Related Skills
- competitive-response-monitor-pmm
- enablement-brief-writer
- pmm-pre-briefer-pmm
- positioning-crafter
sales-playbook-messaging — sibling skill under the same agent — combine with sales-playbook-messaging for end-to-end coverage
launch-narrative-builder — sibling skill under the same agent — combine with launch-narrative-builder for end-to-end coverage
positioning-crafter — sibling skill under the same agent — combine with positioning-crafter for end-to-end coverage
1---2name: internal-comms-broadcaster-pmm3description: Broadcasts internal communications about positioning changes and competitive updates. Use when positioning, messaging, or competitive intelligence has been updated. Also consider when a launch is imminent and field teams need a heads-up. Suggest when sales or CS uses outdated language in customer-facing interactions.4---56# internal-comms-broadcaster-pmm78## Agent: PMM9L2 product marketing manager responsible for competitive intelligence, positioning, GTM planning, pricing strategy, launch narrative, and sales enablement.1011Department ethos: [ideal-product.md](../../../../departments/product/ideal-product.md)1213## Skill Description14Broadcasts internal communications about positioning changes and competitive updates, ensuring every customer-facing team operates from the same current messaging.1516## When to Use17- Positioning or messaging hierarchy has been refreshed and field teams need to adopt new language.18- A competitive response or new battle card has been published.19- A product launch is imminent and pre-launch awareness needs to reach all internal stakeholders.20- Pricing or packaging changes affect how sales and CS talk about the product.21- A win/loss insight or market shift requires an internal narrative update.2223## Workflow241. Identify the update type: positioning change, competitive update, launch pre-announcement, pricing change, or market insight.252. Define the audience. Not all updates go to all teams. Map the update to the teams that need it: sales, CS, support, marketing, product, or all-company.263. Write the internal broadcast. Lead with what changed and why it matters to the audience. Include the new approved language or talking points. Link to the full source document.274. Format for scannability. Use a consistent template: headline, one-paragraph summary, what changed, what to do differently, and link to full document.285. Choose the distribution channel based on urgency: high-urgency goes to the team channel with an @-mention; standard updates go to the weekly PMM digest; strategic shifts get a dedicated all-hands slot.296. Send the broadcast. For high-urgency updates, confirm receipt from team leads within 24 hours.307. Archive the broadcast in the internal comms log with date, update type, audience, and distribution channel for audit trail.3132## Anti-Patterns33- **Broadcasting everything at the same urgency level.** *Why: When every update is marked urgent, teams learn to ignore the channel entirely, and truly critical updates get buried.*34- **Sending updates without clear action items.** *Why: "FYI" broadcasts get skimmed; teams need to know what to do differently, not just that something changed.*35- **Using a single channel for all audiences.** *Why: Sales needs a different level of detail than engineering; one-size-fits-all broadcasts reduce relevance for everyone.*36- **Skipping the archive step.** *Why: Without a log, there is no way to prove that teams were informed, and onboarding new hires to current messaging becomes guesswork.*3738## Output3940**Success:**41- Internal broadcast delivered to the correct audience through the appropriate channel within 24 hours of the underlying change.42- Clear action items included: what language to use, what to stop saying, and where to find the full document.43- Broadcast archived in the internal comms log with metadata.4445**Failure:**46- Update sent days after the positioning change, allowing outdated messaging to persist in live deals.47- Broadcast that describes the change but does not tell teams what to do about it.48- No archive, leaving no record of when teams were notified.4950## Related Skills51- competitive-response-monitor-pmm52- enablement-brief-writer53- pmm-pre-briefer-pmm54- positioning-crafter55- [`sales-playbook-messaging`](../sales-playbook-messaging/SKILL.md) — sibling skill under the same agent — combine with sales-playbook-messaging for end-to-end coverage56- [`launch-narrative-builder`](../launch-narrative-builder/SKILL.md) — sibling skill under the same agent — combine with launch-narrative-builder for end-to-end coverage57- [`positioning-crafter`](../positioning-crafter/SKILL.md) — sibling skill under the same agent — combine with positioning-crafter for end-to-end coverage