Pain Streak Detection
Forage for consecutive high-effort signals. Detect when team members grind on the same difficult task for days β before burnout hits.
Dive beneath surface tasks to discover effort patterns. See burnout signals before they cascade.
HEAT (Heatmap for Effort and Agile Tracking) is a workplace foraging framework that makes invisible effort visible. Like cormorants diving beneath the surface to forage for what others miss, HEAT reveals the cognitive load patterns hiding beneath time logs.
Traditional View: Developer logged 8 hours
β
HEAT Foraging: 3 hours routine (x1 intensity)
2 hours context switching (x3 intensity)
3 hours grinding on blocker (x8 intensity)
β
Actual Load: 27 intensity units (burnout risk)HEAT discovers what traditional tracking misses:
| Letter | Meaning | Purpose |
|---|---|---|
| H | Heatmap | Visual representation of effort concentration |
| E | Effort | What's measured (intensity, not hours) |
| A | Agile | Lightweight tagging (30 sec/day overhead) |
| T | Tracking | Tag-driven work categorization |
The Pattern: Management assumes capacity. Reality consumes it invisibly. HEAT makes the gap visible.
| Hidden Pattern | Business Impact | HEAT Solution |
|---|---|---|
| Single point of failure | One person touches module for 6 months | Bus factor mapping |
| Silent burnout | Developer grinding on same task for days | π₯ Pain Streak alerts |
| Knowledge silos | Critical logic understood by one person | Ownership pattern visualization |
| Context switching tax | Single interruption costs 15Γ actual time | Context switching score |
| Shadow work | Support/config consuming innovation capacity | Tag analysis (Dev vs Support ratio) |
Research validates the scale:
Example: Mid-size engineering team (50 people)
| Friction Type | Annual Hidden Cost |
|---|---|
| Invisible overload | $150K - $400K |
| Knowledge concentration risk | (Unmeasured until loss) |
| Context switching tax | (Accepted as "normal") |
| Total with HEAT visibility | Preventable through early intervention |
β See full impact by team size
Developer tags work by type and intensity:
Task: Fix SQL performance issue
Tags:
- Type: Blocker
- Area: SQL
- Intensity: x7 (high cognitive load)Manager sees effort concentration:
| Developer | SQL | API | UI | Support | Burnout Risk |
|---|---|---|---|---|---|
| Alice | x42 | x3 | - | x8 | π₯ Streak (4 days) |
| Bob | x5 | x18 | x12 | x2 | Low |
| Carol | x1 | x4 | x38 | x15 | Medium |
Insight: Alice stuck on SQL blocker for 4 days β needs help now.
HEAT primarily addresses Employee (D2) and Operational (D6) dimensions of the 6D Foraging Methodology:
The cascade is real: What looks like a $100K HR problem is often a $600K+ business problem.
β Explore the 6D Cascade Effect
HEAT follows proven patterns from industry-leading frameworks:
| Framework | What It Does | HEAT Parallel |
|---|---|---|
| Google SRE Toil Tracking | Categorizes Toil vs Engineering; <50% target | Tags categorize Dev vs Support |
| Spotify Squad Health Check | Lightweight assessment; traffic-light visualization | Heatmap intensity thresholds |
| DORA Metrics | Deployment frequency, lead time, MTTR | Derived from metadata, not timesheets |
| Enterprise KTLO Tools (Jellyfish, Uplevel) | $50K+/year | HEAT achieves same insight β productized solution |
"All these frameworks exist as parallel lightweight layers because timesheets don't provide effort visibility. HEAT follows the same proven pattern."
| Framework | Purpose | Integration |
|---|---|---|
| 6D Foraging | Discover cost multipliers across six business dimensions | HEAT provides observables for Employee (D2) + Operational (D6) |
| HEAT | Workplace foraging intelligence β make effort visible | Feeds cascade analysis with burnout/overload signals |
| EASE | Engagement-Anchored Solution Enablement | Solutions powered by HEAT insights |
HEAT + EASE: Effort visible. Solutions enabled. πͺΆ