Moments are the specific performance signals and observations that AI Assisted Reviews surfaces from 15Five's context layer for a review. They represent sourced evidence tied to real work — not summaries or generic observations. Every Moment traces back to a specific data source and time period.
This article applies to organizations enrolled in the AI-assisted reviews beta.
What Moments are
Moments are organized into four themes:
| Theme | What it contains |
|---|---|
| Strengths and impact | Specific outcomes and recognized wins from the review period. Used to ground claims about impact in evidence rather than general praise. |
| Goal progress | Progress against objectives set for the cycle, including what was completed, what stalled, and relevant context around both. |
| Growth edges | Areas where the data points to development opportunities or patterns worth addressing. |
| How they work | Signals about collaboration, communication, and working style drawn from connected tools and 15Five data. |
Each Moment includes:
- The sourced evidence (what actually happened)
- The data source it came from (e.g., Asana, Slack, a 1:1 note, a check-in)
- A header describing the observation
- The age of the moment relative to the review period
Where Moments come from
Moments draw from two categories of data within the performance period set during cycle creation:
15Five data (always available):
- Performance reviews from prior cycles
- 1:1 notes
- Check-ins
- Objectives and key results
- High Fives
- Kona insights
- A company or individual context that has been added
Work context from connected integrations (when available):
- Slack and Microsoft Teams conversations
- Jira and Asana tickets and project activity
- Google Drive and OneDrive documents
- Google Calendar and Outlook meeting patterns
- Other connected work system integrations
The more integrations connected and the more context added, the richer and more specific Moments become.
How reviewers work with Moments
During the Reflect phase, reviewers step through each theme and decide what is relevant:
- Review the Moments presented under each theme tab.
- Exclude any Moment that is not relevant to this review — excluded Moments are not used when the AI drafts answers.
- Add notes — type observations or context tied to a theme using the rich text editor.
- Upload files — attach documents, transcripts, or other files as additional context.
Moments that are kept become the evidence pool the AI draws from during the Write phase. The reviewer controls what goes in — the AI does not add evidence the reviewer has not seen.
How Moments feed the draft
After the reviewer finishes working through Moments and clicks Draft review, the AI generates structured draft answers across all review questions. Each draft answer:
- Is grounded in the Moments and notes the reviewer assembled
- Can be edited freely — the reviewer owns the narrative
- Shows the Moments used for that answer directly below the text editor, so the reviewer always knows what the draft is based on
Verifying Moment sources
Every insight in a Moment is traceable. Click View Sources on any Moment to see exactly where the information came from — a specific Slack thread, a Jira ticket, a 1:1 note, or another connected source. This lets reviewers:
- Verify the insight before including it
- Click through to the actual conversation or ticket for more context
- Build confidence that the AI is reading real signals, not generating generic observations
If Moments appear empty or sparse
- Performance period may be too narrow — verify the cycle's performance period covers enough time for meaningful data.
- Work system integrations may not be connected — the Full support level is required to pull data from Slack, Jira, and other tools. See Connect work system integrations (Admin).
- Insufficient 15Five activity — if the employee has limited check-ins, 1:1 notes, or objective updates within the performance period, Moments will be limited to available data.