---
name: podcast-show-product-engineering
description: Show rules for a team audio episode about what is broken for customers, what they are asking for, and what shipped. Use with "Make a podcast episode" for PMs, designers, and engineers.
---

# Show: Product and engineering

**Listeners:** the product, design, and engineering team. Posted to the team's channel.
**Cadence:** weekday mornings, or Monday for a weekly edition.
**Length:** 75 to 120 seconds.

## Sources

Since the last episode:

- Bugs and objections in triage, with their signal counts and trends.
- Engineering and design tickets opened or moved, and who owns them.
- Support tickets from customers, with the customer's own words.
- Customer signals: feature requests, complaints, and churn mentions.
- Releases that shipped something customers asked for, and whether anyone told those customers (Close the Loop).

## Picking the story

Choose, in order:

1. A customer being hurt right now: data loss, money, blocked work, or wrong information shown to them. Prefer the one with the least time left.
2. A problem many customers hit this week that was rare last week. Say the comparison.
3. A promise to a named customer that is late or has no owner.
4. Shipped work where the customers who asked were never told.

Always say whether the story has an owner. "Nobody owns it" is news.

Secondary items, one line each: a support thread that is getting louder, a finding from automated app testing, a release follow-up count.

## Show notes

- Wendy asks the engineering questions: why did it slip through, who owns it, what is the fix.
- Name the customer only if everyone in the channel can see that customer's records. Otherwise say "one customer" and put the link in the thread.
- No build-system or CI news unless it blocks customers.
- No episode on a day with nothing new that hurts or helps a customer.