Measuring Productivity With Activity Heatmaps

Most project dashboards are built around simple state counts: how many tasks are todo, how many are in progress, and how many are done. Those numbers matter, but they are not enough. They tell you where the work ended up. They do not show the shape of the work that got it there.

That distinction is important for Otto do it because process is part of productivity. Writing a useful task, clarifying its description, assigning a priority, setting an estimate, adding a due date, moving the task through workflow, closing it out, archiving stale work, and changing ownership are all signals. They are not equal signals, but they are real signals. A workspace that only counts done tasks misses the planning, context, and decision-making that make done work possible.

[block:activity-heatmaps-video]

The Activity Score Formula is the first Otto do it attempt to make that process visible without pretending that one number can explain everything. The system starts with visible workspace ActivityEvent records, then classifies each event into one of six activity types: workflow, content, planning, lifecycle, people, and context. Workflow events include task completions, status moves, priority changes, and estimate changes, and they carry the highest weight at 5 points. Content events such as task comments, description edits, and title edits are worth 4 points. Planning and lifecycle events are each worth 3 points: planning covers task creation, draft publishing, due dates, and ordering, while lifecycle covers archive, restore, and delete activity. People activity, including account and owner changes, is weighted at 2 points. Context activity, such as labels, links, and supporting changes that do not fit the higher-weight groups, is worth 1 point.

[block:activity-score-formula-image]

The formula is simple on purpose: Activity events x activity type weight = Activity score. The important part is not that the weights are perfect. They will evolve as the product learns more from real workspace behavior. The important part is that the score is grounded in actual actions instead of vibes, vanity totals, or a single progress percentage.

Otto then turns those scores into Heatmaps. Weekly Activity is calculated in 30-minute buckets across the week, with each cell receiving both an event count and a weighted score. A quiet half hour stays empty. A busy half hour gets intensity based on the score in that bucket. The grid is interactive: hover or tap a cell and Otto shows the exact time window, number of Activity events, and point total. The heatmap can be filtered by project and activity type, so users and workspace admins can look at all activity, just workflow movement, planning activity, content updates, or another slice of the workspace.

[block:activity-heatmap-comparison]

The same data also feeds an annual Heatmap. Instead of half-hour buckets, the annual view rolls Activity Score into daily cells across the year, giving users weeks and months of context at once. It helps answer a different question: not just what happened today, but whether work is happening in healthy rhythms over time.

The Signals section adds readable data points around the Heatmaps. Activity score shows weighted momentum. Total Activity events shows raw volume. Tasks created, tasks completed, and closeout ratio keep the familiar progress counters nearby. Peak time finds the busiest two-hour window across the weekly half-hour buckets. Weekend share shows how much activity happened on Saturday and Sunday. Active days, Coverage, Busiest day, and other annual stats make the long-term pattern easier to scan without forcing people to interpret every square manually.

Those signals matter because productivity is not only about finishing work. It is also about when work happens, how much context is being created, whether the workspace is moving in bursts or steady rhythms, and whether the process is visible enough for someone to trust it. A simple in progress or done count can hide too much. It can make a workspace look quiet when people are clarifying tasks, structuring projects, or doing the planning that prevents future confusion.

[block:activity-signals-slider]

For workspace admins, Heatmaps become a way to understand progress and productivity without micromanaging individual tasks. Today they show workspace and project rhythm in real time from the latest ActivityEvent data. As multi-member workspaces expand, the people category will become a stronger part of the model, making it possible to compare activity patterns across members while still keeping the focus on process quality rather than surveillance.

This is not perfect math, and it should not be treated as a judgment of work quality. Project management software cannot know whether the final work is good. But it can show whether the workspace has momentum, whether that momentum is balanced, and whether the process behind the work is visible. That is the point of Activity Score, Heatmaps, and Signals: to give users enough context to understand how they are spending time in relation to their other time, and to make the process of work easier to see.