Weekly status
The Friday status report the Product Lead reads before the weekly 1:1, generated by the pipeline from the same data as every other page, plus the 90-day success metrics from the role.
90-day success metrics
Before and after the weekly process
Old backlog, before this sweep
Business days from ask to decision
How to read this: every ask from the last 8 weeks, by business days waited before its Friday triage. The dashed line is the target.
This week's report
Source files: weekly_status.md · escalations.md · linear_import.csv. Posted in Slack every Friday, with async updates in between.
Operating rhythm
| When | What | Output |
|---|---|---|
| Daily | Watch the request channel, the form and GitHub / X; log new asks and candidates | Raw intake, candidate list |
| Friday morning | Run the pipeline: match, dedupe, score, decide; send every reply | Linear updated, replies sent |
| Friday | Escalations and build briefs out; skill launches go out | Briefs to engineering, launch notes |
| Friday afternoon | Written status in Slack | This report |
| Weekly 1:1 | Product Lead decides on escalations and partnerships | Decisions logged on the Linear issue |
| Quarterly | Backtest the priority weights and refit the skills model on new outcomes; review every declined tool | Updated weights and declines |