Find concentrated activity
See whether contribution or review activity repeatedly gathers around a few people. Inspect their responsibilities before changing assignments.
Activity Heatmap
See participation patterns. Investigate the work behind them.
Follow commits, pull requests, and reviews over time. Find concentrated review activity and changes in participation, then inspect the Developer Work Log for context.
Activity Heatmap
Engineering · October 2026Team contribution patterns
4 contributors · 20 working days
| Contributor | 5 | 6 | 7 | 8 | 9 | 12 | 13 | 14 | 15 | 16 | 19 | 20 | 21 | 22 | 23 | 26 | 27 | 28 | 29 | 30 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Maya Patel | ||||||||||||||||||||
| Alex Morgan | ||||||||||||||||||||
| Sam Taylor | ||||||||||||||||||||
| Jordan Lee |
Fewer eventsMore events
Developer Work Log
Maya Patel · Oct 13 · 2 reviews
- Commits
- 11
- Pull requests
- 3
- Reviews
- 2
Switch the activity type and select a day to inspect the underlying counts. Color intensity in this preview reflects event counts.
From signals to decisions
Turn an activity pattern into a useful question
Read the distribution over time, then inspect the contribution types and context behind it.
Review collaboration patterns
Compare reviews, approvals, comments, and pull requests to understand how work moves between contributors.
Inspect the daily work log
Follow a visual pattern into daily activity counts. Use the details to ask a more specific question in the team review.
What to look at
Make the scoring context visible
Activity intensity helps locate a pattern. Review the settings and underlying events before interpreting what the pattern means.
- Time window and working days
- Selected team, roles, and activity types
- Activity coefficients and daily normalization
- Daily event counts in the work log
- Choose the analysis scope
- Select the period, team, roles, activity types, and working day settings relevant to the question.
- Understand the scoring settings
- Oobeya supports configurable coefficients for activity types and daily normalization. Keep those settings consistent when reviewing trends.
- Check the counts behind the color
- Use the Developer Work Log to inspect the underlying activity. A darker cell indicates more recorded activity within the scoring context.
What to look at
Bring the pattern into the team conversation
Use the heatmap alongside the team’s workflow, responsibilities, and delivery results.
- Review activity alongside delivery and quality
- Account for role, task type, leave, and support work
- Follow recurring patterns over several periods
- Retrospectives
- Review changes in participation over the sprint and discuss the events behind unusual days.
- Review workload
- Find repeated concentration in review activity and discuss opportunities to share knowledge and responsibility.
- Capacity conversations
- Read activity alongside assignments, leave, and support responsibilities. Follow up in Resource Allocation.
Which activities can we inspect?
Activity Heatmap supports contribution types such as commits, pull requests, reviews, approvals, comments, and code changes. Availability depends on the connected sources and selected activity type.
Can we filter the heatmap?
Yes. Use the time period, team, role, activity type, and working day settings to focus the analysis.
How are activity scores configured?
Oobeya supports coefficients for activity types and daily normalization. Review your organization’s settings to understand what the score represents.
What does the Developer Work Log show?
The work log provides daily activity counts behind the visual patterns so teams can inspect the underlying contributions.
Does a darker cell mean higher productivity?
It indicates higher recorded activity within the selected scoring context. Interpret the pattern with the person’s role, task complexity, delivery results, and quality.
How does this relate to resource allocation?
Resource Allocation shows planned workload and capacity. Activity Heatmap shows contribution patterns over time. Use both when discussing assignments and team support.
See Oobeya in practice
Explore the work behind your team’s activity
Walk through Activity Heatmap, the Developer Work Log, and scoring settings with your engineering workflow in mind.