Task Completion Heatmap

Problem

• Finding which departments had finished their piece of an item usually cost a round of status-chasing for the operations team.
• Status lived in the review workflow tool but was hard to read across many items and departments at once.
• Parallel, multi-department progress had no single readable picture for leadership.
• Cells that could not be read had no honest way to be shown, so items could look done when they were not.

Solution

• Profiled the review workflow tool as the source of record and defined the completion logic.
• Designed a read-only pipeline that reads each department's status, normalizes it, and rolls it up without ever writing back.
• Defined how to show a cell that could not be read, so it reads as Not reported rather than assumed done.
• Designed the heatmap plus the item, department, and comparison views so progress is easy to scan.

Results

• Turned parallel, multi-department progress into one grid anyone can scan.
• Eliminated the round of status-chasing to find where an item stands.
• Kept the tool read-only, so it never changes a source status.
• Showed unread cells honestly as Not reported, never counted as done.

What you can explore here

• The skeletal dashboard below is an interactive prototype that reads a static, pre-baked snapshot of aggregate, sample status data. The heatmap, item detail, department view, Data Sources, and About views are all present. The search and the department, item-type, status, and fully-signed-off filters all work client-side over the inlined snapshot; selecting an item or a department opens its detail. There is no backend, no live integration, no login, and no data collection.
• Never color alone. Every heatmap cell shows a short symbol (C, P, N/A, ?) in addition to color, and a full status word for assistive technology, and the Not-reported state also carries a distinct pattern. A cell the integration could not read shows as Not reported and is excluded from the complete count, never assumed done.