The 3Ps Framework
Many team updates list activity without showing what changed, what happens next, or what is blocked. Progress, Plans, and Problems gives the update those three fields.
A status update should help a reader judge movement, commitments, and blockers. When it lists only meetings, tickets, and drafts, the reader still has to ask what changed and what needs action.
The 3Ps force a different contract. Progress states what moved, with numbers. Plans commit to what will be true by the next update. Problems name blockers while they are still cheap to fix, each with an owner and an ask. Three headings, under 200 words, same day every week.
The format creates discipline only when the team keeps the same headings, word limit, and weekly cadence.
HYPOTHETICAL EXAMPLE PROGRESS - Shipped welcome flow v2. Conversion rate increased 1.8 percentage points versus the holdout. - Migrated 3 of 5 lifecycle segments to the customer-lifetime-value model.
HYPOTHETICAL EXAMPLE PLANS - Launch the win-back test to 20% of the lapsed cohort by 08/14/2026. Owner: Jordan Lee. - Draft the Q3 experiment calendar by 08/14/2026. Owner: Jordan Lee.
HYPOTHETICAL EXAMPLE PROBLEMS - Deliverability declined on sending domain 2. Root cause: unknown. Owner: Priya Shah. Ask: Infrastructure Engineering review by 08/14/2026.
CADENCE - Sent Fridays at 2:00 p.m. Mountain Time in #team-lifecycle. - Skipped weeks are announced, never silent.
3ps-framework/
├── SKILL.md ← the procedure and the guardrails
├── meta.yaml ← version, sources, changelog, test prompts
├── LICENSE.md ← MIT
├── assets/
│ └── 3ps-update.md ← the 200-word update scaffold
└── references/
└── weekly-update.md ← two worked updates, one with gaps"Write my weekly 3Ps update from these notes."