Write the weekly product update
One message for the company on what product shipped and what's next.
Product · Software · On a schedule · Updated
Slack
Linear
Jira
GitHubHow do you write the weekly product update?
To write the weekly product update, set a Loop in Maito for Friday afternoon. It reads what shipped in Linear, Jira or GitHub, lists what is next, adds what the team learned, and posts a draft in Slack. You edit the draft and post it to the company channel.
How it's done today
PM writes it every Friday from scratch.
What Maito does
- Read what shipped and what's in progress
- Draft a short update
Example
Loop run: Friday 2:00 PM · Weekly product update
Draft for #general. Edit and post when ready. "Product update, Oct 16 Shipped • Bulk reassign: change the owner of up to 100 projects at once • Faster search: under a second at 10,000+ items • Connect your data step in onboarding Next week • SSO for the Team plan goes to testing • Mobile layout fix for onboarding What we learned The new onboarding step lifted import completion, but it hid the Continue button on small phones. Fix is on its way." The catch: Linear marks Export to PDF as Done, but the code is merged behind a flag that is still off in production. I left it out of Shipped. Say so if you want it in as beta.
@Maito Put SSO first under next week, and add Export to PDF as beta.
Done, updated draft above. Export to PDF now reads "in beta, ask us for access". Nothing has been posted to #general.
Maito (2:00 PM):
Draft for #general. Edit and post when ready.
"Product update, Oct 16
Shipped
• Bulk reassign: change the owner of up to 100 projects at once
• Faster search: under a second at 10,000+ items
• Connect your data step in onboarding
Next week
• SSO for the Team plan goes to testing
• Mobile layout fix for onboarding
What we learned
The new onboarding step lifted import completion, but it hid the Continue button on small phones. Fix is on its way."
The catch: Linear marks Export to PDF as Done, but the code is merged behind a flag that is still off in production. I left it out of Shipped. Say so if you want it in as beta.
Leo (2:18 PM):
Put SSO first under next week, and add Export to PDF as beta.
Maito (2:19 PM):
Done, updated draft above. Export to PDF now reads "in beta, ask us for access". Nothing has been posted to #general.
How to set it up
- Ask your agent
“Every Friday at 2, read what we shipped in Linear and the repo and draft the weekly product update for #general. Send the draft to me first, and I'll post it myself.”
- Connect issue tracker
- Linear
- Jira
- GitHub
Not connected yet? Your agent sends you a link to sign in.
What it won't do
It reports what happened in the tracker and code. Context like why a priority changed comes from you.
Questions
No. It drafts it in Slack for you to edit and send.
The issue tracker and the repository, so the update reflects work that really shipped.
Yes. Share a past update and it follows the same headings and tone.
