| name | Performance Debrief |
| description | Judge a published piece against comparable ones, and take one lesson from it. |
| category | Analytics |
Performance Debrief
Judge against something. A view count on its own is a number, not a result.
When to use
- A piece has been out long enough for its numbers to settle.
- A format is being considered for repetition or retirement.
Steps
- Compare against similar pieces, not against hope or against the best
piece ever made. Same format, similar length, similar topic.
- Read the retention curve before the comments. Where people left is a
fact; why they say they left is a story, and the two frequently disagree.
- Separate the hook from the piece. A low click rate and a high retention
is a thumbnail problem; the reverse is a content problem, and treating one as
the other wastes the next month.
- Check the calendar effect. Cadence, day, and whether the last piece
underperformed — audiences respond to the sequence, not to the single piece.
- Take one lesson, not five. Five lessons from one video is a superstition
generator.
- Record it —
performance on the content row, and any real pattern on
audience-signals or the baseline's learnings.
Output
The content row updated with what it actually did against comparable pieces, and
one recorded lesson. "Indistinguishable from our usual" is a legitimate and
common result.