Templates

Communication

Your week in product, ready to share

Use Template

By Nalvin

Use Template

Description

Nalvin pulls from your product delivery and planning tools to generate a weekly digest of what shipped, what is in progress, and what is coming up. The digest is formatted for your audience—whether that is your team, leadership, or cross-functional stakeholders—and can be posted to Slack or Teams, sent by email, or saved to your docs.

Supported Integrations

Templates are flexible by default. Nalvin automatically picks the right integrations based on what you’ve connected.

Asana

ClickUp

Outlook Email

Gmail

Monday

Trello

Notion

Email

Shortcut

Linear

Microsoft Teams

Confluence

Jira

Slack

How to best use this template

Below are a few tips & tricks from the Nalvin team to get the most out of this template.

Set a consistent scope and schedule

A weekly digest works best when the scope is stable—same project, same team. Pair it with a fixed send time so readers know when to expect it.

Group by theme, not by ticket list

You can level this up by asking Nalvin to group updates by product area or theme instead of listing tickets. Themes are more readable and more useful for stakeholders.

Include a what's next section

A brief forward-looking section helps readers understand what is coming, not just what happened. This makes the digest more valuable for planning conversations.

Keep it short enough to read in two minutes

If the digest is too long, people stop reading it. Aim for 5–8 bullet points max and use a consistent structure so the format becomes familiar.

Allow replies and follow-up questions in Slack or Teams

Post the digest in a channel where stakeholders can react or ask questions. This keeps context together and surfaces missing information naturally.

Set a consistent scope and schedule

A weekly digest works best when the scope is stable—same project, same team. Pair it with a fixed send time so readers know when to expect it.

Group by theme, not by ticket list

You can level this up by asking Nalvin to group updates by product area or theme instead of listing tickets. Themes are more readable and more useful for stakeholders.

Include a what's next section

A brief forward-looking section helps readers understand what is coming, not just what happened. This makes the digest more valuable for planning conversations.

Keep it short enough to read in two minutes

If the digest is too long, people stop reading it. Aim for 5–8 bullet points max and use a consistent structure so the format becomes familiar.

Allow replies and follow-up questions in Slack or Teams

Post the digest in a channel where stakeholders can react or ask questions. This keeps context together and surfaces missing information naturally.