Why it works
Product updates eat a PM's Friday because the inputs are scattered across engineering, design, and data. A fixed weekly prompt turns "chase everyone" into "read the replies," and the "needs a decision" line surfaces the blockers that would otherwise wait for a meeting. The email is identical every week — the substance is in what people send back.
Make it yours
Send it to the working team a day before your stakeholder update goes out, so you're synthesizing fresh replies rather than reconstructing the week from memory. Add a "risks" line if your stakeholders care about what might slip.