Inspect a shift in activity, compare two periods and decide how to follow up. Each case in this illustration uses synthetic activity.
Activity review
Synthetic example
Review queue
Choose a case to inspect its activity.
Case A
Earlier in the week
Both weeks have 12 events. This week, most took place on Monday and Tuesday. The weekly total alone would hide that shift.
Activity by day
Synthetic events per day for Case A
Day
Previous week
Current week
Monday
1
5
Tuesday
1
4
Wednesday
1
1
Thursday
4
1
Friday
4
1
Saturday
1
0
Sunday
0
0
Review question Did the schedule change between these weeks?
Case B
After a pause
The previous week had no recorded events. Activity returned on Wednesday and appeared again on Friday and Saturday. A gap in the record needs context.
Activity by day
Synthetic events per day for Case B
Day
Previous week
Current week
Monday
0
0
Tuesday
0
0
Wednesday
0
2
Thursday
0
0
Friday
0
3
Saturday
0
1
Sunday
0
0
Review question Was the pause expected, or is a record missing?
Case C
A one-day cluster
Each week had eight events. The first spread them across five days. The second recorded all eight on Thursday.
Activity by day
Synthetic events per day for Case C
Day
Previous week
Current week
Monday
2
0
Tuesday
1
0
Wednesday
2
0
Thursday
1
8
Friday
2
0
Saturday
0
0
Sunday
0
0
Review question Were events recorded together after the fact?
Changes last until you reset or reload this page.
What I designed
I defined behavioral risk factors and wrote the criteria for recognizing each one. I designed a scoring framework to prioritize cases for human review.
Where this applies
When a team has more activity to examine than time to examine it, a shared review queue can help. Start with the changes your reviewers care about, agree on what each one looks like, and give the person reviewing a case enough context to decide what to do next.
Work with Matt
What’s slowing your team down?
Tell me about a report you rebuild, a queue you manage, or a process that’s hard to teach.