Why You Should Send a Weekly Summary Email
<p>Since I joined RevenueCat a year and a half ago, I have without fail sent a weekly email summary to my manager and my team, and I am asking all product managers in my team to do the same. It’s not something I invented, and it’s deceptively simple. However, this weekly ritual has many benefits that I want to talk about in the following.</p>
<p>At its core, the weekly email has two headings with 3–5 short bullet points each: <strong>achievements this week</strong> and <strong>priorities next week</strong>. Under the former, you list the 3–5 most important things you got done this week, under the latter, the 3–5 most important things you want to get done the following week.</p>
<p>Here is an example of how such an email could look like:</p>
<blockquote>
<p><strong>Achievements this week:</strong></p>
<p><strong>Charts</strong>: Created working prototype charts for all prioritized new charts ideas</p>
<p><strong>Amazon Appstore support</strong>: Finalized launch plan</p>
<p><strong>Expiration event bug</strong>: Helped triage a nasty bug and spec out a solution that will be implemented next sprint</p>
<p><strong>Priorities next week:</strong></p>
<p><strong>Charts</strong>: Start collecting and incorporating customer feedback on prototype charts</p>
</blockquote>
<p><a href="https://jefago.medium.com/why-you-should-send-a-weekly-summary-email-1c556149ed42"><strong>Read More</strong></a></p>