slice icon Context Slice

What You Worked On

This isn't about job roles or hats. It's about what was actually on their mind during different periods - the specific topics, projects, and themes that dominated their calendar.

CRITICAL: Only Analyze Accepted Meetings

Only count meetings where userAccepted=true. If the user didn't explicitly accept, they weren't there. This is especially important for detecting when the user actually started working - early months may have calendar invites they never responded to.

Mine Descriptions, Not Just Titles

Descriptions are underused gold. Many calendar events have agendas or context in the description field:

  • "Discuss the migration timeline and blockers"
  • "Review product launch checklist"
  • "Deep dive on user retention metrics"

These tell you the ACTUAL topic even when the title is generic like "Sync" or "Check-in."

Find Recurring Meeting Titles

Specific meeting titles that repeat are also valuable:

  • "[Topic A]" appearing 15 times in July, 18 in August → they were deep in that work
  • "[Topic B]" discussions dominating September → that's what they were thinking about
  • "[Project name]" showing up 23 times → major project

Count them. Connect them to periods. This tells you what they were FOCUSED on.

Example insight: "'[Topic A]' became a recurring theme (15 times in July, 18 in August). Combined with '[Topic B]' discussions, this was clearly a heads-down product phase."

Track Topic Shifts Over Time

Topics that appear/disappear signal focus changes:

  • "Customer onboarding" ramping from 2/month → 30/month = product launch
  • "Hiring" appearing everywhere in spring then fading = hiring push completed
  • "Migration" dominating Q3 then vanishing = project shipped

The SHIFT is often more interesting than the total.

All-Day Events Are NOT Topics

Critical: All-day events (isAllDay=true) are status markers, not topics:

  • "Firefighter", "On-call", "WFH" = availability status
  • Do NOT count these or build narratives around them

Blocks Tell You About Focus

Solo blocks with specific titles reveal deep work:

  • "Product roadmap" block → product thinking
  • "Deep work: API design" → technical focus
  • "Strategy doc" → planning mode

These are just as meaningful as meetings for understanding focus.

What They Were Thinking About

Frame findings as what was on their mind, not job functions:

Good: "'[Topic A]' dominated your summer. Combined with '[Topic B]' discussions, you were clearly deep in product thinking."

Bad: "You wore three hats: Firefighter, AI Success Lead, Skills Developer."

The first tells them what they were focused on. The second is a job description.

Time-Bound Specifics

Connect topics to periods with counts:

  • "August was [topic] month - more sessions than any other topic"
  • "Customer conversations ramped up after September: 29 onboarding events"
  • "'Platform' appeared 23 times between April and June, then disappeared"

Output

Markdown section ## What You Worked On

2-3 insights about specific topics that dominated their calendar.
Use actual meeting titles. Include counts. Connect to time periods.
Make them realize what they were actually focused on.