How does the Activity View get its insights?

The view runs automatically and continuously. Every item also shows the specific reasons behind its category, so you can see exactly why it landed where it did.

Each item lands in exactly one category

Some items could fit more than one category at once. When that happens, the Activity View shows the most important one. A finished item always shows as Recently Completed. For anything still in flight, a concern outranks a positive signal: Needs Attention comes first, then Not Updated, then Progressing Well, then Not Started.

For example, a Key Result you have been updating all week still shows as Needs Attention if something it depends on is at risk. The struggling dependency outweighs the recent activity. While work is still in progress, a problem is never hidden behind a positive signal.

What the Activity View watches for

The category comes from concrete signals on each item:

• Needs attention: confidence dropped sharply since the start of your window, progress went backward, the item passed its due date without finishing, a blocker is new or has been open too long, or something it depends on needs attention. An Objective is also flagged when half or more of its Key Results have gone quiet.

• Not updated: the item has not changed, or a Key Result has had no check-ins, for longer than your time window. Progress that has been stuck also counts.

• Progressing well: confidence or progress increased, check-ins are happening at the expected rate, or the item was worked on recently.

• Recently completed: a Key Result reached 100%, a Commitment was marked done, or an Interlock was resolved within your time window.

• Not started: the item has a future start date or was created very recently. New items are given room to get going before they can be flagged as not updated.

Your time window changes what counts as "recent"

You choose the lookback window: 7, 14, 30, or 90 days. The default is 14 days, which matches a typical sprint.

This window sets the bar for every freshness signal, so the same item can land in different categories depending on the window you pick. A Key Result with no check-in for ten days shows as Progressing Well at 30 days, but as Not Updated at 7 days. Shorter windows give a tighter pulse check. Longer windows suit monthly or quarterly reviews.

Dependencies are part of the picture

The Activity View does not look at items in isolation. If an item depends on something that needs attention, it is flagged too, even when it looks healthy on its own. This works across teams: when another team's Interlock slips, your dependent Key Result is surfaced right away. And when an Objective's Key Results go quiet, the Objective itself is flagged.

Why am I seeing a particular item?

Two separate things decide what you see:

• Which items appear depends mainly on the period you are viewing. Longer-range items stay visible inside a shorter period. An annual Objective, for example, still shows while you are viewing a single quarter. Turn on "Show only matching items" to hide those longer-range Objectives and see just what belongs to the exact period. An open Commitment or Interlock also keeps appearing until it is closed, even if it began in an earlier period.

• Which category an item gets depends on your time window.

Changing the time window re-sorts items between categories rather than adding or removing them. The one exception: completed work drops out of the view once it is older than your window.

Every classification is transparent

The Activity View uses a fixed set of rules, not an opaque score. The same inputs always produce the same result, and each item lists the exact reasons for its category. Nothing is guesswork, and nothing is hidden.