Keeping the feed quiet

This is a sample post. The product, the team and every detail in it are invented to show how an article looks. Replace it with your own.

The timeline has one job: to tell you what changed since yesterday. On a day when little changed, it should say little. That sounds obvious, and it took us three releases to get there.

A quiet day is a short page#

Daily summaries used to list every number you track. Most days, most of them had not moved, and the lines that mattered were hard to find. Summaries now mention only what moved.

The rules we follow#

• One entry per topic. Several conversations about the same thing become one line, not several.
• No entry without a change. A number that stayed where it was is not news.
• Nothing moves while you read. A new entry waits until you are back at the top of the page.
• No alerts. The feed does not ask for attention. It waits to be opened.

What an entry looks like#

Every entry has the same three parts: where it came from, when, and one line on what happened. The entries below are made up for this post.

Deploys    2h ago    Release 4.2 is in production. Fourteen changes, no rollbacks.
Support    3h ago    Six new conversations about billing.
Metrics    4h ago    Checkout latency is back to normal.

Less noise. More signal.

A weekly digest, for the same reason#

Workspaces on the Team plan can now receive an email every Monday with the entries that drew the most attention during the week. It is for the people who do not open the timeline every day, and it follows the same rules.